Expand stub blog posts to display full content on individual post pages

[Copilot]

Four blog posts stored only a short abstract in their content field. Since BlogPost.tsx renders post.content directly via ReactMarkdown, individual post pages (e.g. /blog/discovering-hidden-trails) showed only that one-sentence teaser with no further body.

Changes

• src/components/BlogPost.tsx — Replaced single-sentence content stubs with full articles for the four affected posts:

  • discovering-hidden-trails — route narrative, technical highlights, wildlife, practical stats
  • sunrise-ride — pre-dawn departure, lower north shore loop, ride stats, tips
  • coastal-adventure — Bondi–La Perouse route breakdown, coffee stops, return leg
  • helm-kanvas-snapshot — plugin overview, problem it solves, key features, getting-started command block, example workflow. Command references use bold formatting; the install command uses a 4-space-indented code block (proper CommonMark, no backtick escaping required).

• tailwind.config.ts — Added @tailwindcss/typography to the plugins array. The prose / prose-invert classes applied to the markdown container in BlogPost.tsx require this plugin to render markdown as styled HTML (headings, lists, code blocks, links, spacing). The plugin was already present as a dev dependency but was not wired into the Tailwind configuration.

Listing pages are unaffected; they already apply line-clamp-3 to truncate previews regardless of content length.

// Before — only an abstract was stored
content: "Last weekend, I explored some spectacular mountain biking trails..."

// After — full article with Markdown structure
content: `Last weekend, I explored some spectacular mountain biking trails...

**The Route**

The adventure began at Terrey Hills and wound through a series of single tracks...
...`

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[miacycle]

@copilot These forward slashes (and the others in this commit) should not need backticks. This is not proper markdown. Ensure proper markdown is used. Ensure that markdown is rendered as HTML and styled appropriately.

[Copilot]

Fixed in 49174b6. Two changes made:

1. Removed all escaped backtick sequences — the triple-backtick code fence was replaced with a 4-space-indented code block (proper CommonMark markdown), and inline command references now use **bold** instead. No backslashes remain in the content strings.

2. Added @tailwindcss/typography to tailwind.config.ts plugins — the prose class on the markdown container was a no-op without it. Now all markdown renders as properly styled HTML (headings, lists, code blocks, links, spacing).

Screenshot of the rendered result:

[Copilot]

Pull request overview

This pull request expands four blog posts from short abstracts to full-length articles with detailed content. The posts now provide comprehensive information instead of single-sentence teasers, improving the user experience when viewing individual blog post pages.

Changes:

• Expanded "discovering-hidden-trails" cycling post with route details, technical highlights, wildlife observations, and practical information
• Expanded "sunrise-ride" cycling post with pre-dawn departure narrative, route description, ride statistics, and tips
• Expanded "coastal-adventure" cycling post with detailed route breakdown, coffee stops, historical context, and return journey description
• Expanded "helm-kanvas-snapshot" tech post with plugin overview, problem statement, key features, installation instructions, and example workflow

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/components/BlogPost.tsx	Expanded content field for four blog posts from single-sentence abstracts to full articles with proper Markdown formatting, including escaped backticks for code blocks
package-lock.json	Extensive dependency flag changes (removing "dev": true from many packages) that appear unrelated to the blog content changes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The term "de-facto" should be written as "de facto" (two words, no hyphen). This is the standard Latin phrase meaning "in fact" or "in practice".

Suggested change

	The Helm Kanvas Snapshot plugin is an extension for Helm — the de-facto package manager for Kubernetes — that integrates directly with Meshery's Kanvas visualisation platform. When you deploy or upgrade a Helm release, the plugin automatically captures a snapshot of the resulting cluster configuration and stores it as a visual, shareable Kanvas diagram.
	The Helm Kanvas Snapshot plugin is an extension for Helm — the de facto package manager for Kubernetes — that integrates directly with Meshery's Kanvas visualisation platform. When you deploy or upgrade a Helm release, the plugin automatically captures a snapshot of the resulting cluster configuration and stores it as a visual, shareable Kanvas diagram.