Build a JSON Content System for a Website You Already Run

JSON is the labeled box, not the finished page

JavaScript Object Notation, usually called JSON, is a plain text format for storing labeled information.

The JSON file holds the words and facts. PHP reads those labels and builds the page a person sees.

Keeping those jobs separate means the design can change without rewriting the content. It also means the same record can support more than one page element.

{
  "slug": "build-a-content-system-with-json",
  "title": "Build a JSON Content System",
  "summary": "Write the content once and reuse it.",
  "updated": "2026-09-29"
}

This lesson is its own receipt

The page you are reading comes from the lessons.json file published by 1 Mouse Marketing. The lesson hub reads the same record to build its card.

The page template also sends the title and dates into the structured data. The federation catalog counts the lesson as part of the site's public lesson collection.

This is not a diagram of a possible system. It is the system serving this lesson.

One lesson record now performs four jobs

The record is useful because the rest of the site knows how to reuse it.

1. Build the full lesson page

   The template reads the title, opening, sections, links, and next step.

2. Build the lesson hub card

   The same title and summary introduce the lesson on the free lesson page.

3. Describe the lesson to search and AI systems

   The template passes the record into the page's structured data instead of maintaining a second description.

4. Publish the lesson collection as data

   The federation catalog names the lesson dataset and links to the public JSON file.

Keep content separate from presentation

The JSON record should not decide whether a card has two columns or one. That belongs in the template and the stylesheet.

The template should not decide the lesson title or hide a paragraph inside a PHP array. That belongs in the content record.

This line is what makes the system reusable. Content can move through the site while the design remains free to change.

Build the first version in four moves

1. Choose the repeated fields

   Start with the information every item shares. A title, summary, URL, and updated date are enough for the first version.

2. Write one clean JSON record

   Use labels a person can understand. Validate the file before the page depends on it.

3. Make one PHP renderer

   Read the record and escape every value before sending it into HTML.

4. Check every place the record appears

   Render the full page and its card. Then validate the JSON and the structured data generated from it.

Use the portfolio when you need the deeper layer

DataSetSEO explains how organized datasets become discoverable assets. Digital Karma Web documents the federation layer that connects those assets across the portfolio.

1 Mouse Marketing has a different job. This is where a builder learns the method by making a working version first.