Skip to content

feat(blog): implement new blog layout, custom card component, and markdown data pipeline#139

Open
moshams272 wants to merge 6 commits into
webpack:mainfrom
moshams272:feat/create-blogs
Open

feat(blog): implement new blog layout, custom card component, and markdown data pipeline#139
moshams272 wants to merge 6 commits into
webpack:mainfrom
moshams272:feat/create-blogs

Conversation

@moshams272

@moshams272 moshams272 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Summary

1. Data Pipeline (scripts/data/blogs.mjs)

  • Automatically adds missing # H1 tags to prevent the Orama indexer from dropping blog pages.
  • Converts descriptions to pure plain text. (need to be more clean)
  • Sorts posts by dates descending and prepends an Overview link in the generated site.json.

2. UI Components & Layout

  • BlogCard: Uses a Stretched Link to make the whole card clickable while safely supporting nested GitHub avatar links. Includes a Webpack diamond hover effect.
  • BlogLayout: Wraps the blog grid inside PartialArticle to preserve the global Sidebar and Navbar.

3. Navigation (pages/site.mjs)

  • Sidebar Integration: Hooks the generated blogs/site.json into the root sidebar config to enable correct navigation across /blogs/* paths.

Related issue: #101

@@ -0,0 +1,229 @@
---
title: Webpack 5.105
sort: 20260203

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Since we're already making changes, we should remove the sort metadata. We already have dates in the filename, and we could introduce a date metadata field (or something similar) so authors don't have to rename a blog post every time the publication date changes, which is pretty common here.

That said, we should still support the existing option of deriving the date from the filename.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think explicitly putting the publish date is fine, so that the path can really be anything, similar to Node.js, e.g. https://nodejs.org/en/blog/vulnerability/june-2026-security-releases

Comment on lines +1 to +8
---
title: Webpack 5.105
sort: 20260203
contributors:
- bjohansebas
---

# Webpack 5.105

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
---
title: Webpack 5.105
sort: 20260203
contributors:
- bjohansebas
---
# Webpack 5.105
---
published: 20260203
authors:
- bjohansebas
---
# Webpack 5.105

@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
webpack-doc-kit Ready Ready Preview, Comment Jun 16, 2026 4:03pm

Request Review

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can we split this into a few different files to make things clearer, such as:

  • Blog/PostCard
  • Blog/Cover (the post image)
  • Blog/Byline (the author info)

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.

3 participants