dev #20
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Changes
Related Issues
Checklist
make lint)make test)📋 Pull Request Summary
Adds a self-hosted blog feature using Astro Content Collections and a sample post, plus accompanying documentation updates and a small nginx configuration tweak. The PR introduces a content collection schema, a dynamic post page, and updates developer docs and README to reflect the blog workflow and new color palette.
Type: ✨ Feature
Changes
✅ Added:
blogcontent collection schema (title, date, description, draft).📝 Modified:
absolute_redirect off;to server config.Files Affected
src/content/config.ts- New content collection configuration forblogusing zod schema; declares title, date, description, and optional draft flag.src/pages/blog/[...slug].astro- New dynamic page that builds static paths from the blog collection and renders individual Markdown posts inside BaseLayout with scoped prose styles and a subtle grid background.src/content/blog/love-without-access.md- New blog post (Markdown) added as example content and to demonstrate the blog feature.DEVELOPMENT.md- Large documentation update: describes new src/content structure, blog pages, content schema, instructions for adding posts/images, and swaps the documented color palette to Catppuccin Mocha.README.md- Updated features and setup instructions: mentions Catppuccin Mocha palette, documents the blog, adjusts docker run port mapping and asset guidelines.TODO.md- Project TODO updated to mark the blog implementation complete and refine related tasks (RSS, wording about no CMS).nginx.conf- Small server config change:absolute_redirect off;added (affects how nginx constructs redirects).Impact
🟡 Scope: Medium
Introduces a new blog feature and content pipeline (Astro Content Collections) which affects site structure, build-time routes, and documentation. Reviewers should verify build/static generation, routing for blog pages, markdown rendering, and that public asset conventions (/blog//) and nginx redirect behavior are acceptable. Documentation and Docker run instructions were updated; confirm the port mapping change is intentional.
AI Code Review
AI review encountered an error: Failed to parse JSON response: '{\n "summary": "This PR adds a blog (content collection, markdown posts, and dynamic post page), updates docs (README, DEVELOPMENT, TODO), and makes small infra/config changes (nginx, Docker run example). The blog implementation is mostly complete and includes styling and a long sample post. However, there are several functional correctness and maintainability issues that can break builds (how dynamic routes/props are handled), documentation inaccuracies (Docker port mapping), potential runtime/...'
Summary
Overall Severity:
UNKNOWNAI Recommendation: Changes Requested
📋 Pull Request Summary
Adds a blog to the project using Astro Content Collections: new content schema, routes to render Markdown posts, and an initial post. Documentation, TODOs, and README were updated to reflect the blog and a new Catppuccin Mocha color palette; a small nginx config tweak and a Docker run port example were also changed.
Type: 🔀 Mixed
Changes
✅ Added:
blog(title, date, description, draft)📝 Modified:
absolute_redirect offFiles Affected
src/content/config.ts- New Astro content collection config defining theblogschema (title, date, description, optional draft flag).src/pages/blog/[...slug].astro- New dynamic route to generate static paths for non-draft blog posts and render Markdown content with layout, styling, and date formatting.src/content/blog/love-without-access.md- New blog post (Markdown) added to the content collection as the initial example post.DEVELOPMENT.md- Documentation update: file tree extended to include content/blog, blog authoring and image guidance, color palette swap to Catppuccin Mocha, and updated page/section breakdown.README.md- README updated to advertise the blog feature, show new palette name, add blog/image setup instructions, and change the example Docker run port mapping.TODO.md- Task list updated: marks blog implementation (Astro content collections) as done and tweaks related items (RSS, analytics notes).nginx.conf- Small server config change:absolute_redirect offadded (affects how nginx rewrites redirects).Impact
🟡 Scope: Medium
Introduces a new blog feature and content pipeline that affects routing, build-time content collection usage, and documentation. Requires Astro's content collections support and proper static image placement under public/blog/. Minor operational impacts: README's Docker run example maps host port 3000 to container port 80 (adjust if your container serves a different port), and nginx redirect behavior is slightly changed. Overall, non-breaking if the environment supports Astro content collections and existing assets are unaffected, but reviewers should verify build settings, dependency compatibility (astro/content + zod usage), and container/NGINX port expectations.