zhravan/zen-mdx-blog

feat: externalize portfolio data to YAML

Open

#3 opened on Oct 15, 2025

View on GitHub
 (5 comments) (0 reactions) (1 assignee)TypeScript (6 forks)auto 404
good first issuehacktoberfesthacktoberfest-acceptedhacktoberfest2025help wanted

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description:

Move hardcoded portfolio data (name, projects, social links) into /data/*.yaml, loaded at runtime (RSC-safe) with optional validation.

Usecase:

  • no code edits required.
  • single source of truth for site content.
  • cleaner components; easier theming/i18n later.

Add /data/site.yaml, /data/projects.yaml, /data/socials.yaml and create yaml parser than can be used wherever required.

This will include, websitename, person name, email, contacts and social media links and favicon too.

This task is blocker to https://github.com/zhravan/monolog-mdx-blog/issues/4

Contributor guide

Research direction
Create `/data/site.yaml`, `/data/projects.yaml`, `/data/socials.yaml` with sample data, then implement a YAML parser that loads and validates these files at runtime (RSC safe). Use a library like `js yaml` for parsing and `zod` for validation. Ensure the data is accessible across components without code changes.
Tech stack
typescriptreact
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75