From Zero to Site: Implementation Notes

I chose Jekyll for one reason: static delivery with low maintenance.

Personal Blog System Architecture

Current stack:

• Jekyll + Liquid for templating
• Markdown for content
• Plain CSS and JavaScript for full control

The project is split into clear layers:

• _layouts for page skeletons
• _includes for reusable blocks
• _data for profile and project metadata
• _posts and _posts_en for bilingual content

This structure makes design, content, and features evolve independently without large refactors.