Building a Website

Building a Website

A website includes page content, templates, navigation, assets and settings. GenerateBlocks provides the layout blocks; the active theme determines where many site-wide parts are stored and rendered.

Keep the existing architecture deliberate

Site architecture	Where to look
GeneratePress with GP Premium Elements	Block Elements and their display rules for supported theme regions/templates
A block theme	Site Editor templates and template parts
Another classic theme	That theme's documented header, footer and template integration

GeneratePress is not required merely to use these skills. Do not change the theme or add template code as an automatic side effect of a page-design request. Pro Site Header or Navigation blocks must still be placed where the chosen architecture renders them.

Plan the build

1. Inventory the theme, GenerateBlocks versions, existing templates and shared references.
2. List required pages and the navigation destinations they need.
3. Decide which content is static and which comes from queries or custom fields.
4. Choose local styling or explicitly authorize a shared system.
5. Build one representative page and verify it before repeating the pattern.
6. Implement the authorized template regions and their display conditions.
7. Review forms, navigation, mobile layout and empty/dynamic states before publication.

Keep new styling local unless shared styles or tokens were explicitly chosen. A consistent site can still use local styles; shared reuse is a choice with cross-page effects.

Template context matters

An archive template should preserve the archive's query and pagination rather than always showing the same fixed posts. A single-post template should resolve dynamic tags against the displayed post. Verify display conditions on the intended URLs and on an excluded URL.

Do not assume an Element record, a page record, a form record and an overlay record share an API route or identical metadata. Resolve the storage owner before editing.

What an assistant can do depends on its access

An assistant with local files can generate layout files. With an authorized WordPress connection it may create drafts or edit the intended records. Access to a repository is not access to WordPress, and source files do not provide authentication.

Native editor and frontend checks still matter even when much of the build happens through tools. Publishing, navigation changes, template-wide changes and shared-style changes should match the scope you actually requested.

Continue with WordPress Editing and Publishing and the template reference.

---

Back to wiki home · Reference library