A website with several pages quickly develops a maintenance problem: the same header, footer, colors, and spacing appear everywhere. WordPress offers one way to manage that repetition while letting an editor publish content without touching HTML. The useful starting point is understanding which parts of the site belong to content, presentation, and functionality.

Start with the Editing Workflow

Before choosing a theme or adding plugins, list the things an editor actually needs to change: articles, project descriptions, navigation, and perhaps a contact page. Then distinguish these everyday changes from less frequent design changes. A content management system earns its complexity when that publishing workflow is valuable; a small, infrequently updated site can also work well as static HTML.

For a WordPress build, a block theme makes the page structure editable through blocks. The official quick-start guide walks through activation, customization, and exporting a theme. Use a local installation for this exercise and work on a copy rather than experimenting on a live site.

A Small Theme You Can Inspect

Create a folder named research-notes under wp-content/themes. This example uses the following files:

research-notes/
├── style.css
├── theme.json
├── parts/
│   ├── header.html
│   └── footer.html
└── templates/
    ├── index.html
    └── single.html

According to the Theme Handbook, style.css and templates/index.html are the required files for recognizing a block theme. The other files in this example make the structure easier to reuse. Start style.css with the theme metadata:

/*
Theme Name: Research Notes
Version: 1.0
Text Domain: research-notes
*/

Put a site-title block in parts/header.html. Put the shared copyright paragraph in parts/footer.html. These are block markup files, not complete HTML documents:

<!-- parts/header.html -->
<!-- wp:site-title /-->

<!-- parts/footer.html -->
<!-- wp:paragraph -->
<p>Research Notes. All rights reserved.</p>
<!-- /wp:paragraph -->

Separate the Article List from the Article

The index template needs a list of posts and a way to move between result pages. The inherited query uses the current request, so an archive or search page can supply its own set of results. Place this in templates/index.html:

<!-- wp:template-part {"slug":"header","tagName":"header"} /-->
<!-- wp:group {"tagName":"main","layout":{"type":"constrained"}} -->
<main class="wp-block-group">
  <!-- wp:query {"query":{"inherit":true}} -->
  <div class="wp-block-query">
    <!-- wp:post-template -->
      <!-- wp:post-title {"isLink":true} /-->
      <!-- wp:post-excerpt /-->
    <!-- /wp:post-template -->
    <!-- wp:query-pagination -->
      <!-- wp:query-pagination-previous /-->
      <!-- wp:query-pagination-next /-->
    <!-- /wp:query-pagination -->
  </div>
  <!-- /wp:query -->
</main>
<!-- /wp:group -->
<!-- wp:template-part {"slug":"footer","tagName":"footer"} /-->

A reader who opens a post needs its full content, rather than the excerpt from the list. Give that state its own templates/single.html:

<!-- wp:template-part {"slug":"header","tagName":"header"} /-->
<!-- wp:group {"tagName":"main","layout":{"type":"constrained"}} -->
<main class="wp-block-group">
  <!-- wp:post-title {"level":1} /-->
  <!-- wp:post-content {"layout":{"type":"constrained"}} /-->
</main>
<!-- /wp:group -->
<!-- wp:template-part {"slug":"footer","tagName":"footer"} /-->

Both templates reference the same header and footer. A change to one template part can therefore reach both surfaces. As the site grows, add specialized templates only when the page needs different behavior; copying the entire structure into every template recreates the original maintenance problem.

Keep Design Settings Together

The theme.json system connects shared settings and styles to the front end and editor. For example, the following file gives normal content and wide blocks distinct widths and sets a simple white-and-dark palette:

{
  "version": 2,
  "settings": {
    "layout": { "contentSize": "760px", "wideSize": "1100px" }
  },
  "styles": {
    "color": { "background": "#ffffff", "text": "#222222" },
    "typography": { "fontFamily": "Arial, sans-serif", "lineHeight": "1.7" }
  }
}

A shared content width is easier to adjust than unrelated widths on individual blocks. Keep exceptional styling explicit and limited. If a Site Editor change seems to override a file change, inspect saved template or style customizations before adding more CSS: the file on disk is not always the only source of the displayed design.

Keep Persistent Features out of the Theme

A project content type, a publication database, or a registration workflow should not disappear when the visual theme changes. Put such functionality in a plugin. The Plugin Handbook introduces the plugin file structure and hooks. Conversely, typography and page composition normally belong in the theme.

Before delivery, create several sample posts with long titles and different content lengths. Open the list, an individual article, search results, and a missing URL. Check pagination, keyboard navigation, and mobile layout. Finally, export the theme changes and confirm that the files are present in the version you intend to deploy. The goal is a publishing workflow that remains understandable after the first page is finished.

References and Further Reading

  1. WordPress Theme Handbook: Quick-Start Guide
  2. WordPress Theme Handbook: Theme Structure
  3. WordPress: Introduction to theme.json
  4. WordPress Plugin Handbook: Plugin Basics