Skip to content

Conversation

@TedGoas
Copy link
Owner

@TedGoas TedGoas commented Aug 5, 2025

Note

Major redesign and build simplification with Eleventy 3 and custom CSS.

  • Upgrade to Eleventy v3; drop PostCSS/Tailwind pipeline and related transforms/files; add CSS passthrough and watch
  • New dark-mode layouts (default.njk, post.njk) and simplified 404; remove legacy header/footer partials and icons
  • Robust readableDate filter (Luxon v3) and HTML minification transform that skips XML/RSS
  • Add src/_data/newsletter.js to fetch Beehiiv RSS; adjust site data; remove unused tag collections/files
  • Update scripts and dependencies; set Node 18; refresh README/humans; remove dublin.rdf

Written by Cursor Bugbot for commit 563d923. This will update automatically on new commits. Configure here.

* Fresh install of 11ty
* Basic CSS, page content, and RSS
* import blog posts
* Remove unused files
@TedGoas TedGoas self-assigned this Aug 5, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

module.exports = async function() {
try {
const response = await fetch('https://rss.beehiiv.com/feeds/vZHlctjmDk.xml');
const xml = await response.text();
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HTTP errors silently ignored in newsletter data fetch

Medium Severity

The fetch() call doesn't check response.ok or response.status before processing the response. The Fetch API doesn't throw exceptions for HTTP error responses (4xx, 5xx) - only for network failures. If the beehiiv RSS server returns a 404 or 500 error, the code will attempt to parse the error page as XML, find no items, and silently return an empty issues array. The catch block only catches network errors, not HTTP errors, so there's no logging or indication when the feed server returns an error status.

Fix in Cursor Fix in Web

<script src="{{ '/assets/js/bundle.js' | url }}"></script>
{% if highlightjs %}
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/10.7.2/highlight.min.js"></script>
<script>hljs.initHighlightingOnLoad();</script>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Syntax highlighting removed but posts still expect it

Medium Severity

The redesigned default.njk template removes the conditional highlight.js loading ({% if highlightjs %}...{% endif %}), but several posts still have highlightjs: true in their frontmatter (e.g., src/posts/2014-05-13-jerseyscript.md, src/posts/2020-01-02-my-first-interactive-email.md, src/work/2016-01-01-canfield.md, src/work/2020-01-01-stack-overflow.md). Code blocks in these posts will render without syntax highlighting, causing a visual regression.

Fix in Cursor Fix in Web

And make article list CSS names more generic
/* Utility Classes */
.text-mono { font-family: var(--font-mono); }
.text-muted { color: var(--color-text-muted); }
.text-secondary { color: var(--color-text-secondary); }
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CSS variable used but never defined

Medium Severity

The CSS variable --color-text-secondary is referenced in multiple places (.text-secondary utility class, .caption, .post-content blockquote, and .btn) but is never defined in the :root block. Elements using the text-secondary class in templates like 404.njk, default.njk, and post.njk will not receive the intended muted text color, instead falling back to inherited colors. The variable --color-text-muted is defined and appears to be the intended equivalent.

Additional Locations (2)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants