Suggestion: move from PHP to Markdown and Jekyll, serve with GitHub Pages

[vinyanalista]

I would like to suggest an enhancement that I believe would make your life (our lives) easier.

Although your website is written in PHP, it shows only static content. Why don't you rewrite it using Markdown and Jekyll?

Doing that, you could serve it using GitHub Pages. Your GitHub repo would host both your source code and web site.

If you want to see it in action, take a look at:

• https://github.com/kamarada/guiadoopensuse/tree/d1fb85f0c9b1b3c36288b515ce8df492b32c4173 (source, in Markdown / Jekyll)
• https://kamarada.github.io/guiadoopensuse/ (website, served by GitHub Pages)

I have already rewritten your website using Markdown and Jekyll, because I'm going to publish my derivative using GitHub Pages. First I converted all the PHP pages to Markdown pages (.md extension), now I'm going to translate the content to Brazilian Portuguese.

That's why I referenced a specific commit in the above link, because soon I'm going to start translating, but right on that commit my repo is just a fork of yours but converted to Markdown.

If you agree with moving to GitHub Pages, we can do just a "copy and paste" from that commit to your repo. Please let me know if you want me to do a pull request.

Also, you are able to use a custom domain with GitHub Pages, so you could keep using http://opensuse-guide.org/ (instead of moving to, let's say, https://cb400f.github.io/opensuse-guide.org/).

Thanks for the great content and keep up the good work!

[vinyanalista]

Also, note that Markdown allows you to focus on content. Although you can use HTML tags for specific needs, most of time you don't need them. They are inserted by Jekyll while compiling HTML pages from your Markdown source.

For example:

<h1>A title</h1>

In Markdown would be written:

# A title

Another example:

<a href="https://www.google.com/">Google</a>

In Markdown would be written:

[Google](https://www.google.com/)

As another example, compare:

• https://raw.githubusercontent.com/cb400f/opensuse-guide.org/ea98a183eae342ede3fe1477f1a07ba31beb6317/apps.php
• https://raw.githubusercontent.com/kamarada/guiadoopensuse/d1fb85f0c9b1b3c36288b515ce8df492b32c4173/apps.md

The second is smaller, cleaner, easier to read and maintain, and result is the same:

• http://opensuse-guide.org/apps.php
• https://kamarada.github.io/guiadoopensuse/apps