SiteBricks 1.2.1

Tiny flat-file websites made from Bricks.

Keeping A Website Portable

Website Portability is a useful way to think about what SiteBricks is trying to achieve. The aim is not to recreate every feature of a large content management system. It is to make moving, backing up and restoring a site without hidden dependencies straightforward enough that the owner can concentrate on the website rather than the framework.

Start with the problem



The useful question is not how many features can be added. It is what the site owner is actually trying to accomplish. A modest information site often needs clear pages, dependable links and a design that does not get in the way. Starting there keeps decisions grounded in real use rather than in a checklist borrowed from much larger systems.

Keep the machinery visible



One attraction of SiteBricks is that somebody can open the folder and understand much of the site immediately. Pages, Themes and Bricks have obvious homes. That visibility makes experimentation less intimidating because changes are concrete: add a file, change a setting, copy a Brick or switch a Theme. The framework should preserve that direct relationship between an action and its result.

Prefer capabilities over compulsory features



Core should provide the capabilities needed to assemble and display the site. Optional behaviour belongs in Bricks. This distinction matters because a feature that is useful to one site may be irrelevant to another. Keeping it outside Core means a basic installation does not carry code simply because somebody else might need it.

Test with ordinary work



The best way to judge the idea is to use it. Add pages with spaces in their filenames, change their order, switch Themes, request a missing page and remove an optional Brick. Everyday actions expose awkward assumptions quickly. SiteBricks 1.x should improve in response to those practical discoveries rather than trying to predict an elaborate future architecture.

Leave room to grow



Simple does not mean frozen. New Bricks, Themes and conveniences can appear as people discover real needs. The important discipline is deciding where each improvement belongs. If it can remain optional, it probably should. That lets the ecosystem grow while the Core remains recognisable, small and easy to explain.

What this means for website portability



In practice, website portability should remain understandable from the files themselves. The owner should be able to make a change, refresh the browser and see why the result occurred. Where extra behaviour is useful, a Brick can provide it without turning that behaviour into a permanent Core dependency. This keeps SiteBricks suitable for small personal sites, experiments, documentation and other projects where clarity matters more than scale.

The SiteBricks test



There is a deliberately simple test for every change: does it make the common task easier without making the basic system harder to understand? If it does, it is probably moving in the right direction. If a new feature requires pages, Themes and Core all to become more complicated, it deserves another look. The reaction we want from somebody building their first SiteBricks site is still the same: “That was easy.”

For this test article, the emphasis is on moving, backing up and restoring a site without hidden dependencies. As SiteBricks.co.uk grows, this principle can be tested against the real site rather than treated as theory. That is why the 1.x series matters: small releases can solve problems we actually encounter while keeping the framework useful throughout the process.