[moisbo]

This pull request updates the architecture documentation and related UI to clarify and expand on the storage layer options, improve terminology consistency, and enhance the visual representation of storage connections. The main changes are focused on the Architecture.astro component and minor formatting improvements in WhyCrateWorks.astro.

Architecture documentation and diagram improvements:

• Updated the storage layer description and sub-options in the layers array to clarify the role of OCFL, add RaspboCrate as an option, and improve naming consistency (e.g., "LDaC", "Nabu") (src/components/Architecture.astro).
• Enhanced the architecture flowchart by:
  • Renaming nodes for consistency (e.g., "LDaC", "Nabu", "RaspboCrate").
  • Adding new storage types: "OCFL", "AWS S3", and "Flat Folders".
  • Illustrating explicit connections between repositories, storage types, and the API.
  • Updating link styles and class definitions for the new nodes (src/components/Architecture.astro).

Content and formatting improvements:

• Improved the explanation of RO-Crate and API in WhyCrateWorks.astro by adding spacing and emphasis for better readability (src/components/WhyCrateWorks.astro).

[johnf]

Just checking is LDaC right or should it be LDaCA?

[johnf]

Just checking is LDaC right or should it be LDaCA?

[moisbo]

Just checking is LDaC right or should it be LDaCA?

We have ldac-api that we are sharing accross LDaCA. For example work on ARDS/Batchelor/LDaCA use ldac-api. Now RAPID also used ldac-api but they since have forked it and changed it. So unsure!