-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate website to astro #2564
Comments
I'd love to be part of this effort. |
@rishi-raj-jain thanks for your intrest, I did go through this a while ago but there was some deal breaking issues #2562
So I don't think this is something we can do right now |
Why's that the case? I believe you can use https://starlight.astro.build and just create folders for versioning, ain't it? |
Yeah we can just need to then do the selection ourself. The first item was the biggest deal breaker the version might just need more or less work from us |
Progress for #2564 Changes: - Decided to cut versioning for now. Starlight doesn't support well now and would be a decent amount of work. Our doc have been quite stable and this slows down the build significantly.\ The plan is as follow 1. Merge this as a parallel build to the docusaurus website 2. Add blog back 3. Cleanup things (like migrate more things out of fluentui react components) 4. Switch the website to use this one 5. If we are happy delete docusaurus
progress for #2564 - Get rid of fluent ui jsx apart from the playground as it cannot be SSr with astro - Use pure astro components for everything which force them to be fully rendered on the UI
Progress for #2564 Made the header responsive. Fixed up some styles issues/improved a few things Added tailwind.css to allow some simpler responsive based css class utils to be used instead of having to repeat the common things.
Current setup makes it very hard to iterate and see output in website as you have to always `pnpm copy` after a change last item for microsoft#2564
Progress for microsoft#2564 Changes: - Decided to cut versioning for now. Starlight doesn't support well now and would be a decent amount of work. Our doc have been quite stable and this slows down the build significantly.\ The plan is as follow 1. Merge this as a parallel build to the docusaurus website 2. Add blog back 3. Cleanup things (like migrate more things out of fluentui react components) 4. Switch the website to use this one 5. If we are happy delete docusaurus
) progress for microsoft#2564 - Get rid of fluent ui jsx apart from the playground as it cannot be SSr with astro - Use pure astro components for everything which force them to be fully rendered on the UI
Progress for microsoft#2564 Made the header responsive. Fixed up some styles issues/improved a few things Added tailwind.css to allow some simpler responsive based css class utils to be used instead of having to repeat the common things.
Current setup makes it very hard to iterate and see output in website as you have to always `pnpm copy` after a change last item for microsoft#2564
After some quick investigation migrating to astro would both improve build performance and runtime performance.
Astro main selling point is everything is rendered on the server(unless go through extra step to have dynamic content)
This means it result in a completely static website without the need for javascript. Somethings like light/dark theme switch still use js but the core of the website is available.
Pros:
Issues:
Tasks
The text was updated successfully, but these errors were encountered: