Theme vs Custom Layout Decision

You already have a working custom template system.

Now make an explicit decision: keep it, replace part of it with a theme, or adopt a theme more broadly.

Option A: keep custom layouts

Strengths:

• every important template is visible in your repo;
• source ownership is obvious;
• no theme dependency;
• easier to explain in a portfolio defense.

Costs:

• you maintain the design yourself;
• accessibility/visual bugs are yours;
• fewer upstream theme updates.

Option B: adopt a gem-based theme

Strengths:

• reusable upstream presentation system;
• potentially maintained fixes/features;
• smaller visible project tree.

Costs:

• hidden/default source comes from dependency;
• overrides create fork points;
• theme compatibility/version becomes part of build.

Option C: use theme selectively

Depending on the theme/Jekyll architecture, you might keep substantial local layouts/styles while consuming selected theme behavior or transition gradually.

Do not assume every theme supports the exact hybrid you imagine. Inspect its documentation/source.

Decision evidence

Create an ADR:

Decision:
Context:
Current custom architecture:
Theme considered:
Useful theme capabilities:
Files I would override:
Dependency/maintenance cost:
Deployment compatibility:
Decision:
Rejected alternative:

Portfolio rule

The final site does not need a third-party theme to count as a Jekyll site.

If your custom layouts are clear, responsive, accessible, and maintainable, keeping them can be the stronger student artifact.

Checkpoint

Defend the decision based on architecture, not which screenshot looks more fashionable.