About this Project
BlockHubSyS was born from a simple thought: I didn’t want to rely on overly complex CMS systems, nor did I want to keep endlessly tweaking a website.
My goal wasn’t to build a community platform — I just wanted a website: clean, straightforward, and functional.
At first, everything was powered by basic PHP that generated text files. With just two input fields — title and content — I could create pages.The title even doubled as the navigation link. About as simple as it gets.
But it soon became clear: text files aren’t great for managing content. So I switched to generating HTML pages — which quickly led to problems with PHP applications. After that, I tried generating PHP files, but once the site grew beyond 30 pages, that became messy, too.
So I started over, inspired by other systems. In the end, I decided to store all content in JSON and simply load it when needed. That conversion wasn’t easy and took quite a bit of time — and at that stage, there was still no design, nothing that really looked like a website. But the basic framework was finally in place.
The next step: content blocks.
My goal was to keep the system as simple and fast as possible, and to ensure it would work on 90% of standard web hosting environments. That’s why I chose JSON, with the editor itself running on BBCodes — lightweight, flexible, and efficient.
My goal wasn’t to build a community platform — I just wanted a website: clean, straightforward, and functional.
At first, everything was powered by basic PHP that generated text files. With just two input fields — title and content — I could create pages.The title even doubled as the navigation link. About as simple as it gets.
But it soon became clear: text files aren’t great for managing content. So I switched to generating HTML pages — which quickly led to problems with PHP applications. After that, I tried generating PHP files, but once the site grew beyond 30 pages, that became messy, too.
So I started over, inspired by other systems. In the end, I decided to store all content in JSON and simply load it when needed. That conversion wasn’t easy and took quite a bit of time — and at that stage, there was still no design, nothing that really looked like a website. But the basic framework was finally in place.
The next step: content blocks.
My goal was to keep the system as simple and fast as possible, and to ensure it would work on 90% of standard web hosting environments. That’s why I chose JSON, with the editor itself running on BBCodes — lightweight, flexible, and efficient.