-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(js): Move some configuration pages to "Best Practices" #9571
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 1.14kB ⬆️
|
58c98d0
to
827c62f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that looks really good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
Description of changes
Some pages in "Configuration" do not really contain configuration examples, but offer more of a "guideline". Users might search for usage examples for "Micro Frontends" or "Browser Extensions". Therefore, "Best Practices" are created. Talked with @HazAT and @mydea about this.