github-data-poster

You can publish local blog content to GitHub Pages by running the build_site.py script, which converts your local blog_data into a complete static site directory with Home, Category, and Post pages alongside copied image assets.

Content.txt rendering works by parsing the text file and converting it into HTML while preserving the exact order of text and inline image markers. Per-post image assets are copied into the published directories to maintain stable links.

Yes, you need Python to generate a GitHub Pages blog from local data because the Skill relies on executing a Python script, build_site.py, to process the blog_data resources and rebuild the site structure.

The best way to organize local blog posts by category is to structure them within a blog_data directory containing individual post folders with content.txt files, allowing the build script to automatically generate category navigation metadata and accessible post links.

The Skill lists markdown as a dependency, indicating it processes markdown formatting within content.txt files to render the final HTML post pages for your GitHub Pages static blog.

Image assets may not show up if the per-post image files are missing from the blog_data resources or if the inline image markers in content.txt are incorrectly formatted, as the script relies on these to copy assets and preserve filenames for stable links.