OpenLake / OpenLake/OpenLake--Website
Feature: Implement blog detail page
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 16
- Avg merge
- 8h 54m
- Merged PRs (30d)
- 7
Description
Implement blog detail page
This is a sub-issue of #15
Overview
Create or update the BlogDetail.jsx component to render individual blog posts from Markdown files with proper formatting and navigation.
Tasks
- Update BlogDetail.jsx to fetch and display a single blog post using the slug from URL parameters
- Implement Markdown rendering with appropriate styling for different elements (headings, lists, code blocks, etc.)
- Add metadata section displaying author, date, read time, and tags
- Include author information with optional GitHub profile link
- Create navigation controls to return to the blog listing
- Add social sharing functionality (optional)
- Implement related posts section based on tags (optional)
- Add syntax highlighting for code blocks
Technical Details
- Use the getBlogBySlug utility from Issue #16
- Implement responsive design for the blog content
- Ensure proper rendering of embedded images and other media
- Use semantic HTML for better accessibility and SEO
- Add proper metadata for search engines
Definition of Done
- Blog detail page correctly renders Markdown content with appropriate styling
- Metadata is clearly displayed at the top of the post
- Navigation controls work properly
- Page is responsive across different devices
- Code blocks render with syntax highlighting
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with BlogDetail.jsx and the getBlogBySlug utility from issue #16, then trace how the slug is supplied by the URL. The work is done when one Markdown post renders with styled content, metadata, navigation, responsive semantic markup, and syntax-highlighted code blocks as described in the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100