A custom CMS website is a hand-coded site with its own editing screens — one for each part you change yourself, such as prices, menus, staff, news or opening hours — and plain pages for everything that stays put. Ozwebnet writes both the site and its editing screens from scratch in Adelaide, South Australia, for businesses across Australia. One fixed quote covers it, staged against milestones, and the source code is handed over with the IP assigned to you.
DETAIL OF SHEET 03 — CUSTOM WEBSITES →
A custom CMS website is a hand-coded site with a content management system written for it, rather than one installed on top of WordPress or another general-purpose CMS. Each part you change yourself — a price list, a menu, a staff page, a news feed, a jobs board — gets its own editing screen with only the fields it needs. You log in, change the text or picture, and the page updates. Pages that stay put remain plain pages with nothing to patch, and both the site and its CMS are yours: source code delivered, IP assigned to you.
Before anything is built we list which parts of the site change, how often, and who on your staff will change them. That list decides which parts get an editing screen and which stay plain pages, and if the content lives in WordPress or a spreadsheet today, it comes across.
A price list gets a price list screen; a menu gets a menu screen; a staff page gets a staff screen. Each has only the fields that part needs, in the order you fill them in, and nothing else.
Photos, PDFs and documents are uploaded from the editing screen, resized for the page they appear on and placed where the page expects them.
Every editor has their own login, and what each one can change is set per person, so one person can update the news and another the prices.
A change can be seen on the page before it goes live and published when it is right, and earlier versions are kept so a mistake can be put back the way it was.
The home page, the about page and anything that changes once a year stay hand-coded, with no editing screen to maintain and nothing to update.
A short written guide for each editing screen, and the source code for the site and its CMS, delivered with the IP assigned to you.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →We list what changes on the site, how often it changes and who will be changing it.
Each editing screen and each plain page is specified in writing; the fixed quote is set here, staged against milestones.
Pages and their editing screens are built together, one part at a time, so each milestone ends with a part of the site you can already edit.
Every screen is tried by the people who will use it, with their own content, and checked on real phones before launch.
At launch the site goes onto your domain with each editor's login ready, and the source code for the site and its CMS is handed over with the IP assigned to you.
No. WordPress is a general-purpose CMS you install and then fit a site into. A custom CMS is written for your site, with one editing screen for each part that changes and nothing else. If your content lives in WordPress today, it comes across.
The parts that change often — prices, menus, stock, staff, news, jobs, opening hours. Anything that stays the same from one year to the next is left as a plain page with no screen behind it. The list of parts that get a screen is agreed in writing at the specification stage.
No. Each screen has plain fields — text, a picture, a price, a date — in the order you fill them in. You change a field, check the preview and publish, and a short written guide comes with each screen.
One fixed quote, set in writing before the build and staged against milestones. What sets the price is how many parts of the site need an editing screen, which is why that list is agreed first.
Yes. The source code for both the site and its editing screens is delivered with the IP assigned to you, so any developer can maintain it after us.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.
