Yoel Zeldes • 11/8/2016

Pelican and GitHub Pages workflow

Read Original

This technical article details a workflow for deploying a Pelican-generated static blog to GitHub Pages. It explains the conflict between Pelican's default output folder and GitHub Pages' requirement for the master branch to be the site root. The author's solution uses two branches (source and master) within a single repository and automates the build and deployment process using a custom git pre-push hook script.

0 comments
#static-site-generator #github-pages #workflow automation
Pelican and GitHub Pages workflow

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes