Sébastien Lorber

yes 👍 good solution Wonder if we shouldn't add this in core to ensure Docusaurus users would at most use a single version of React Although the path may vary...

> unlisted - The post will be accessible by directly visiting the URL but will not show up in the sidebar in the final build; during local development, the post...

Thanks for the feedback @jodyheavener Yes we should provide this feature as a follow-up of https://github.com/facebook/docusaurus/pull/6457, as it's quite difficult to achieve this properly in userland. We can exclude unlisted...

> Hey! We respect every restrictions and metadatas (noindex, robots.txt, etc.) by default. You can freely set those on the Docusaurus side and we won't index those pages. Thanks @shortcuts...

I see thanks :)

Yes that makes sense. We have a few cases where we should probably try to update the webpack compiler config. Similarly, if you swizzle a component while your dev server...

What prevents you from using a plugin instead? The API is not easy to discover but I think this impl should be good enough? ```js function pluginMonetization(context, options) { return...

What about just using the synthetic boottrap plugin above to provide a `siteConfig.head` or `siteConfig.headTags` API? Like suggested here: https://github.com/facebook/docusaurus/issues/8049#issuecomment-1239493341 In the end it's the most flexible way to add...

Similarly, it can also be handled in the core synthetic bootstrap plugin: ```js export function createBootstrapPlugin({ siteDir, siteConfig, }: LoadContext): LoadedPlugin { const { stylesheets, scripts, head, // { const...

> I'm guessing that all users are somehow using the createBootstrapPlugin and they just don't know it? Exactly: all sites implicitly have this plugin by default. > I don't know...