blog-redesign: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 25: | Line 25: | ||
=== Simple PHP templates === | === Simple PHP templates === | ||
Similar to oauth.net, use simple PHP templating for the pages. ([https://github.com/aaronpk/oauth.net/blob/main/public/webauthn/index.php example source file]) | Similar to oauth.net, use simple PHP templating for the pages. ([https://github.com/aaronpk/oauth.net/blob/main/public/webauthn/index.php example source file]) | ||
=== Static HTML archive === | |||
* Archive all pages as static HTML, including month pages and tag pages | |||
* New blog post pages would exist entirely outside of the static archive | |||
Revision as of 22:08, 12 September 2024
This article is a stub. You can help the microformats.org wiki by expanding it.
This page is to keep track (project management) of a 2024 microformats.org blog redesign including moving from WordPress to something based on static files in order to drastically reduce admintax and potential for future vulnerabilities/compromises.
Primary Concerns
- All existing blog posts remain, ideally at their existing permalinks, or at least redirecting from current permalinks to new permalinks
- Many blog posts have custom inline HTML and styles, which need to be preserved
- Able to add new blog posts occasionally (this only happens around once a year at this point)
- As little dynamic server code as possible to reduce the chances of vulnerabilities
Types of content
- Blog post permalinks
- Month pages
- Tag pages
Options
Static site generator built on GitHub Actions
- Port the site to some sort of SSG that can be built on GitHub
- Deploy the static built files to the server
Simple PHP templates
Similar to oauth.net, use simple PHP templating for the pages. (example source file)
Static HTML archive
- Archive all pages as static HTML, including month pages and tag pages
- New blog post pages would exist entirely outside of the static archive