Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select CMS for new website #1

Open
artob opened this issue Jun 23, 2016 · 1 comment
Open

Select CMS for new website #1

artob opened this issue Jun 23, 2016 · 1 comment
Assignees
Labels

Comments

@artob
Copy link

artob commented Jun 23, 2016

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:

  1. 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.
  2. 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.
  3. 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.
@artob
Copy link
Author

artob commented Aug 11, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants