Skip to main content
Q-Code Dev

Suited to

What you can build

Q-Code builds content websites: local business sites, brochure sites, publications and landing pages, where words and structure are the product.

Each of these gets the same foundation, so the difference between them is which parts get used rather than which tier you are on. What it is not suited to is further down, said plainly.

In practice

Four shapes

A local business site

The most common job and the one the template is shaped around. A handful of pages that answer what you do, where, for whom and at what price, with a form that reaches you and opening hours a search engine can read.

  • Services and prices
  • Contact form and inbox
  • Local business structured data
  • Reviews with real ratings

A brochure site that stays current

For a business whose offer changes faster than its website usually does. The pages are code, but the words on them that move most often are data, so keeping them right does not need a developer or a deploy.

  • Editable questions and answers
  • Editable testimonials
  • Legal pages from one config block
  • Social links that update live

A publication

A blog with a schedule, images, categories and a feed. Posts are written to one style contract so the tenth reads like the first, and every post carries the markup that lets it be quoted rather than just crawled.

  • Scheduled or on-demand posts
  • Generated hero and in-content images
  • Article and FAQ structured data
  • RSS and sitemap

A landing page that has to rank

One page, one job, and every mechanism search and answer engines use to decide whether to show it. Answer-first paragraphs, a clean heading outline, and a page that is complete in the HTML before any script runs.

  • Answer-first structure
  • llms.txt and content signals
  • Open Graph and Twitter cards
  • No layout shift

Limits

What it is not for

A tool that will not name its limits cannot be judged, and the fastest way to be disappointed by a build platform is to find its edges by accident.

It is not an application framework

Sites are static files. That is why they are fast, cheap and hard to break, and it is also why a logged-in dashboard with per-user state is the wrong thing to ask it for. The interactive parts it does well are the ones a content site needs: a form, an admin area, a live-updating list.

It does not invent facts about your business

Written content is researched against what the site already says. It will not produce a price, a timescale or a guarantee that you have not given it, and where it cannot answer something it says so rather than filling the gap.

A published post is a commitment

Posts are files, not rows, because each one carries generated images, a feed entry, a sitemap URL and its own structured data. Editing one is a build, and deleting one asks you to type the title, because every link to it in the world stops working.