website

Build, test, and clean the dart_node documentation website with Eleventy and Playwright.

113|2|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/MelbourneDeveloper/dart_node --skill website-melbournedeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: website
Source: https://github.com/MelbourneDeveloper/dart_node/tree/main/.claude/skills/website
Command: npx skills add https://github.com/MelbourneDeveloper/dart_node --skill website-melbournedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of building, serving, and testing the documentation website for the dart_node project, ensuring accurate and up-to-date information for users.

Core Features & Use Cases

  • Website Generation: Builds a static documentation site using Eleventy, incorporating package READMEs and generated API documentation.
  • Development Server: Provides a live-reloading development server for real-time previewing of changes.
  • End-to-End Testing: Executes Playwright tests to ensure the website's functionality, responsiveness, and content accuracy.
  • Use Case: Developers can quickly iterate on documentation content, previewing changes instantly and running automated tests to catch regressions before deployment.

Quick Start

Run the website skill to build and test the documentation.

Frequently Asked Questions about website

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and serve a static documentation website using Eleventy?

To build and serve a static documentation website, this Skill uses Eleventy for static site generation and provides a live-reloading development server to preview content changes instantly.

Can I run automated end-to-end tests for my documentation site with Playwright?

Yes, you can run automated end-to-end tests with Playwright to ensure your documentation website maintains functionality, responsiveness, and content accuracy during development.

How do I generate API documentation and include package READMEs in my website?

Generating API documentation and incorporating package READMEs is handled automatically by the build process, pulling content updates directly into the static site structure.

What is the best way to iterate on documentation content and catch regressions before deployment?

The best way to iterate on documentation content is using the live-reloading server for real-time previews and executing Playwright tests to catch website regressions before deployment.

Does this documentation build process support automated content updates from existing package files?

Yes, the documentation build process supports automated content updates by extracting and integrating content directly from existing package READMEs into the generated site.