Unit 07 · lesson

Find the Theme Files You Cannot See

If a theme supplies your layout, you should be able to locate that source.

Invisible in the project tree does not mean unknowable.

Find the installed gem

Jekyll's theme documentation shows a Bundler command such as:

bundle info --path THEME_NAME

For a Minima-based experiment that might be:

bundle info --path minima

The command reports the installed theme gem directory.

Inspect, do not edit the installed gem

Open or list that directory.

Look for:

_layouts
_includes
_sass
assets
_data

The exact tree depends on the theme/version.

Your goal is to learn where the build gets its defaults.

Do not make your normal customization by editing the installed gem files in place.

Why?

Because those files live in dependency-managed installation state, not your project source. Reinstall/update the gem and your direct edit may disappear.

Trace one generated element

Pick something visibly provided by the theme:

header;
footer;
page wrapper;
post metadata;
stylesheet.

Find the source file inside the theme.

Then trace:

THEME FILE
   ↓ Jekyll lookup/render
GENERATED OUTPUT

Hidden-source debugging

Suppose a footer appears in generated HTML but no footer file exists in your repo.

Before assuming Jekyll invented it, inspect:

selected theme;
theme includes/layouts;
nested layout composition;
local overrides.

Evidence checkpoint

Save an inventory:

Theme path:
Theme layout inspected:
Theme include inspected:
Theme stylesheet/Sass source inspected:
Generated output tied to one theme source:

Checkpoint

Explain why editing a dependency's installed files is weaker project history than creating a deliberate local override.