OpenLieroX website (Jekyll)

🌐 Live site: https://klirktag.github.io/openlierox-jekyll/

A static Jekyll replica of the original openlierox.net website, built so the site can be hosted for free on GitHub Pages instead of a paid server.

Local development

Requires Ruby and Bundler.

bundle install
bundle exec jekyll serve

Then open http://localhost:4000/.

Deployment

Pushing to the main branch triggers the .github/workflows/jekyll.yml workflow, which builds the site and deploys it to GitHub Pages. In the repository settings, under Settings → Pages, set Source to GitHub Actions.

Custom domain

To serve the site at openlierox.net, add a CNAME file containing the domain at the repository root and configure DNS. Keep baseurl: "" in _config.yml. For a project page (<user>.github.io/<repo>/) the deploy workflow passes the correct baseurl automatically.

Structure

Path	Purpose
_config.yml	Jekyll site configuration
_layouts/default.html	Shared page shell (head, logo, menu, footer)
index.md	Main page
news/, downloads/, screenshots/, help/, faq/, install/, wiki/, forum/	Content pages (index.md in each)
feed.xml	RSS news feed
official/	Original CSS, images and assets from openlierox.net

Editing pages

Every page is a Markdown file (index.md). Each starts with YAML front matter, then the content:

---
layout: default
title: FAQ
permalink: /faq/
---
## A heading

Some **Markdown** content.

The original site uses specific CSS classes. Markdown blocks get those classes via kramdown's inline attribute lists: {:.classname} on the line after a block, or {:.class} directly after an inline image/link. Structural wrappers (e.g. the release boxes and the download-icon grids) are kept as raw HTML inside the Markdown — which is valid Markdown. Always link assets/pages with the relative_url filter, e.g. [Downloads]({{ '/downloads/' | relative_url }}).

Differences from the original site

The original site was partly dynamic (PHP + database). Those parts cannot run on static hosting, so:

• News was database-backed (the live page currently shows a database error). The real posts were recovered from the Wayback Machine and are served as a static page.
• Wiki and Forum ran dynamic software. They are replaced with static landing pages that link to the surviving community resources.
• Google Analytics (a retired tracking property using document.write) was removed.
• A viewport meta tag was added so the fixed 990px layout scales on mobile.

Download links still point to the project's files on SourceForge.