---
title: "Markdown JSON template: one garden bed record"
slug: markdown-json-template
excerpt: "Keep one invented garden bed record on a Markdown page, with a reusable title and framing line plus filled, empty and absent-or-null JSON variants."
quickAnswer: "A Markdown JSON template pairs a page title and a purpose sentence with one fenced JSON record. This example follows Jane Doe's invented garden bed through three variants: filled fields, empty arrays and objects, and absent or null values. A short note beneath each explains the writer's choice."
keyTakeaways:
  - "A bed title and a purpose sentence introduce the fenced record."
  - "The filled example gives Jane Doe's invented bed a bedId, caretaker, crops and watering details."
  - "Empty crops and watering fields retain their places while holding no entries."
  - "The last example omits crops and leaves watering null, with a note explaining both choices."
  - "A bed-specific file name keeps the page tied to the same invented record."
publishedDate: 2026-10-24
dateModified: 2026-10-24
author: Bobby Huang
cluster: A
role: post
status: published
faq:
  - q: "What does the page title identify?"
    a: "It identifies the bed described by the record. The title can use the same bedId that appears inside the JSON."
  - q: "Why keep the empty crops and watering fields?"
    a: "In this invented example, Jane Doe wants their places to remain visible before she adds their entries."
  - q: "Why explain an absent field or null value?"
    a: "The note tells the reader what Jane Doe intends here: crops is omitted from this copy, while watering has no chosen value."
related:
  - markdown-recipe-template
---

A Markdown JSON template puts one data record beside a sentence about its purpose. The page title names the subject; the JSON carries its details. A note below the fence explains any deliberate gaps in that particular copy.

Fictional Jane Doe keeps a record for an invented community garden bed here. Every person and value in the garden example is invented for this post. The three examples describe the same bed, with different amounts of detail written down.

## What belongs on the record page

Give the bed a title and say why you are keeping its record. Jane Doe's framing sentence says the page holds planting details for one invented community garden bed. That sentence stays outside the JSON, where she can revise it as prose.

The record itself has a bedId, a caretaker, crops and watering details. A bedId identifies the bed across the examples. The caretaker stays Jane Doe throughout. Only the crops and watering fields change between the three copies.

The page has an .md ending. For background on that ending, consult [the .md file explanation](what-is-a-md-file.md).

## Reusable bed record template

Reuse the shape below, substituting your wording for the bracketed phrases. Under the framing line, put one of the fenced records below, with its note directly beneath it.

```text
# [Bed record title]

Jane Doe keeps [planting details] for [one invented community garden bed] on this page.

[Fenced JSON record for this bed]

[One sentence explaining the fields filled in or left empty in this copy.]
```

Name the bed in the title, leaving its individual details inside the record. The framing line names the purpose of the whole record. The final sentence explains the choice made in that copy, so a gap has context beside it.

For the fence punctuation used in the examples below, see [Markdown code blocks](markdown-code-blocks.md). The record stays inside its fence; the sentence about it stays beneath the closing line.

## Jane Doe's filled bed record

For her invented bed, Jane Doe uses the title "Amber bed" and the framing line "This page keeps planting details for Jane Doe's invented community garden bed." She fills the record as follows.

```json
{
  "bedId": "amber-bed",
  "caretaker": "Jane Doe",
  "crops": ["violet beans", "silver basil"],
  "watering": {
    "method": "clay jug",
    "dayPart": "dusk"
  }
}
```

This filled copy names two invented crops and supplies two watering details; Jane Doe might keep it when she wants those choices written beside the bed's identity.

## The same bed with empty arrays and objects

The title, framing line, bedId and caretaker remain as above. Jane Doe leaves crops and watering in place but gives neither any entries.

```json
{
  "bedId": "amber-bed",
  "caretaker": "Jane Doe",
  "crops": [],
  "watering": {}
}
```

Here crops holds an empty array and watering holds an empty object; Jane Doe might keep this copy before adding either kind of detail, while retaining both field names.

## The same bed with absent or null values

The earlier title and framing sentence accompany this copy too. This time she leaves crops out of the record and writes null for watering.

```json
{
  "bedId": "amber-bed",
  "caretaker": "Jane Doe",
  "watering": null
}
```

This copy omits crops and gives watering a null value; Jane Doe might keep it when she wants no crops field and has no chosen watering value, with this sentence recording that intent.

## Wording beside an unfinished record

An empty field, an absent field and a null value need not express the same intention in Jane Doe's writing. In her empty copy, both field names remain with no entries. In her last copy, crops is absent altogether, while watering remains present with null. Her prose explains those choices for this invented bed alone.

Keep the explanation specific to what changed. "No chosen watering value" describes Jane Doe's intent in the last example. Whether the bed receives water remains unstated. Likewise, the missing crops field says nothing here about whether anything is planted; it says which detail this copy leaves out.

## Naming the bed record file

For these examples, `amber-bed.md` names the subject held inside. The same file can hold the title, purpose sentence, one chosen variant and its note. Keeping one variant on that page avoids presenting three alternatives as three separate beds.

For wording a file name around its subject, consult [Markdown file naming](markdown-file-naming.md). Jane Doe can keep the bedId inside the record even if she later gives the page a longer title.

## Where Sashmark fits

Sashmark's plan pairs Markdown reading with text editing in a desktop app. With the app still in development, those plans concern people receiving Markdown pages written by agents.