Series navigation for the AI Blockchain blogpost series is broken

[michaelmwu]

The navigation:

👉 Part 1: AI, Blockchain, and Cloud – Who Does What
👉 Part 2: Why Fully Decentralized AI Is Mostly a Myth
👉 Part 3: How Cloud ML Pipelines Power Web3 Analytics
👉 Part 4: AI for Blockchain Fraud & Anomaly Detection
👉 Part 5: Smart Contracts + AI Agents
👉 Part 6: What Comes Next (Predictions)

In parts 1, 2, 3, 4, 5, 6 are broken - they need to have /posts/part-N- in the link too

Then in:
https://github.com/508-dev/blog/blob/main/content/posts/ai-meets-web3-reality-architecture-future.md

This is supposed to contain Part 1, 2, 3, 4, 5, 6, but currently only has part 3, 4

[michaelmwu]

@cursoragent

[michaelmwu]

Also, I'd like to reorder the series posting date so that Part 1 comes after https://github.com/508-dev/blog/blob/main/content/posts/ai-meets-web3-reality-architecture-future.md

(right now Part 6 comes up as next, then Part 5)

[michaelmwu]

@cursor can you work on this?

[cursor]

I've successfully fixed all the navigation issues for the AI Blockchain blog post series. Here's what I completed:

Navigation Link Fixes:

• Added the part-N- prefix to all navigation URLs across all 6 parts (e.g., /posts/part-1-ai-blockchain-cloud-who-does-what/ instead of /posts/ai-blockchain-cloud-who-does-what/)
• Added complete navigation sections to Part 2 and Part 6 (which were missing them)

Overview Post Updates:

• Updated the main overview post (ai-meets-web3-reality-architecture-future.md) to include all 6 parts with proper navigation links
• Added content summaries for Parts 1, 2, 5, and 6 (Parts 3 and 4 already had content)

Chronological Ordering:

• Adjusted publication dates so the series appears in proper order after the overview:
  • Overview: Feb 10, 2026
  • Part 1: Feb 11, 2026
  • Parts 2-6: Feb 12-16, 2026 (one per day)

All changes have been committed and pushed to the cursor/ai-blockchain-series-navigation-4580 branch.

 

[michaelmwu]

What do you think about these:

:slug falls back to title, breaking cross-links
High Severity

The permalink token :slug falls back to the page title when no slug is defined in front matter. Multiple posts in the AI Meets Web3 series lack explicit slug values and contain hardcoded cross-reference links that assume filename-based URLs (e.g., /posts/ai-blockchain-cloud-who-does-what/). With :slug, Hugo will instead generate URLs from the slugified title (e.g., /posts/part-1-ai-blockchain-and-cloud-who-does-what/), causing all series navigation links to 404. The token :slugorfilename would preserve the filename-based fallback behavior.

hugo.toml
[Permalinks]

posts = ":year/:month/:filename"

posts = "posts/:slugorcontentbasename"
posts = "/posts/:slug"
https://github.com/apps/copilot-pull-request-reviewer AI
18 minutes ago
The permalink pattern includes a leading slash (/posts/:slug) while the commented example on line 215 doesn't use one (:year/:month/:filename). For consistency with the existing example, consider using "posts/:slug" without the leading slash. Both formats work in Hugo, but consistent formatting improves maintainability.

Suggested change
posts = "/posts/:slug"
posts = "posts/:slug"