From 81713332d118fb01ccfceff93cc3a5d9cfc68e0e Mon Sep 17 00:00:00 2001
From: Kevin F <Freymaurer@gmx.de>
Date: Thu, 19 Sep 2024 12:08:29 +0200
Subject: [PATCH] publish domain change

---
 README.md                                    |  2 +-
 astro.config.mjs                             |  3 +--
 src/components/Home/HeroText.astro           |  2 +-
 src/components/Navbar.astro                  | 10 +++++-----
 src/components/Search.astro                  |  8 ++++++++
 src/components/ThemeController.astro         |  6 +++---
 src/layouts/BaseLayout.astro                 |  2 +-
 src/layouts/MarkdownLayout.astro             |  2 +-
 src/pages/details/arc-data-hub.md            |  6 +++---
 src/pages/details/arc-data-model.md          | 10 +++++-----
 src/pages/details/arc-representation.md      |  4 ++--
 src/pages/details/developer-toolstack.md     |  4 ++--
 src/pages/details/documentation-principle.md | 12 ++++++------
 src/pages/details/fairness-and-rdm.md        |  6 +++---
 src/pages/details/organization-principle.md  |  4 ++--
 src/pages/details/validation.md              |  4 ++--
 src/statics.ts                               |  2 +-
 tailwind.config.mjs                          |  8 ++++----
 18 files changed, 51 insertions(+), 44 deletions(-)

diff --git a/README.md b/README.md
index 055a5bf..ecb4a3f 100644
--- a/README.md
+++ b/README.md
@@ -2,4 +2,4 @@
 
 The official ARC (annotated research context) website!
 
