docusaurus/website/_dogfooding
2023-01-19 17:08:24 +01:00
..
_asset-tests
_blog tests chore: revert docs(website): use MDX comments instead of HTML comments (#8517) 2023-01-06 17:07:53 +01:00
_docs tests docs: blog + community + dogfood docs should use .mdx extension (#8507) 2023-01-04 19:59:56 +01:00
_pages tests feat(eslint-plugin): new prefer-docusaurus-heading rule (#8384) 2023-01-19 17:08:24 +01:00
_partials docs: blog + community + dogfood docs should use .mdx extension (#8507) 2023-01-04 19:59:56 +01:00
clientModuleCSS.css chore: upgrade lint-staged and globs (#6369) 2022-01-15 16:33:09 +08:00
clientModuleExample.ts refactor(pwa): simplify registerSW code, fix ESLint errors (#7579) 2022-06-07 21:42:17 +08:00
docs-tests-sidebars.js feat(docs,blog,pages): add support for "unlisted" front matter - hide md content in production (#8004) 2022-11-03 14:31:41 +01:00
dogfooding.config.js feat(docs,blog,pages): add support for "unlisted" front matter - hide md content in production (#8004) 2022-11-03 14:31:41 +01:00
dogfooding.css fix(cssnano-preset): disable z-index minification (#7593) 2022-06-15 12:13:25 +02:00
README.mdx docs: blog + community + dogfood docs should use .mdx extension (#8507) 2023-01-04 19:59:56 +01:00
testSwizzleThemeClassic.mjs refactor(theme): split admonitions, make swizzle easier, better retrocompatibility (#7945) 2022-09-07 17:49:44 +02:00

---
test: 'some test front matter'
---

# Docusaurus website dogfooding

This is where we test edge cases of Docusaurus by using fancy configs, ensuring they all don't fail during a real site build.

Eventually, we could move these tests later so another test site? Note there is value to keep seeing the live result of those tests.

Fancy things we can test for here:

- Plugin Multi-instance
- Webpack configs
- \_ prefix convention
- Huge sidebars impact
- Using folders with spaces on purpose
- Importing MD docs that are out of content plugin folders as partials (such as this README file!)