Questions, ideas,
and useful corrections.

Help us understand your question

For a question about an article or guide, include the page address and the heading closest to the relevant passage. Tell us which part is unclear and what you were trying to accomplish. If a technical instruction behaves differently in your project, include the framework version and the smallest useful description of the difference.

For a broken page or image, include the affected URL, your browser, and the approximate screen size or device. A short sequence of steps is more useful than a general report that a page does not work.

Editorial corrections

Corrections are welcome. Quote the specific sentence you think needs attention and, when possible, identify an official reference that supports the correction. Please distinguish a factual error from a suggestion about the explanation or design so the intended change is clear.

For image or licensing questions, identify the asset by its filename or the page where it appears. Include enough context to locate the item without sending unrelated personal information.

Choose the next useful guide

If your question is about where to begin, the static builder overview compares the main workflows. The Lab covers practical implementation questions, and the launch checklist helps identify common publishing gaps.

This site provides learning resources and workflow guidance. Questions about a third-party tool’s account, billing, or service need to go to that tool’s own support team.