| ... | ... | @@ -16,3 +16,31 @@ Defining blocks and components in the CMS is preferrable to hardcoding them in . |
|
|
|
1. **Tag renderer:** Astro can override renderers for individual tags. For example, we can replace the default realisation of `\*\*\*` as `<hr>` [by something else,](https://mdxjs.com/table-of-components/) for example an .astro component.
|
|
|
|
2. **Custom composable blocks:** We can define a directory `/block` to let CMS users author MDX fragments that can be reused in pages or other components, reducing the reliance on hardcoded .astro templates. Combined with (1.), we can expose a subset of the tag renderers as customizable .mdx files living in a `/tag` directory.
|
|
|
|
3. **Markdown/.mdx plugins:** Astro supports<span dir=""> third-party </span>[remark](https://github.com/remarkjs/remark)<span dir=""> and </span>[rehype](https://github.com/rehypejs/rehype)<span dir=""> plugins</span>.
|
|
|
|
|
|
|
|
# Astro features
|
|
|
|
|
|
|
|
* [Automatic Sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/#i18n)
|
|
|
|
* Automatic Routing (as long as we stay in SSG territory)
|
|
|
|
|
|
|
|
# Multilingual Content and Ui
|
|
|
|
|
|
|
|
#### Template/Ui i18n
|
|
|
|
|
|
|
|
I found https://astro-i18next.yassinedoghri.com/\
|
|
|
|
which seems amazing for Ui and template localization (time, date, pluralization etc.) but what about blog posts that are available in several languages?
|
|
|
|
|
|
|
|
#### Multilingual Content
|
|
|
|
|
|
|
|
> How does the Directus Editor handle multilingual text?
|
|
|
|
|
|
|
|
Problem description:
|
|
|
|
|
|
|
|
https://github.com/directus/directus/discussions/10362
|
|
|
|
|
|
|
|
Workaround:
|
|
|
|
|
|
|
|
https://blog.lunarbyte.io/2021/08/11/directus-content-translations/
|
|
|
|
|
|
|
|
Issue discussion:
|
|
|
|
|
|
|
|
https://github.com/directus/directus/discussions/6654 |
|
|
\ No newline at end of file |
