You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copying from a previous email discussion with @webdata:
What I'd suggest we do going forward (at some point, but preferably sooner rather than later) is change the site over from the current WordPress content management system to a modern Git-based system such as Jekyll which is perhaps the most popular such system used for open-source project websites. (But there are others as well.)
This has a number of advantages over the current solution, most importantly:
The WordPress version the current site runs on is outdated and obsolete, and that usually means it is hackable. Defacement and spam links are the eventual fate for WP installations not actively keeping up with the latest updates. In contrast, with a Jekyll site there is nothing to hack--it produces static HTML pages from input Markdown files. One less thing to worry about.
The current site requires PHP and MySQL hosting, which usually costs money or at least webmaster/sysadmin effort. In contrast, Jekyll sites can be directly hosted anywhere that can serve plain old HTML files--in the case of GitHub projects, hosted for free by GitHub themselves. One less thing to worry about.
With the current site, there is no way for non-webmasters to directly contribute fixes and enhancements if they don't have WordPress admin user credentials to the site. With a Jekyll site, they can fork the repository on GitHub, make their fixes, and submit a pull request which can be discussed on GitHub, easily reviewed by the core team, and then merged and published with a single click. Less bottlenecks, more contributions.
The text was updated successfully, but these errors were encountered:
Now that there are some bugs reported against the current website, perhaps time to begin moving forward on this. Any new thoughts on the matter, @webdata?
Copying from a previous email discussion with @webdata:
What I'd suggest we do going forward (at some point, but preferably sooner rather than later) is change the site over from the current WordPress content management system to a modern Git-based system such as Jekyll which is perhaps the most popular such system used for open-source project websites. (But there are others as well.)
This has a number of advantages over the current solution, most importantly:
The text was updated successfully, but these errors were encountered: