blog-redesign: Difference between revisions
Jump to navigation
Jump to search
(stiub) |
No edit summary |
||
| Line 2: | Line 2: | ||
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. | 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. ([https://github.com/aaronpk/oauth.net/blob/main/public/webauthn/index.php example source file]) | |||
Revision as of 21:59, 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)