// Use when configuring site.json, setting up layouts, frontmatter, site properties, themes, dark mode, plugins, page navigation, headers, footers, custom CSS/JS, or when users ask about site structure, site-wide settings, or page configuration
| name | markbind-site-config |
| description | Use when configuring site.json, setting up layouts, frontmatter, site properties, themes, dark mode, plugins, page navigation, headers, footers, custom CSS/JS, or when users ask about site structure, site-wide settings, or page configuration |
| paths | site.json,*.md,*.html |
MarkBind site behavior is configured through site.json, frontmatter, and layout files in _markbind/layouts/.
main.csssite.json as the source of truth for site-wide defaults and generation behavior.globalOverride for cross-page overrides.baseUrl before deployment, especially for GitHub Pages project sites._markbind/layouts/ and ensure each layout renders {{ content }}.pages/glob configuration to avoid accidentally publishing draft or fragment files.site.json structure, what each top-level property controls, and how property precedence works when multiple config sources set the same value.src/glob, exclude subsets with globExclude/pagesExclude, and apply page-level options like layout, title, scripts, and output extension.title, layout, pageNav, header, footer, keywords) and how frontmatter interacts with site.json and globalOverride._markbind/layouts/, using {{ content }} correctly, and injecting assets/scripts with <head-top>, <head-bottom>, and <script-bottom>.style (dark mode, Bootswatch theme, code theme, code line numbers) and when to use each option.pluginsContext, and the expected shape of plugin config in site.json.searchable, headingIndexingLevel, and Pagefind selectors for excluding content from indexing.site.json settings (deploy.message, deploy.repo, deploy.branch) and how to set baseUrl so links resolve correctly after deployment.fileExtension (for example .json/.txt) and the limitations that apply to non-HTML pages.Refer to this skill for MarkBind-specific authoring features and formatting when writing MarkBind pages.
Use when adding MarkBind components like boxes, panels, tabs, modals, tooltips, popovers, dropdowns, navbars, search bars, cards, badges, questions, quizzes, trees, thumbnails, annotations, scroll-to-top buttons, dark mode toggles, breadcrumbs, site-nav, or page-nav to MarkBind pages
Use when deploying MarkBind sites to GitHub Pages, Netlify, or CI platforms, configuring deploy settings in site.json, setting up GitHub Actions workflows, PR previews, or when users ask about publishing, hosting, or deploying their MarkBind site
Use when initializing a new MarkBind site, choosing templates, installing MarkBind, serving locally, or when a user asks how to get started with MarkBind, create a new documentation site, or scaffold a project
Use when creating Nunjucks macros, advanced templating patterns, dynamic content generation, loops, conditionals, custom macros for repeated component patterns, or when users ask about automating content, creating reusable component templates, or advanced Nunjucks features in MarkBind
Use when reusing content across pages with includes, defining variables, creating boilerplate templates, sharing content between sites, creating content variations, or when users ask about content reuse, DRY patterns, includes, variables, or templates in MarkBind