strict

strict is the future stricter tier for repositories that want more opinionated Docusaurus-site enforcement.

What it configures today

strict includes all of recommended, plus the stricter Docusaurus page-module and site-source CSS rules:

• no-conflicting-config-link-props
• no-empty-config-link-destinations
• no-empty-config-link-labels
• no-conflicting-theme-config-metadata-keys
• no-empty-head-tags
• no-duplicate-footer-column-titles
• no-duplicate-footer-link-item-destinations
• no-duplicate-footer-link-item-labels
• no-duplicate-head-tags
• no-duplicate-navbar-item-destinations
• no-duplicate-i18n-locales
• no-duplicate-navbar-item-labels
• no-duplicate-plugin-pwa-head-tags
• no-duplicate-theme-config-metadata-keys
• no-empty-footer-link-columns
• no-empty-theme-config-metadata
• no-empty-navbar-dropdown-items
• no-empty-navbar-item-objects
• no-duplicate-sidebar-doc-ids
• no-empty-sidebar-categories
• no-mixed-sidebar-link-kinds
• no-redundant-social-card-metadata
• no-svg-social-card-image
• no-use-base-url-for-internal-link-components
• prefer-css-modules-in-site-src
• prefer-head-tag-attributes-object
• prefer-i18n-default-locale-first
• prefer-theme-config-metadata-name-for-twitter-tags
• prefer-theme-config-metadata-property-for-og-tags
• no-page-css-module-imports-in-components
• prefer-use-base-url-for-static-assets
• require-default-export-pages
• require-head-tag-attributes-when-no-inner-html
• require-head-tag-tag-name
• require-theme-config-color-mode-object
• validate-theme-config-color-mode-default-mode
• validate-theme-config-color-mode-switch-flags
• no-conflicting-theme-config-color-mode-flags
• require-theme-config-announcement-bar-id
• validate-theme-config-announcement-bar-is-closeable
• require-base-url-issue-banner-enabled
• require-base-url-slashes
• require-i18n-default-locale-in-locales
• require-plugin-pwa-debug
• require-plugin-pwa-offline-mode-activation-strategies
• require-plugin-pwa-setup
• require-pages-plugin-excludes
• require-site-config-fields
• require-site-url-origin
• require-trailing-slash-explicit
• require-theme-config-image
• validate-navbar-item-position

The recommended link-semantics rules also remain enabled here, so strict covers both config/sidebar correctness and component-level routing conventions.

If you only want Docusaurus config/theme/plugin enforcement without the broader page-module and CSS architecture rules, use config instead.

Flat config example

import docusaurus2 from "eslint-plugin-docusaurus-2";

export default [docusaurus2.configs.strict];

When to use it

Use strict if you are intentionally adopting the strongest future tier and are comfortable with that preset becoming more opinionated over time.