Everything under the hood
Fast, findable and easy to publish — built, tested and ready before the first block is added.
Images
Pictures that fit every screen
Every photo is resized and compressed for the screen it lands on, so a phone never downloads a desktop photograph. Pages feel instant, and the pictures still look sharp.
- Quality tuned to the job: photos, thumbnails, banners, backdrops
- A modern format that keeps files small without changing how they look
- Uploads from the media library are optimised automatically
Search
Found by Google, on purpose
Every page follows a written set of search guidelines: tidy addresses, a sitemap of the pages worth indexing, and a simple checkbox to keep a page — like a thank-you or 404 page — out of results.
- A proper title, description and share picture on every page
- Your site name shown correctly in search results
- A sitemap and crawl rules ready for each environment
Publishing
One click to production
Publishing builds the site and puts it live on fast, secure hosting. Testing, staging and production all work the same way — and a trial environment can be taken down again, leaving nothing behind.
- The same steps for every environment
- Settings for each environment are passed in explicitly, never guessed
Optional extra
An optional app mode
Visitors can add the site to their home screen like an app. After their first visit, its pages open even without a connection, though pictures they have not viewed will not load. It is one setting, on or off, so you choose whether your site offers it.
- One icon, rendered for every device
- A single switch to keep it off while you are still testing
One engine, many sites
The core machinery — how blocks are found, checked and drawn — is identical in every HUGways site, and an automatic check proves it. What differs from site to site is a small, clearly labelled set of options; everything else a client changes is content.
If a site ever drifts from the base, the check names exactly what changed and how to put it right. That is why improvements to the base can reach every site.
Under-the-hood questions
Why a static site?
Static pages are fast, cheap to host and have nothing to patch. When someone edits in the CMS, the site rebuilds — the visitor still gets plain, quick pages.
How do I know the blocks and the editor agree?
Automatic tests check every page and template against what each block accepts, confirm every picture exists, and make sure the editor's description of the blocks is up to date.
Can a site look or behave differently from the base?
Yes — in a few named places: the brand, the theme and a handful of options. The rest is shared on purpose, so every site gets the same improvements.
A base you can trust
Built, tested and deployed — before the first block is added.
