What problem does it solve? Creating a new MariaDB documentation page involves many easy-to-miss conventions: correct frontmatter, house style, GitBook block syntax, file naming rules, and a SUMMARY.md nav entry without which the page never appears in the published docs. This Skill walks through the entire process so the new page is publishable as-is. ## Core Features & Use Cases - Correct placement and naming: Chooses the right space and subdirectory, enforces kebab-case naming (preserving underscores for identifiers), and uses README.md for section landing pages. - House style and GitBook syntax: Generates pages with description frontmatter, American English, sentence-style headings, and valid hint/tabs/code/content-ref blocks, plus proper relative and cross-space alias links. - SUMMARY.md nav integration: Adds the navigation entry in the correct location with matching indentation style, then validates the result with the doc-lint hook. - Use Case: A contributor asks to "add a docs page about configuring the binary log under server". The Skill confirms the space and location, creates server/reference/.../configuring-the-binary-log.md with proper frontmatter, adds the SUMMARY.md entry, and runs the linter. ## Quick Start Ask the assistant to create a new documentation page about your topic in a specific MariaDB docs space, for example: "Create a new page about connector timeouts under the connectors space."
