docusaurus/website/_dogfooding
Joshua Chen 87a486a02f
chore: generate dogfooding test for long pathname during CI (#5977)
* chore: generate dogfooding test for long pathname during CI

* Fix test

* Fix again
2021-11-20 14:18:50 +08:00
..
_asset-tests feat(core): allow sourcing from multiple static directories (#4095) 2021-11-18 22:26:26 +08:00
_blog tests feat(content-blog): new readingTime plugin option (#5702) 2021-10-21 15:26:10 +02:00
_docs tests fix(ideal-image): fix IdealImage in dev not handling ES import images properly (#5760) 2021-10-21 17:22:49 +02:00
_pages tests chore: generate dogfooding test for long pathname during CI (#5977) 2021-11-20 14:18:50 +08:00
_partials feat(v2): allow specifying TOC max depth (themeConfig + frontMatter) (#5578) 2021-09-29 11:19:11 +02:00
clientModuleExample.ts chore(website): enable eslint in website (#5889) 2021-11-06 19:04:45 +08:00
docs-tests-sidebars.js chore(website): enable eslint in website (#5889) 2021-11-06 19:04:45 +08:00
docs-tests-symlink fix: ability to link md files with relative paths when paths contain space (#5270) 2021-08-02 18:02:01 +02:00
dogfooding.config.js chore(website): enable eslint in website (#5889) 2021-11-06 19:04:45 +08:00
README.md feat: mdx loader fallback, allow importing mdx docs from anywhere (#5299) 2021-08-06 11:32:22 +02:00

test
some test frontmatter

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
  • Symlinks support
  • 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!)