Debug a Content-Model Failure

Content systems fail in different ways depending on the model.

Today you diagnose by asking what should have created this output?

Scenario A: data record missing

The project grid renders, but one project is absent.

Inspect:

1. _data structure;
2. the loop scope;
3. filters/conditions;
4. generated HTML.

Scenario B: post absent from journal

Inspect:

• _posts filename convention;
• front matter/date;
• whether the file is being recognized as a post;
• site.posts output.

Scenario C: collection exists but project URL is missing

Inspect:

• collection declaration;
• output setting;
• server restart after config change;
• project.url;
• permalink configuration.

Scenario D: link points to wrong deployment path

Inspect:

• generated href;
• relative_url use;
• baseurl assumptions;
• actual deployed root.

Lab

Create one bounded failure in the content model you use.

Do not break the whole site.

Record:

Expected model:
Missing/wrong output:
Source object that should have produced it:
First evidence:
Root cause:
Repair:
Verification:

Checkpoint

Your diagnosis should name the content model and the failed boundary, not merely say "Jekyll didn't generate it."