Plugin Decision Lab

This lab is a controlled extension experiment.

You are not collecting plugins.

You are testing whether one extension earns its place.

Choose one candidate

Use a plugin relevant to a static portfolio and compatible with your chosen experiment environment.

Possible categories include:

• sitemap generation;
• feed generation;
• SEO/meta helpers.

Check the current plugin's own license, maintenance state, and documentation before use. The Jekyll repository linking to a plugin does not automatically govern that plugin's separate source license.

Baseline

Before installation, record:

Build time/behavior:
Generated files relevant to feature:
Current manual alternative:
Gemfile dependencies:

Add the plugin deliberately

Document every source change:

• Gemfile;
• configuration;
• layout tag/include if needed;
• generated output.

Build locally.

Verify behavior

Do not accept "bundle installed successfully" as proof.

Find the generated output the plugin claims to create or modify.

Examples:

• sitemap file;
• feed file;
• metadata tags.

Remove it

In a disposable branch/copy, remove the extension and rebuild.

What source/output now fails or disappears?

That tells you how tightly the project became coupled to it.

Decision record

Problem solved:
Generated evidence:
New dependency:
Portability impact:
Maintenance impact:
Keep / remove:
Reason:

Checkpoint

A plugin only passes this lab if you can state what it added, where it ran, what output proves it worked, and what dependency cost it introduced.