// Refer to this skill for MarkBind-specific authoring features and formatting when writing MarkBind pages.
| name | markbind-authoring |
| description | Refer to this skill for MarkBind-specific authoring features and formatting when writing MarkBind pages. |
| paths | *.md,*.html |
Use this skill for MarkBind-specific authoring behavior and syntax extensions.
MarkBind pages are not plain Markdown. The processing order matters:
{% ... %}, {{ ... }}){% raw %}...{% endraw %} when needed..always-index, .no-index, .keyword) intentionally.==, !!, %%, ++, --, color syntax) and when to use them..line-numbers, start-from, highlight-lines, heading) and inline code language classes..always-index, .no-index).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
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