What jedee kept from Eleventy Excellent

jedee is a fork of Eleventy Excellent by Lene Saile. Every other page in this wiki states EE-stock-versus-jedee where it happens to matter locally; this page states it systematically, so a claim on another page can be checked against one inventory.

The source is Lene’s own documentation collection, src/docs/ in the upstream checkout at /Users/johanedlund/Projects/eleventy-excellent — 22 files, about 3,800 words, read in place and never edited. The checkout sits on tag 4.6.1; jedee merged 4.6.0 in May 2026, one patch behind.

⚠ The docs are dated 30 March 2026 and are already stale in Lene’s own repo. details.md describes a <custom-details> WebC component at length — and the string custom-details appears nowhere in the 4.6.1 source tree except inside that doc file. The component was folded back into a plain <details>/<summary> partial and the doc was never updated. Treat every claim here as verified against code on 2026-07-31, not as a transcription of Lene’s prose.

Stock and untouched

These are EE’s, unchanged, and this wiki should not describe them as jedee inventions:

• The config module layout. src/_config/ splits into collections.js, events.js, filters.js, plugins.js, shortcodes.js, each a barrel over a folder of the same name, plus setup/ and utils/. jedee’s tree is file-for-file identical to EE’s. eleventy.config.js only registers; the logic lives in the modules.

• The cascade layer order, byte-identical in both global/global.css:

  @import 'tailwindcss/base' layer(tailwindBase);
  @import 'base/reset.css' layer(reset);
  @import 'base/fonts.css' layer(fonts);
  @import 'tailwindcss/components' layer(tailwindComponents);
  @import 'base/variables.css' layer(variables);
  @import 'base/global-styles.css' layer(global);
  @import-glob 'compositions/*.css' layer(compositions);
  @import-glob 'blocks/*.css' layer(blocks);
  @import-glob 'utilities/*.css' layer(utilities);
  @import 'tailwindcss/utilities' layer(tailwindUtilities);

  Including the consequence Lene spells out in css.md: the “local” bundle uses no layers, so a per-page stylesheet outranks the whole global bundle regardless of selector specificity.

• Two CSS streams, not three. css.md documents a third destination, src/assets/css/components/, for stylesheets a WebC component references from the output folder — and _config/events/build-css.js does glob it, identically in both repos. But the folder exists in neither checkout: not in jedee, and not in vanilla 4.6.1 either. It is a wired-up route with nothing routed through it, on both sides.

• Tailwind as a token pipeline, not a utility framework. No utility classes in the markup on either side.

• The two JS bundles (js-inline.njk, js-defer.njk) and the two source folders behind them — scripts/components/ ships to the output folder for custom elements to load directly, scripts/bundle/ ships to _includes/scripts/ for the {% js %} shortcode.

• The three image routes (HTML Transform, markdown syntax, {% image %} / {% imageKeys %}) — see Self-hosting remote images at build time for the one place jedee leans on a route Lene documents but does not use much.

• OG image generation, favicon generation, the pa11y config generator, the _redirects template — all four still the stock pipelines. See The accessibility test for what jedee changed in how pa11y is run.

• <custom-card>, <custom-masonry>, <custom-youtube>, <custom-peertube>, <custom-svg> — the five WebC components EE 4.6.1 actually ships, all still present. (The folder holds seven .webc files; custom-youtube-link.webc and custom-peertube-link.webc are the no-JS fallback partners of the two embeds, not components in their own right. Counts on this page exclude them on both sides.)

Extended

The interlinker is the consequential addition. Vanilla EE does not ship it, which is exactly what made a vanilla checkout the decisive control when jedee’s navigation rendered blank — see The interlinker's second render pass. Any oddity that only reproduces here and not upstream should be tested against that checkout before anything else.

The design-token divergence is narrower than it looks from the file count: jedee kept Lene’s colorsBase.json → colors.json generation step and her npm run colors script verbatim, and added a semantic layer and composite typography tokens on top. It did not replace the pipeline.

Deleted

what-delete.md is Lene’s own list of what a fork can safely remove, which makes it a fair measure of how much of the starter jedee actually kept. Against that list:

So jedee removed almost exactly the set Lene marks as optional, and nothing beyond it. The starter’s own structure survived the fork intact.

⚠ Left behind by those deletions

Three pieces of EE machinery are still in the tree with nothing referencing them. All three are the residue of a deletion, not a decision:

• partials/details.njk + scripts/bundle/details.js — the disclosure UI that rendered the src/docs/ collection into /get-started/. The collection is gone; no template includes the partial. meta.details (the expand/collapse button labels) is still in meta.js too.
• partials/gallery.njk + scripts/bundle/dialog.js — EE’s <dialog>-based lightbox, superseded by PhotoSwipe. No layout includes it.
• scripts/components/custom-easteregg.js — still copied to the output folder. base.njk gates the component behind {% if meta.easteregg %} (stock EE behavior) and meta.easteregg is false, so nothing ever loads it.

Each is a handful of kilobytes of source that compiles but ships to no page — the JS-and-partial equivalent of the orphan local/*.css problem. Nothing is broken; the note exists so the next reader doesn’t take their presence as evidence the features are in use.

Source: /Users/johanedlund/Projects/eleventy-excellent/src/docs/ at tag 4.6.1 (docs dated 2026-03-30), every claim checked against both checkouts on 2026-07-31.