diff --git a/astro.config.mts b/astro.config.mts
index a8d3352c7..9c54c8c66 100644
--- a/astro.config.mts
+++ b/astro.config.mts
@@ -51,6 +51,24 @@ export default defineConfig({
collapsed: true,
autogenerate: { directory: 'guides' },
},
+ {
+ label: 'Resources',
+ // Collapse the group by default.
+ collapsed: true,
+ autogenerate: { directory: 'resources' },
+ },
+ {
+ label: 'Git',
+ // Collapse the group by default.
+ collapsed: true,
+ autogenerate: { directory: 'git' },
+ },
+ {
+ label: 'CWL',
+ // Collapse the group by default.
+ collapsed: true,
+ autogenerate: { directory: 'cwl' },
+ },
{
label: 'Fundamentals',
// Collapse the group by default.
diff --git a/src/content/docs/guides/arc-commander-quick-start-expert.md b/src/content/docs/arc-commander/arc-commander-quick-start-expert.md
similarity index 100%
rename from src/content/docs/guides/arc-commander-quick-start-expert.md
rename to src/content/docs/arc-commander/arc-commander-quick-start-expert.md
diff --git a/src/content/docs/guides/arc-commander-quick-start.mdx b/src/content/docs/arc-commander/arc-commander-quick-start.mdx
similarity index 100%
rename from src/content/docs/guides/arc-commander-quick-start.mdx
rename to src/content/docs/arc-commander/arc-commander-quick-start.mdx
diff --git a/src/content/docs/arc-commander/before-we-start.mdx b/src/content/docs/arc-commander/before-we-start.mdx
index 17d1ac8d1..eb95a962d 100644
--- a/src/content/docs/arc-commander/before-we-start.mdx
+++ b/src/content/docs/arc-commander/before-we-start.mdx
@@ -7,7 +7,7 @@ lastUpdated: 2023-06-14
After the setup steps, you're all set and ready to start using the ARC Commander. 🎉
:::tip
-We recommend trying the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/guides/arc-commander-quick-start) for your first steps with the ARC Commander.
+We recommend trying the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/arc-commander/arc-commander-quick-start) for your first steps with the ARC Commander.
:::
:::tip
@@ -17,7 +17,7 @@ After the quickstarts, we strongly recommend to read the in-depth ARC Commander
## Notes on ARC Commander Guides
-- For most steps in this manual and in the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/guides/arc-commander-quick-start), it is assumed, that you opened a [shell or command prompt](/nfdi4plants.knowledgebase/guides/tutorial-command-line) within a directory you want to initiate as an ARC
+- For most steps in this manual and in the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/arc-commander/arc-commander-quick-start), it is assumed, that you opened a [shell or command prompt](/nfdi4plants.knowledgebase/fundamentals/tutorial-command-line) within a directory you want to initiate as an ARC
- In the shell, `arc` defines the path to the ARC Commander executable (e.g. on Windows "C:\Users\userA\programs\ArcCommander\arc.exe").
- Note that each input that contains non-literal characters must be encapsulated in "quotation marks" when entered within the shell. This also applies when using the editor for numerals that are no numbers (dates, phone numbers, etc.).
diff --git a/src/content/docs/arc-commander/index.mdx b/src/content/docs/arc-commander/index.mdx
index 3afe58341..694001fd8 100644
--- a/src/content/docs/arc-commander/index.mdx
+++ b/src/content/docs/arc-commander/index.mdx
@@ -32,7 +32,7 @@ Unless you actively request it to, the ARC Commander does not delete, modify or
## Do I have to use the ARC Commander?
No. As with most tools and services developed in DataPLANT, you are not obliged to use the ARC Commander to benefit from DataPLANT's support in [FAIR RDM](/nfdi4plants.knowledgebase/fundamentals/research-data-management).
-However, we'd highly recommend to check it following the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/guides/arc-commander-quick-start).
+However, we'd highly recommend to check it following the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/arc-commander/arc-commander-quick-start).
The alternative would be to
@@ -48,7 +48,7 @@ The ARC Commander runs on current Windows, Mac and Linux operating systems. The
For details, please
-- try out the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/guides/arc-commander-quick-start),
+- try out the [ARC Commander QuickStart](/nfdi4plants.knowledgebase/arc-commander/arc-commander-quick-start),
- check the [GitHub repository](https://github.com/nfdi4plants/ARCCommander) to download and install the latest ARC Commander release on your device, or
- explore this ARC Commander Manual for in-depth details.
diff --git a/src/content/docs/guides/arc-enabling-platforms.md b/src/content/docs/core-concepts/arc-enabling-platforms.md
similarity index 99%
rename from src/content/docs/guides/arc-enabling-platforms.md
rename to src/content/docs/core-concepts/arc-enabling-platforms.md
index 2f99e927e..0594550ab 100644
--- a/src/content/docs/guides/arc-enabling-platforms.md
+++ b/src/content/docs/core-concepts/arc-enabling-platforms.md
@@ -79,7 +79,7 @@ The standardized ARC structure helps with routine computations:
- The ARC's simple [directory structure](/nfdi4plants.knowledgebase/core-concepts/arc) itself helps building routines, no matter whether you work with code or licensed software. Across projects, you and your collaborators know, where to find metadata and raw data, where to store processed data and results.
- The ARC facilitates task automation such as quality control and validation within one project or across multiple ARCs covering routine measurements
-- Code-based computations can be designed as reusable and reproducible workflows using [Common Workflow Language (CWL)](/nfdi4plants.knowledgebase/guides/data-analysis/computational-workflows)
+- Code-based computations can be designed as reusable and reproducible workflows using [Common Workflow Language (CWL)](/nfdi4plants.knowledgebase/cwl)
### Data publication
@@ -144,7 +144,7 @@ Following the exemplary scenario A, you could setup the ARC for your collaborati
Alternatively, collaborators already working with ARCs could invite you to "their" ARC (exemplary scenario B). They can independently set up the ARC and fill metadata (4) based on your prepared templates (3).
:::tip
-In scenario B the collaborator might invite you to a very large ARC with data not really relevant for your platform-specific collaboration. In this case you might want to [exclude irrelevant data or avoid downloading large data](/nfdi4plants.knowledgebase/guides/arc-gitignore) when syncing the ARC.
+In scenario B the collaborator might invite you to a very large ARC with data not really relevant for your platform-specific collaboration. In this case you might want to [exclude irrelevant data or avoid downloading large data](/nfdi4plants.knowledgebase/git/git-gitignore) when syncing the ARC.
:::
**Can I retain my established naming convention for project management and data storage?**
diff --git a/src/content/docs/guides/data-analysis/computational-workflows/cwl-examples.md b/src/content/docs/cwl/cwl-examples.md
similarity index 100%
rename from src/content/docs/guides/data-analysis/computational-workflows/cwl-examples.md
rename to src/content/docs/cwl/cwl-examples.md
diff --git a/src/content/docs/guides/data-analysis/computational-workflows/cwl-introduction.md b/src/content/docs/cwl/cwl-introduction.md
similarity index 100%
rename from src/content/docs/guides/data-analysis/computational-workflows/cwl-introduction.md
rename to src/content/docs/cwl/cwl-introduction.md
diff --git a/src/content/docs/guides/data-analysis/computational-workflows/cwl-metadata.md b/src/content/docs/cwl/cwl-metadata.md
similarity index 98%
rename from src/content/docs/guides/data-analysis/computational-workflows/cwl-metadata.md
rename to src/content/docs/cwl/cwl-metadata.md
index 09c1761de..4fb13aab9 100644
--- a/src/content/docs/guides/data-analysis/computational-workflows/cwl-metadata.md
+++ b/src/content/docs/cwl/cwl-metadata.md
@@ -7,8 +7,7 @@ authors:
# CWL Metadata
-Metadata plays a crucial role in enhancing the comprehensibility of CWL files. By embedding additional information about the performer and the process within the metadata,
-researchers can create a more comprehensive and informative description of their workflows.
+Metadata plays a crucial role in enhancing the comprehensibility of CWL files. By embedding additional information about the performer and the process within the metadata, researchers can create a more comprehensive and informative description of their workflows.
- Performer Metadata:
diff --git a/src/content/docs/guides/data-analysis/computational-workflows/cwl-runner-installation.md b/src/content/docs/cwl/cwl-runner-installation.md
similarity index 100%
rename from src/content/docs/guides/data-analysis/computational-workflows/cwl-runner-installation.md
rename to src/content/docs/cwl/cwl-runner-installation.md
diff --git a/src/content/docs/cwl/index.mdx b/src/content/docs/cwl/index.mdx
new file mode 100644
index 000000000..ff25a627e
--- /dev/null
+++ b/src/content/docs/cwl/index.mdx
@@ -0,0 +1,37 @@
+---
+title: Computational Workflows
+lastUpdated: 2023-02-05
+authors:
+ - kevin-frey
+---
+import { CardGrid } from '@astrojs/starlight/components';
+import { LinkCard } from '@astrojs/starlight/components';
+
+Welcome to the section on Computational Workflows (CWL).
+
+Here you can find documentation about CWL and best practices. If you want to get a picture of CWL first, please check out the [CWL Main Page](https://www.commonwl.org/).
+
+Please explore the sections on the left to find guides on
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/src/content/docs/guides/best-practices-for-data-annotation.md b/src/content/docs/fundamentals/best-practices-for-data-annotation.md
similarity index 100%
rename from src/content/docs/guides/best-practices-for-data-annotation.md
rename to src/content/docs/fundamentals/best-practices-for-data-annotation.md
diff --git a/src/content/docs/fundamentals/data-management-plan.mdx b/src/content/docs/fundamentals/data-management-plan.mdx
index 711445345..5b27f1740 100644
--- a/src/content/docs/fundamentals/data-management-plan.mdx
+++ b/src/content/docs/fundamentals/data-management-plan.mdx
@@ -48,7 +48,7 @@ DataPLANT helps the community by providing [DataPLAN](https://plan.nfdi4plants.o
## Follow-up
- If you are looking for DataPLAN, the Data Management Plan (DMP) generator of DataPLANT, you can find it [here](https://plan.nfdi4plants.org).
-- If you are looking for an article about DataPLAN, you can find it [here](/nfdi4plants.knowledgebase/guides/dataplan).
+- If you are looking for an article about DataPLAN, you can find it [here](/nfdi4plants.knowledgebase/resources/dataplan).
## Sources and further information
diff --git a/src/content/docs/fundamentals/metadata.mdx b/src/content/docs/fundamentals/metadata.mdx
index 815f4a980..0bc06c9fd 100644
--- a/src/content/docs/fundamentals/metadata.mdx
+++ b/src/content/docs/fundamentals/metadata.mdx
@@ -54,7 +54,7 @@ The diversity of metadata types, sources and stakeholders highlights that collec
Metadata stakeholders from different environments have different understandings of what metadata is required for comprehension of the annotated data. As plant biologists we probably agree that, when retrieving data from a public repository or publication, it is beneficial to know what type of measurement was performed on what species of plants. By contrast, a computational biologist and a librarian might emphasize the importance of the programming environment required to interpret a script or the contributing authors and licenses, respectively.
As plant biologists, we frequently experience how hard it is (if at all possible) to reproduce an experiment described with too little information in a publication. So, the more metadata the merrier – wouldn't it be great to capture *all* metadata about a project? Realistically we can only collect a portion of metadata. To guide users on what metadata is encouraged to collect, different domains of data experts have formulated these requirements into what is often referred to as "metadata standards" or "minimum information standards".
-Examples for bibliographic and administrative metadata standards include [DublinCore](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/) and [DataCite](https://schema.datacite.org). Prominent standards to annotate data relevant to different plant science domains are grouped under the "Minimum Information for Biological and Biomedical Investigations" ([MIBBI](https://fairsharing.org/3518d)) and define e.g. minimum information about a high-throughput SEQuencing Experiment ([MINSEQE](https://www.fged.org/projects/minseqe)), Proteomics Experiment ([MIAPE](http://www.psidev.info/miape)) or a Plant Phenotyping Experiment ([MIAPPE](https://www.miappe.org)). There are many more metadata standards available which can be explored at [fairsharing.org]. You can also use DataPLANT's [Metadata recommendation quiz](/nfdi4plants.knowledgebase/guides/metadata-quiz) for finding suitable metadata standards, metadata checklists for repositories as well as corresponding [Swate](/nfdi4plants.knowledgebase/swate) templates for your data.
+Examples for bibliographic and administrative metadata standards include [DublinCore](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/) and [DataCite](https://schema.datacite.org). Prominent standards to annotate data relevant to different plant science domains are grouped under the "Minimum Information for Biological and Biomedical Investigations" ([MIBBI](https://fairsharing.org/3518d)) and define e.g. minimum information about a high-throughput SEQuencing Experiment ([MINSEQE](https://www.fged.org/projects/minseqe)), Proteomics Experiment ([MIAPE](http://www.psidev.info/miape)) or a Plant Phenotyping Experiment ([MIAPPE](https://www.miappe.org)). There are many more metadata standards available which can be explored at [fairsharing.org]. You can also use DataPLANT's [Metadata recommendation quiz](/nfdi4plants.knowledgebase/resources/metadata-quiz) for finding suitable metadata standards, metadata checklists for repositories as well as corresponding [Swate](/nfdi4plants.knowledgebase/swate) templates for your data.
The metadata standards can be regarded as "checklists", which, when followed, provide that the data is annotated with the required metadata attributes to make it comprehensible at least in the current context.
diff --git a/src/content/docs/fundamentals/public-data-repositories.mdx b/src/content/docs/fundamentals/public-data-repositories.mdx
index 0d9293a2b..3bd0b7730 100644
--- a/src/content/docs/fundamentals/public-data-repositories.mdx
+++ b/src/content/docs/fundamentals/public-data-repositories.mdx
@@ -46,7 +46,7 @@ Examples for general-purpose repositories include
The following resources provide good starting points to seek a suitable repository for your research data.
-- DataPLANT's [Metadata recommendation quiz](/nfdi4plants.knowledgebase/guides/metadata-quiz)
+- DataPLANT's [Metadata recommendation quiz](/nfdi4plants.knowledgebase/resources/metadata-quiz)
- FAIRsharing: https://fairsharing.org
- re3data (Registry of Research Data Repositories): https://www.re3data.org
- Overview of EMBL-EBI repositories: https://www.ebi.ac.uk/services/all
diff --git a/src/content/docs/guides/tutorial-command-line.md b/src/content/docs/fundamentals/tutorial-command-line.md
similarity index 100%
rename from src/content/docs/guides/tutorial-command-line.md
rename to src/content/docs/fundamentals/tutorial-command-line.md
diff --git a/src/content/docs/guides/tutorial-markdown.md b/src/content/docs/fundamentals/tutorial-markdown.md
similarity index 100%
rename from src/content/docs/guides/tutorial-markdown.md
rename to src/content/docs/fundamentals/tutorial-markdown.md
diff --git a/src/content/docs/guides/arc-gitignore.mdx b/src/content/docs/git/git-gitignore.mdx
similarity index 100%
rename from src/content/docs/guides/arc-gitignore.mdx
rename to src/content/docs/git/git-gitignore.mdx
diff --git a/src/content/docs/guides/arc-lfs.mdx b/src/content/docs/git/git-lfs.mdx
similarity index 100%
rename from src/content/docs/guides/arc-lfs.mdx
rename to src/content/docs/git/git-lfs.mdx
diff --git a/src/content/docs/guides/arc-syncing-recommendation.mdx b/src/content/docs/git/git-syncing-recommendation.mdx
similarity index 100%
rename from src/content/docs/guides/arc-syncing-recommendation.mdx
rename to src/content/docs/git/git-syncing-recommendation.mdx
diff --git a/src/content/docs/guides/git-troubleshooting.md b/src/content/docs/git/git-troubleshooting.md
similarity index 99%
rename from src/content/docs/guides/git-troubleshooting.md
rename to src/content/docs/git/git-troubleshooting.md
index d21d0f6b3..506643c95 100644
--- a/src/content/docs/guides/git-troubleshooting.md
+++ b/src/content/docs/git/git-troubleshooting.md
@@ -311,7 +311,7 @@ This might however pose a safety risk. Please read the details here: https://www
### Git LFS
-[Git LFS](/nfdi4plants.knowledgebase/guides/arc-lfs) is basically the system in the back to simplify working with git and (ARCs containing) large data files.
+[Git LFS](/nfdi4plants.knowledgebase/git/git-lfs) is basically the system in the back to simplify working with git and (ARCs containing) large data files.
ARC commander and ARCitect offer options to download (clone) an ARC without large files; speeding up the process and avoiding waste of data storage, if you are only interested e.g. in the metadata.
If you have downloaded (cloned) an ARC without large files and try to upload it to a new location (i.e. new remote due to a transfer to other user, group, etc.), you will see the following or similar error
diff --git a/src/content/docs/guides/arc-working-with-branches.mdx b/src/content/docs/git/git-working-with-branches.mdx
similarity index 100%
rename from src/content/docs/guides/arc-working-with-branches.mdx
rename to src/content/docs/git/git-working-with-branches.mdx
diff --git a/src/content/docs/guides/arc-adding-external-data.mdx b/src/content/docs/guides/arc-adding-external-data.mdx
index 17a95c3e5..c9087f697 100644
--- a/src/content/docs/guides/arc-adding-external-data.mdx
+++ b/src/content/docs/guides/arc-adding-external-data.mdx
@@ -1,5 +1,5 @@
---
-title: Adding external data to the ARC
+title: External Data
lastUpdated: 2023-07-07
authors:
- dominik-brilhaus
@@ -39,5 +39,5 @@ As with any other routine used by researchers to share scientific results and da
:::
:::tip
-You can add datasets to the [.gitignore](/nfdi4plants.knowledgebase/guides/arc-gitignore) file, if you are unsure about the conditions to reuse data from an external source.
+You can add datasets to the [.gitignore](/nfdi4plants.knowledgebase/git/git-gitignore) file, if you are unsure about the conditions to reuse data from an external source.
:::
\ No newline at end of file
diff --git a/src/content/docs/guides/arc-cwl.mdx b/src/content/docs/guides/arc-cwl.mdx
new file mode 100644
index 000000000..7ca114c60
--- /dev/null
+++ b/src/content/docs/guides/arc-cwl.mdx
@@ -0,0 +1,7 @@
+---
+title: CWL
+---
+
+import CwlIndex from '../cwl/index.mdx'
+
+
\ No newline at end of file
diff --git a/src/content/docs/guides/arc-locations.md b/src/content/docs/guides/arc-storing-arcs.md
similarity index 91%
rename from src/content/docs/guides/arc-locations.md
rename to src/content/docs/guides/arc-storing-arcs.md
index e9d03a0d9..074e8ed7e 100644
--- a/src/content/docs/guides/arc-locations.md
+++ b/src/content/docs/guides/arc-storing-arcs.md
@@ -1,5 +1,5 @@
---
-title: Managing ARCs across locations
+title: Storing ARCs
lastUpdated: 2024-07-17
authors:
- dominik-brilhaus
@@ -22,8 +22,8 @@ A few things are important when maintaining ARCs in multiple locations:
1. Try to keep your ARC in sync via the DataHUB
2. Make sure to sync large files properly
-As with any cloud service, when a single file is edited from multiple locations, you can run into merge conflicts. To avoid these, make sure to regularly [sync your ARC with the DataHUB](/nfdi4plants.knowledgebase/guides/arc-syncing-recommendation) and from there sync with your (other) locations before adding or editing data.
-In order to have the large files only where you need them and not where you do not (e.g. your personal computer), the ARC and DataHUB implement the LFS (Large file storage) system. The ARCitect and ARC commander provide options to properly handle [LFS-tagged files](/nfdi4plants.knowledgebase/guides/arc-lfs).
+As with any cloud service, when a single file is edited from multiple locations, you can run into merge conflicts. To avoid these, make sure to regularly [sync your ARC with the DataHUB](/nfdi4plants.knowledgebase/git/git-syncing-recommendation) and from there sync with your (other) locations before adding or editing data.
+In order to have the large files only where you need them and not where you do not (e.g. your personal computer), the ARC and DataHUB implement the LFS (Large file storage) system. The ARCitect and ARC commander provide options to properly handle [LFS-tagged files](/nfdi4plants.knowledgebase/git/git-lfs).