Skip to content

Changes

Page history
Update Astro and MDX files from Directus authored by Flupsi's avatar Flupsi
Show whitespace changes
Inline Side-by-side
Astro-and-MDX-files-from-Directus.md
View page @ a81a0b4e
https://docs.astro.build/en/guides/markdown-content/#mdx-features
I am currently experimenting with Astro: https://github.com/upsiflu/astro-blog
```mermaid ```mermaid
graph TD graph TD
A[CMS] --- B{Data Model - Directus} A[CMS] --- B{Data Model - Directus}
...@@ -33,6 +29,10 @@ graph TD ...@@ -33,6 +29,10 @@ graph TD
* [ ] Drafts can be specified with the `draft: true` MD(x) frontmatter directive and will be automatically hidden by Astro. (TODO: Check what the corresponding convention in Directusland is, and if we can translate losslessly) * [ ] Drafts can be specified with the `draft: true` MD(x) frontmatter directive and will be automatically hidden by Astro. (TODO: Check what the corresponding convention in Directusland is, and if we can translate losslessly)
* [ ] If each site has a unique slug, we can realise a flat sitemat for authored content (in addition to a hierarchical sitemap where we can have logbook/x). TODO: Who should generate the slugs? (a) Directus, adding a non-writable field via a `flow` (b) Astro, using some slug library (c) the author, via a writeable field that only allows url-safe characters? I'm leaning towards (a) for consistency and uniqueness guarantees, and to establish directus as single-source-of-truth. * [ ] If each site has a unique slug, we can realise a flat sitemat for authored content (in addition to a hierarchical sitemap where we can have logbook/x). TODO: Who should generate the slugs? (a) Directus, adding a non-writable field via a `flow` (b) Astro, using some slug library (c) the author, via a writeable field that only allows url-safe characters? I'm leaning towards (a) for consistency and uniqueness guarantees, and to establish directus as single-source-of-truth.
# MDX Magic
https://docs.astro.build/en/guides/markdown-content/#mdx-features
## Customization ## Customization
Defining blocks and components in the CMS is preferrable to hardcoding them in .astro. Directus can edit .mdx files, and Astro can do a lot with these, so we get the following features to allow block customization and composition: Defining blocks and components in the CMS is preferrable to hardcoding them in .astro. Directus can edit .mdx files, and Astro can do a lot with these, so we get the following features to allow block customization and composition:
...@@ -67,3 +67,7 @@ https://blog.lunarbyte.io/2021/08/11/directus-content-translations/ ...@@ -67,3 +67,7 @@ https://blog.lunarbyte.io/2021/08/11/directus-content-translations/
Issue discussion: Issue discussion:
https://github.com/directus/directus/discussions/6654 https://github.com/directus/directus/discussions/6654
> How should multilingual content be represented in Astro Content Collections?
Conventionally, we'd have `content/leaflets/en/<id>` and `content/logbook/en/<id>`
\ No newline at end of file