Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Confirming that I have tested/looked for (large screen size): |
|
I had checked this PR before the optimizations and everything was working properly, and again I'm here to confirm everything looks great! What I tested:
|
|
is updating our contributor/translator guide a pre-req to merging this? Should we have that available first, @delucis @yan-thomas ? |
I believe @delucis made all the necessary changes to these, couldn't find anywhere else in our |
|
DOES THIS MEAN I APPROVE???? |
sarah11918
left a comment
There was a problem hiding this comment.
I have not found any reason not to approve this...
Great work @delucis & @bholmesdev !
Let's ... NOT do this again soon?? 😅
What kind of changes does this PR include?
Description
docscollection under/src/content/docs/. This preserves the existing i18n folder structure, unchanged.typefrontmatter param. Thistypereplaces thelayoutparam, and can be omitted when using theMainLayout. These types can be found browsing the schemas undersrc/content/config.ts. I'm curious if the docs team has ideas for CONTRIBUTING updates or further refactors here!globto usegetCollection.[lang]/[...slug].astroto render content collection entries. This also allowed for fallbacks and page routes to be generated in the same place. This also maps thetypefrontmatter param to the correct layout.splitSlugFromLangutil. This helps with parsing the language out of the generated content collectionslug.[...enRedirectSlug]and[enBaseLevelRedirectSlug]. This was purely for readability debugging our new slug generation routes. I'll differ to @delucis for changing this naming back.Chores
markdownconfig to use newgfmandsmartypantsflags