-[nfdi4plants.github.io/arc-website/](https://nfdi4plants.github.io/arc-website/)
+[arc-rdm.org/](https://arc-rdm.org)
diff --git a/astro.config.mjs b/astro.config.mjs
index b18790a..cbe165f 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -14,8 +14,7 @@ import pagefind from "astro-pagefind";
 // https://astro.build/config
 export default defineConfig({
   integrations: [tailwind(), mdx(), icon(), pagefind()],
-  site: 'https://nfdi4plants.github.io',
-  base: 'arc-website/', // will kill pagefind integration without trailing slash
+  site: 'https://nfdi4plants.github.io/',
   markdown: {
     remarkPlugins: [remarkDirective, remarkReplaceLinks(), remarkReplaceTooltips(), remarkAsides()],
     rehypePlugins: [
diff --git a/src/components/Home/HeroText.astro b/src/components/Home/HeroText.astro
index 2f2e63d..40f9d0b 100644
--- a/src/components/Home/HeroText.astro
+++ b/src/components/Home/HeroText.astro
@@ -16,7 +16,7 @@ const mainHeroText = "The ARC is a framework for organizing and documenting rese
           <span class="text-accent">C</span>ontext 
         </div>
       </h1>
-      <p class="py-6 prose-lg" style="text-align:justify">
+      <p class="py-6 prose-lg xl:prose-xl" style="text-align:justify">
         {mainHeroText}
       </p>
     </div>
diff --git a/src/components/Navbar.astro b/src/components/Navbar.astro
index 45a31bd..c61927a 100644
--- a/src/components/Navbar.astro
+++ b/src/components/Navbar.astro
@@ -64,7 +64,7 @@ const linksMin: Link[] = [
       </div>
     </div>
     <a class="btn btn-ghost text-xl" href={URLS.INTERNAL_HOME} >
-      <img src="/arc-website/favicon.svg" alt="logo" class="h-8 w-8" />
+      <img src="/favicon.svg" alt="logo" class="h-8 w-8" />
     </a>
   </div>
   <div class="navbar-center hidden lg:flex">
@@ -76,7 +76,7 @@ const linksMin: Link[] = [
       <img
         id="github-logo"
         class="p-2"
-        src="/arc-website/github-mark.svg">
+        src="/github-mark.svg">
       </img>
     </a>
     <ThemeController />
@@ -86,11 +86,11 @@ const linksMin: Link[] = [
 <style>
   /* Light mode: Show light-mode.svg */
 html[data-theme="light"] #github-logo {
-  content: url('/arc-website/github-mark.svg');
+  content: url('/github-mark.svg');
 }
 
 /* Dark mode: Show dark-mode.svg */
-html[data-theme="black"] #github-logo {
-  content: url('/arc-website/github-mark-white.svg');
+html[data-theme="dark"] #github-logo {
+  content: url('/github-mark-white.svg');
 }
 </style>
\ No newline at end of file
diff --git a/src/components/Search.astro b/src/components/Search.astro
index d5e167c..0a51693 100644
--- a/src/components/Search.astro
+++ b/src/components/Search.astro
@@ -97,6 +97,14 @@ document.addEventListener('keydown', function(event) {
   --pagefind-ui-font: sans-serif;
 }
 
+.pagefind-ui__search-input {
+  outline: unset !important;
+}
+
+.pagefind-ui__search-input:focus {
+  border: 2px solid oklch(var(--p))
+}
+
 </style>
 
 <style>
diff --git a/src/components/ThemeController.astro b/src/components/ThemeController.astro
index 21e271c..cd898b2 100644
--- a/src/components/ThemeController.astro
+++ b/src/components/ThemeController.astro
@@ -3,7 +3,7 @@
   function initializeTheme() {
     const savedTheme = localStorage.getItem('theme');
     const prefersDarkMode = window.matchMedia('(prefers-color-scheme: dark)').matches;
-    const theme = savedTheme || (prefersDarkMode ? 'black' : 'light');
+    const theme = savedTheme || (prefersDarkMode ? 'dark' : 'light');
     document.documentElement.setAttribute('data-theme', theme);
     updateToggleButton(theme);
   }
@@ -11,7 +11,7 @@
   // Function to toggle between light and dark themes
   function toggleTheme() {
     const currentTheme = document.documentElement.getAttribute('data-theme');
-    const newTheme = currentTheme === 'light' ? 'black' : 'light';
+    const newTheme = currentTheme === 'light' ? 'dark' : 'light';
     document.documentElement.setAttribute('data-theme', newTheme);
     localStorage.setItem('theme', newTheme);
     updateToggleButton(newTheme);
@@ -35,7 +35,7 @@
 <button class="btn btn-ghost btn-circle">
   <label class="swap swap-rotate">
     <!-- this hidden checkbox controls the state -->
-    <input id="theme-toggle" type="checkbox" class="theme-controller" value="black"/>
+    <input id="theme-toggle" type="checkbox" class="theme-controller" value="dark"/>
   
     <!-- sun icon -->
     <svg
diff --git a/src/layouts/BaseLayout.astro b/src/layouts/BaseLayout.astro
index 8d0d9dc..e65d17b 100644
--- a/src/layouts/BaseLayout.astro
+++ b/src/layouts/BaseLayout.astro
@@ -16,7 +16,7 @@ const { title } = Astro.props;
 		<meta charset="UTF-8" />
 		<meta name="description" content="Astro description" />
 		<meta name="viewport" content="width=device-width" />
-		<link rel="icon" type="image/svg+xml" href="/arc-website/favicon.svg" />
+		<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
 		<meta name="generator" content={Astro.generator} />
 		<title>{"ARC | " + title}</title>
 	</head>
diff --git a/src/layouts/MarkdownLayout.astro b/src/layouts/MarkdownLayout.astro
index 455b6a6..70839c7 100644
--- a/src/layouts/MarkdownLayout.astro
+++ b/src/layouts/MarkdownLayout.astro
@@ -40,7 +40,7 @@ function buildNestedHeadings(headings: Heading[]): NestedHeading[] {
 const { frontmatter, headings } = Astro.props;
 
 function createTagLink(tag: string) {
-  return `/arc-website/details/tags/${tag}`;
+  return `/details/tags/${tag}`;
 }
 
 // Generate the nested headings structure
diff --git a/src/pages/details/arc-data-hub.md b/src/pages/details/arc-data-hub.md
index 0d17203..90a753b 100644
--- a/src/pages/details/arc-data-hub.md
+++ b/src/pages/details/arc-data-hub.md
@@ -14,7 +14,7 @@ The **ARC Data Hub** concept applies the software development principles of _Con
 ARCs can be continuously validated, built, and deployed much like software.
 By using CI/CD for a set of subsequently defined tasks, many collaborative cloud platforms such as GitLab, GitHub, or Bitbucket can be used to build an ARC Data Hub.
 
-![ARC Data Hub leverages CI/CD capabilities to build, deploy, and validate ARCs](/arc-website/arc-data-hub-overview.png)
+![ARC Data Hub leverages CI/CD capabilities to build, deploy, and validate ARCs](/arc-data-hub-overview.png)
 
 ## Continuous Deployment
 
@@ -23,7 +23,7 @@ CD can be used to continuously deploy ARC artifacts such as metadata export form
 ARC Data Hubs use CD to build and deploy the [ARC-RO-Crate metadata]({{INTERNAL_DEV_REPRESENTATION_RO_CRATE}}) of each commit to a central package registry.
 This way, both [representations of the ARC]({{INTERNAL_DEV_REPRESENTATION}}) are always in sync and accessible, deploying both a user-centric and a machine-readable view on the ARC.
 
-![ARC Data Hubs use CD to build and deploy the ARC-RO-Crate metadata](/arc-website/ci-cd-arc-application.png)
+![ARC Data Hubs use CD to build and deploy the ARC-RO-Crate metadata](/ci-cd-arc-application.png)
 
 ## Continuous Integration
 
@@ -43,4 +43,4 @@ Beyond its core functionality as an ARC Data Hub, it incorporates **CQC** within
 CQC also supports submissions to various endpoint repositories, provided the corresponding validation package and downstream submission application are available.
 This flexible system ensures that ARC submissions meet the necessary standards for different repositories, enabling seamless integration and data sharing across platforms.
 
-![cqc can be used to submit relevant parts of an ARC to endpoint repositories](/arc-website/ci-cd-cqc.png)
+![cqc can be used to submit relevant parts of an ARC to endpoint repositories](/ci-cd-cqc.png)
diff --git a/src/pages/details/arc-data-model.md b/src/pages/details/arc-data-model.md
index 8332d9f..3c1f124 100644
--- a/src/pages/details/arc-data-model.md
+++ b/src/pages/details/arc-data-model.md
@@ -12,24 +12,24 @@ tags: ["RO-Crate", "FAIR digital object","JSON-LD"]
 
 ARC is an implementation of a FAIR Digital Object (FDO), utilizing RO-Crate with Schema.org and Bioschemas objects as its foundation, and further enhancing it with additional metadata and structure. An RO-Crate serves as a research object, composed of a collection of research elements and data, enabling detailed descriptions of these collections. Research elements in this context include samples, measurement data, and other research outputs.
 
-![ARC RO-Crate](/arc-website/arc-ro-crate.png)
+![ARC RO-Crate](/arc-ro-crate.png)
 
 ARC extends the basic RO-Crate concept by incorporating detailed descriptions of the processes that lead to the generation of data. This enhancement allows the data model to represent a complete process graph, encompassing experimental procedures, simulations, analyses, and the interconnections and provenance among them.
 In this model, research elements are the nodes of the process graph, while the connections between them, defined as lab processes, are represented by edges. 
 
-![ARC RO-Crate-Process](/arc-website/ARC-isa-cwl-decorations.png)
+![ARC RO-Crate-Process](/ARC-isa-cwl-decorations.png)
 
 To allow for unambiguous inclusion of data entities into the process graph, Data Fragment Selectors, defined by W3, can be used in.
 Each process can be further specified and annotated with explanatory and descriptive metadata using lists of PropertyValues, enhancing its clarity and traceability.
 
-![Fragment Selector](/arc-website/data-fragment-selector.png)
+![Fragment Selector](/data-fragment-selector.png)
 
 The collection of data fragment selectors for a given dataset is called the datamap. In addition to the selectors, the datamap contains additional information about how to read and interpret the content of the data fragments. Besides this, it carries and annotates data resources which do not originate in the process sequence.
 
-![Datamap](/arc-website/datamap.png)
+![Datamap](/datamap.png)
 
 To specialize ARC for biological data, the widely recognized ISA model (Investigation, Study, Assay) is employed, alongside the abstract Common Workflow Language (CWL) for workflows. The ISA model and CWL provide additional layers of metadata and structure, allowing for more precise definitions of processes and data. Dataset objects within ARC can implement either ISA or CWL interface object definitions, ensuring compatibility and standardization across various biological datasets and workflows.
 
-![ARC RO Crate](/arc-website/arc-ro-crate-profiles.png)
+![ARC RO Crate](/arc-ro-crate-profiles.png)
 
 This approach elevates ARC from merely documenting research objects to providing a full, interconnected representation of the research process, from data generation to analysis, making it a powerful tool for tracing and reproducing scientific investigations.
diff --git a/src/pages/details/arc-representation.md b/src/pages/details/arc-representation.md
index a69be29..240fac9 100644
--- a/src/pages/details/arc-representation.md
+++ b/src/pages/details/arc-representation.md
@@ -8,7 +8,7 @@ image:
 tags: ["RO-Crate", "FAIR Digital Object", "JSON-LD", "XLSX", "CWL"]
 ---
 
-The ARC is a flexible and comprehensive research data management (RDM) framework. It not only facilitates FAIR (Findable, Accessible, Interoperable, Reusable) documentation, storage, and collaboration but also empowers researchers to create their own [FAIR Digital Objects (FDOs)](/arc-website/details/arc-fdo) using a broad set of tools and services, all without being locked into a specific platform or toolset.
+The ARC is a flexible and comprehensive research data management (RDM) framework. It not only facilitates FAIR (Findable, Accessible, Interoperable, Reusable) documentation, storage, and collaboration but also empowers researchers to create their own [FAIR Digital Objects (FDOs)](/details/arc-fdo) using a broad set of tools and services, all without being locked into a specific platform or toolset.
 
 The ARC data model encompasses the necessary entities to document the full research cycle effectively. However, this model can be expressed in various formats, each offering distinct advantages. These different representations enhance accessibility and usability for a variety of users and workflows. Currently, two ARC representations have been specified, and while the unified **ARC Scaffold** is highly encouraged to maintain consistency across user perspectives, domain-specific adaptations are also possible to suit particular needs.
 
@@ -16,7 +16,7 @@ The ARC data model encompasses the necessary entities to document the full resea
 
 The two main ARC representations are the **ARC RO-Crate** and the **ARC Scaffold**. Both adhere to the same underlying data model, making conversion between them straightforward and requiring no complex mapping. This seamless transition ensures frictionless collaboration, even between users who prefer different representations. Think of the ARC RO-Crate as a more machine-friendly, compiled version of the ARC Scaffold, which is geared toward human input and interaction.
 
-![ARC RO Crate](/arc-website/ro-crate-vs-scaffold.png)
+![ARC RO Crate](/ro-crate-vs-scaffold.png)
 
 ### ARC RO-Crate
 
diff --git a/src/pages/details/developer-toolstack.md b/src/pages/details/developer-toolstack.md
index ca25aee..31f5cb7 100644
--- a/src/pages/details/developer-toolstack.md
+++ b/src/pages/details/developer-toolstack.md
@@ -27,7 +27,7 @@ Depending on your programming language, ARCtrl can be found via different packag
 
 ### Handling representations
 
-The ARCtrl library supports a wide set of base operations for working with different [ARC representations](/arc-website/details/arc-representation). ARCtrl can parse ISA metadata files in XLSX format and CWL files in YAML format, resulting in a full parsing of the ARC Scaffold representation. On the other hand, the full scaffold data model can also be transformed to the RO-Crate metadata model and parsed as such. Through this, transition between the two representations is merely a few function calls away. In addition to the RO-Crate and the Scaffold representation, ARCtrl also supports parsing the experimental metadata to ISA-JSON, providing an additional entry and exit point.
+The ARCtrl library supports a wide set of base operations for working with different [ARC representations](/details/arc-representation). ARCtrl can parse ISA metadata files in XLSX format and CWL files in YAML format, resulting in a full parsing of the ARC Scaffold representation. On the other hand, the full scaffold data model can also be transformed to the RO-Crate metadata model and parsed as such. Through this, transition between the two representations is merely a few function calls away. In addition to the RO-Crate and the Scaffold representation, ARCtrl also supports parsing the experimental metadata to ISA-JSON, providing an additional entry and exit point.
 
 ### ARC manipulation
 
@@ -43,7 +43,7 @@ The library guarantees to behave consistently across the different programming e
 
 For this, the source code is written in FSharp. From there it is being compiled to Common Intermediate Language for usage in .NET, and transpiled to Javascript and Python source code using the [Fable compiler](https://github.com/fable-compiler/Fable). As file access can be vastly diverging between different frameworks, especially for javascript, a contract layer was established. This way, every implementation of ARCtrl can decide for itself, how to handle file-system access.
 
-![ARCtrl layers](/arc-website/ARCtrl-layers.png)
+![ARCtrl layers](/ARCtrl-layers.png)
 
 To test the functioning of all of this, especially the cross-compatibility, a comprehensive set of well over 1000 tests was established, which is also being transpiled and run in javascript and python.
 
diff --git a/src/pages/details/documentation-principle.md b/src/pages/details/documentation-principle.md
index d99ec11..b2b933e 100644
--- a/src/pages/details/documentation-principle.md
+++ b/src/pages/details/documentation-principle.md
@@ -19,15 +19,15 @@ To facilitate a shared understanding, a standardized nomenclature is introduced.
 A single ARC encapsulates one investigation. The metadata of an investigation includes a title and a description of its focus. The authors and contributors to the research may include colleagues, measurement facility experts, bioinformaticians, supervisors, and supporting technicians. 
 
 Crucially, the investigation also holds information about the objects or samples under study, which may be grouped into one or more studies. The study metadata describe the samples and observables, especially the processes leading to sample generation. One or more studies may be included in an investigation, depending on how the samples are intended to be processed or analyzed. 
-![Documentation Principle](/arc-website/documentation-principle-study.png)
+![Documentation Principle](/documentation-principle-study.png)
 
 Samples, once created, typically undergo assays, which involve measurements or analyses of samples from one or multiple studies. The assay includes both the data generated and the metadata describing the process. If the samples require special treatment for a specific assay, the relevant metadata should be incorporated into the assay documentation.
-![Documentation Principle](/arc-website/documentation-principle-assay.png)
+![Documentation Principle](/documentation-principle-assay.png)
 
 When computational analysis is performed on a sample or on the data resulting from an assay, this process is referred to as a run.
-![Documentation Principle](/arc-website/documentation-principle-run.png)
+![Documentation Principle](/documentation-principle-run.png)
 A workflow, on the other hand, is the computational protocol detailing how the data is processed, simulated, or analyzed on a computer without actually executing the computation. Since workflows offer significant value for reuse in other datasets, they are documented separately from runs. 
-![Documentation Principle](/arc-website/documentation-principle-workflow.png)
+![Documentation Principle](/documentation-principle-workflow.png)
 
 :::note
 The ARC is designed to document the entire journey (process) from the object of study, through measurements and analysis (as processes) to the final results. This journey represents a process of processes, capturing each stage as part of the broader transformation from observable phenomena to conclusive outcomes. The ARC annotation principle is to add tags on these process for documentation.  
@@ -36,7 +36,7 @@ The ARC is designed to document the entire journey (process) from the object of
 
 (The term "experiment" is avoided here to prevent confusion, as it can intuitively overlap with "investigation," "study," or "assay" depending on context.) 
 
-![Documentation Principle](/arc-website/arc-process-graph.png)
+![Documentation Principle](/arc-process-graph.png)
 
 ## Annotation Principle
 
@@ -48,7 +48,7 @@ In the ARC, metadata is organized in tables. The headers store the keys (tags),
 
 Special header keys have specific meanings, such as sample name, protocol reference, and data.
 
-![Annotation Principle](/arc-website/annotation-principle-figure-1.png)
+![Annotation Principle](/annotation-principle-figure-1.png)
 
 ### ISA Model Key Parametrization
 
diff --git a/src/pages/details/fairness-and-rdm.md b/src/pages/details/fairness-and-rdm.md
index abbb875..089bc6f 100644
--- a/src/pages/details/fairness-and-rdm.md
+++ b/src/pages/details/fairness-and-rdm.md
@@ -24,7 +24,7 @@ The ARC is designed to fully support Research Data Management (RDM) practices an
 
 By integrating ARC into research workflows, researchers can effectively manage data across these stages, ensuring their research is well-organized, accessible, and reusable.
 
-![Research data lifecycle](/arc-website/research-data-lifecycle.png)
+![Research data lifecycle](/research-data-lifecycle.png)
 
 #### Goals of Research Data Management (RDM):
 - **Enhancing research effectiveness and efficiency**: Well-organized data accelerates the research process by making data easier to find, analyze, and reuse.
@@ -76,12 +76,12 @@ Producing FDOs that meet FAIR standards is always worthwhile. FAIRness is a cont
 
 FAIRness can be progressively enhanced over time. It represents a balance between the agile development of research data and the need for scholarly stability. The ARC supports this philosophy by providing researchers with the tools and structure to improve their data’s FAIRness gradually, ensuring maximum value for both the individual researcher and the broader scientific community.
 
-![Gradual FAIRness](/arc-website/fairness-gradual-process.png)
+![Gradual FAIRness](/fairness-gradual-process.png)
 
 ### "Small Data Done Right" is Big Data
 
 When data are well-managed and shared effectively, even small datasets can contribute to large-scale scientific efforts. Combining data across studies requires data-sharing practices that extend beyond the lifespan of individual projects. This reinforces the idea that **research done right is teamwork by default**, and well-structured, shareable data is a cornerstone of collaborative science.
 
-![RDM long tail data](/arc-website/fairness-long-tail-data.png)
+![RDM long tail data](/fairness-long-tail-data.png)
 
 By embracing these principles, ARC fosters a research environment that enhances RDM practices, promotes open science, and supports the continuous improvement of data FAIRness, driving the scientific community forward.
\ No newline at end of file
diff --git a/src/pages/details/organization-principle.md b/src/pages/details/organization-principle.md
index a715052..9661538 100644
--- a/src/pages/details/organization-principle.md
+++ b/src/pages/details/organization-principle.md
@@ -14,7 +14,7 @@ tags: ["community", "organization", "project management"]
 
 The core principle of the ARC is that collected data are stored in directories, while metadata are maintained in accompanying tables that reference and describe the data. This organizational structure is closely aligned with the ISA model, while also incorporating workflows, computational processing, and analysis results.
 
-![ARC scaffold structure](/arc-website/orga-principle-folder2process.png)
+![ARC scaffold structure](/orga-principle-folder2process.png)
 
 The foundational idea behind ARC is to provide a directory scaffold that ensures research data, along with their processing and analysis, are organized in a structured and annotated manner. This scaffold supplies a basic file structure for organizing research locally on a personal machine, as well as on data-producing devices such as measurement instruments or compute servers. A key feature of this system is its ability to seamlessly transfer to the cloud, specifically to a DataHUB instance (e.g., Git-LFS) hosted by an institution or NFDI consortium.
 
@@ -26,7 +26,7 @@ The unified structure of ARC ensures that research can be shared and understood
 
 ARC represents an entire investigation. At the top level, it includes directories named **“studies,” “assays,” “workflows,”** and **“runs,”** along with an **investigation metadata table** that holds all administrative metadata.
 
-![ARC scaffold structure](/arc-website/orga-principle-scaffold.png)
+![ARC scaffold structure](/orga-principle-scaffold.png)
 
 #### Study
 The **studies** folder contains one or more studies, each in its own directory. Each study folder contains:
diff --git a/src/pages/details/validation.md b/src/pages/details/validation.md
index 4f940fb..23a2ee6 100644
--- a/src/pages/details/validation.md
+++ b/src/pages/details/validation.md
@@ -5,7 +5,7 @@ pubDate: 2024-09-10
 description: 'ARCs are evolving FDOs. A mechanism to continuously assess quality metrics of an ARC is indispensable during its lifecycle.'
 author: 'Kevin Schneider'
 image:
-    url: '/arc-website/validation-pull-model.png'
+    url: '/validation-pull-model.png'
     alt: 'A validation package pulls the necessary context for its assertions from the ARC'
 tags: ["validation", "quality control", "unit testing"]
 ---
@@ -72,7 +72,7 @@ This targeted approach minimizes unnecessary workloads for researchers.
 For example, shared sample information across multiple assays or overlapping (meta)data can be reused.
 This ensures that validation efforts are focused on the context-relevant aspects of the ARC, rather than unrelated (meta)data.
 
-![A validation package pulls the necessary context for its assertions from the ARC](/arc-website/validation-pull-model.png)
+![A validation package pulls the necessary context for its assertions from the ARC](/validation-pull-model.png)
 
 In this model, a **validation package** pulls the necessary context from the ARC for its specific assertions.
 This enables a customizable validation process, allowing researchers to maintain high (meta)data quality according to individual requirements, without compromising flexibility.
diff --git a/src/statics.ts b/src/statics.ts
index abc25d1..ebc443c 100644
--- a/src/statics.ts
+++ b/src/statics.ts
@@ -1,5 +1,5 @@
 
-const BASE_PATH = "/arc-website/"
+const BASE_PATH = "/"
 
 export enum URLS {
   INTERNAL_HOME = BASE_PATH,
diff --git a/tailwind.config.mjs b/tailwind.config.mjs
index 59aa88f..2b18603 100644
--- a/tailwind.config.mjs
+++ b/tailwind.config.mjs
@@ -18,17 +18,17 @@ export default {
         },
       },
       {
-        black: {
-          ...require("daisyui/src/theming/themes")["black"],
+        dark: {
+          ...require("daisyui/src/theming/themes")["dark"],
           primary: "#00a896",
           accent: "#c70039",
           warning: '#ffbe00',
           error: '#ff5861',
           info: '#00b6ff',
-          success: '#00a96e'
+          success: '#00a96e',
         },
       }
     ],
   },
-  darkMode: ['class', '[data-theme="black"]']
+  darkMode: ['class', '[data-theme="dark"]']
 }