How to update your website content
Two ways to keep a site current, depending on how yours was built. Send us the change and we handle it end to end, or log in and edit it yourself in WordPress. This covers both — including exactly how the Enfold builder works, and the handful of things in there that will break a page.
On this page
On this page
A website that still advertises last winter's menu does more damage than no website at all. Keeping one current isn't hard — but how you do it depends entirely on how yours was built, and the two paths are genuinely different jobs. Work out which one you're on first.
Which site have you got?
- Built by us as a Caidence site? There's no login, because there's nothing to log into. You email us the change and we do it. Skip to Option 1.
- WordPress with the Enfold theme? You have a username and password, and a page builder you can use yourself — or you can still just ask us. Skip to Option 2.
- Not sure? Try
yoursite.com.au/wp-admin. A WordPress login screen means Enfold. A "page not found" almost certainly means Caidence. Or just ask us — quicker than guessing.
Either way, the important part is the same: somebody has to actually own it. The sites that go stale aren't the ones with the wrong tooling, they're the ones where updating the website is nobody's job in particular.
01 — The choiceThe two ways at a glance
Both work. They ask very different things of you.
| Caidence site | WordPress + Enfold | |
|---|---|---|
| How a change happens | You email us; we do it | You log in and edit it, or ask us |
| What you need to learn | Nothing | The Enfold builder |
| Logins to manage | None | One per person who edits |
| Checked before it goes live | Always — you approve a preview | Only if you preview it, or ask us to review |
| Software to keep patched | None on the site itself | WordPress, plugins and the theme |
| Can it break from an update? | No — there's nothing to update | Yes, and it does happen |
| Suits you if… | You'd rather it just be handled | You want hands-on control and have someone with the time |
For most clubs and pubs, Caidence — and not because it's ours. It's because in venue after venue we watch the same thing happen: the person who learned the builder moves on, the login goes with them, and eighteen months later the site is still advertising a Melbourne Cup lunch. Removing the website from your team's list of things to remember is the single change most likely to keep it current.
If you genuinely want to be hands-on — you've got someone in marketing who enjoys it and has the hours — WordPress is a perfectly good answer, and we'll support you in it.
02 — Option 1Send it to us — the Caidence way
Caidence sites are hand-built HTML. There's no dashboard, no builder and no login, which sounds like a limitation until you see what it removes. You send the change; we make it; you see it before anyone else does.
The process, start to finish
You email the change
To support@cyberry.com.au, with the final wording and any images attached. There's a template further down that gets you a same-day turnaround more often than not.
We build it and put it on a private preview
Your change goes onto a staging copy of your site first — a private link only you and we can see. Your live site is untouched at this point.
You get a review email with an approve button
Open the preview link, check it reads the way you meant it, and click approve. If it's not right, reply and tell us — no limit on going back and forth before it's live.
We publish it
Once you've approved, it goes to the live site. You get a confirmation with the live link so you can see it in place.
Why we push people toward this
- It's less work for you, not more. Writing "can we change Friday's raffle to 7pm" in an email takes fifteen seconds. Logging in, finding the page, working out which element holds that text, editing it, previewing it and publishing it takes fifteen minutes — and that's when nothing goes wrong.
- Nothing half-finished ever reaches the public. Every change is staged and approved first. Compare that with editing live, where a mis-click publishes a broken layout to everyone who visits in the next hour — including Google.
- There are no updates to install and no plugins to patch. The site is HTML. There's no database, no plugin layer, and no admin login on the public site — so the entire category of "the website broke after an update" and "the website got hacked through a plugin" doesn't apply.
- It's fast, and it stays fast. No database query, no plugin stack — pages are files, served as-is. That matters most on a phone on club Wi-Fi.
- Nobody on your staff has to be "the website person." No login to hand over when someone leaves, nothing to retrain, no knowledge walking out the door.
WordPress itself is not the problem, and we're not going to pretend it is — its core code is well looked after. The risk sits in the layer bolted on top. In Patchstack's 2025 figures, 91% of newly disclosed WordPress vulnerabilities were in plugins and 9% in themes, while WordPress core accounted for six, all low priority. The awkward part is that around 46% of those vulnerabilities had no fix available from the developer at the time they were made public.
That's a maintenance burden, and it's real whether or not anything ever goes wrong. A static site simply doesn't have that layer. There's still a server, a certificate and DNS to look after — that's our job either way — but there's nothing on the site itself waiting to be patched.
Caidence is our development brand — it's how we build websites, kiosks and bespoke software for venues. If you want to see what it covers, there's an overview on this site and more at caidencesystems.com.
On timing: tell us your deadline in the request and we'll confirm it when we acknowledge the job. Small text and date changes are usually quick; anything involving new design or new pages we'll come back to you with a time.
03 — Option 2WordPress with Enfold
Enfold is a long-established WordPress theme built around its own page builder — the Advanced Layout Builder, sometimes called the Avia builder. Instead of typing into one big text box, you assemble a page out of blocks: sections, columns, text, images, buttons.
It's capable, and it's the most common thing we inherit when a venue comes to us with an existing site. If that's you, there are three ways to work — and they're not mutually exclusive. Pick per change.
You do it
Best for small, familiar edits
- Changing a date, a price, a phone number
- Swapping one photo for another the same shape
- Adding an event to a page that already lists events
You ask us
Best for anything structural, or anything urgent
- New pages, new sections, layout changes
- Anything you'd rather not risk on a Friday
- Same email, same address — support@cyberry.com.au
This is the one most people don't realise is available, and it's often the best of both. Make the change yourself, publish it, then email us and ask us to look over it. You get it up straight away without waiting on us; we come along behind and check the things that are easy to miss — how it looks on a phone, whether the heading levels are right, whether that image is a 6 MB file slowing the page down, whether anything else on the page shifted.
Say so in the email — "published this myself, can you check it over" — and we'll clean up rather than second-guess whether you wanted it touched.
04 — AccessLogging in safely
Your WordPress login lives at yoursite.com.au/wp-admin. A few rules that save real pain:
- One account per person — never a shared "office" login. When someone leaves you disable their account instead of changing a password everybody knows.
- Use a password manager, not a note in the drawer and not the same password as the POS. The admin area of your website is worth protecting properly.
- Ask for the least access you need. Editing pages doesn't require a full Administrator account — an Editor account can change content but can't install plugins or break the theme. Ask us to set that up; it's a five-minute job and it removes most of the ways a site gets accidentally damaged.
- Tell us when staff change. If someone with a login leaves, let us know the same week so we can close the account.
- Never email a password. If you need to get one to us, ring — or better, ask us to reset it at our end.
05 — EditingEditing a page with the Enfold builder
Find the page
In the left-hand menu, Pages → All Pages. Click the title of the page you want. (If you're editing a news item or blog post, it's Posts instead — same idea.)
Make sure you're in the right editor
Enfold pages are usually built in the Advanced Layout Builder, and you'll see a page made of stacked blocks rather than one long text area. There's a button to switch between it and the standard WordPress editor. Don't. More on this in a moment — it's the one mistake that costs a whole page.
Find the element holding the thing you want to change
Click on it. A settings panel opens over the page with that element's content and options in it.
Make the change and close the panel
Edit the text or swap the image, then save/apply to close the element panel. That updates the element in the builder — it has not gone live yet.
Preview it
Preview Changes opens your edit in a new tab, on the real site, without publishing. Look at it on your phone too, not just the desktop.
Publish it
Happy? Hit Update. Not finished? Save Draft keeps your work without putting it live, and you can come back to it.
How an Enfold page is put together
Understanding the nesting saves a lot of confusion. Elements come in three groups in the builder:
| Group | What's in it | What it's for |
|---|---|---|
| Layout Elements | Color Section, Grid Row, Columns | The containers. A Color Section is a full-width band down the page. A Grid Row holds one to five cells side by side, each able to have its own background. Columns split a section into halves, thirds and so on. |
| Content Elements | Text Block, Heading, Button, Table, Accordion | The words and the calls to action. A Text Block is where nearly all body copy on your site lives — it's the element you'll edit most. |
| Media Elements | Image, Video, Gallery, Slider | Pictures and video. Most hero banners and photo strips are one of these. |
Content and media elements go inside layout elements. Worth knowing: full-width elements like a Color Section can't be dropped inside a column — if the builder refuses to let you place something, that's usually why.
Changing text
Click the Text Block, edit the words, apply, then Update the page. A few habits worth having:
- Type into the page, don't paste from Word. Pasting from Word or a PDF drags invisible formatting in with it and the text comes out a different size or font. If you must paste, paste as plain text and re-apply any bold yourself.
- Don't fake a heading with big bold text. Use the Heading element or the heading styles. Google and screen readers use real headings to understand the page; bold text tells them nothing.
- Don't hand-colour text to make it stand out. It'll drift away from the rest of the site, and it's the most common reason a page starts looking homemade.
Swapping an image
- Replace like with like. Put a wide photo where a wide photo was. Drop a tall portrait shot into a wide banner slot and it'll crop to something unusable, usually through someone's forehead.
- Resize before you upload. A photo straight off a camera or phone can be 6–12 MB. That's fine for print and terrible for a web page — it's the single most common reason a venue site feels slow. Aim for under about 400 KB for a full-width image. Send them to us if you'd rather not deal with it.
- Fill in the alt text — a short plain description of what's in the photo. It's what someone using a screen reader hears, and search engines read it too.
- Check the same rules as any venue content — no gaming machines in frame, permission for anyone identifiable. Our content capture guide covers that in detail, and it applies just as much to a photo you're putting on the website.
06 — Safety netPreview, publish, and undoing a mistake
Preview before you update. Every time. It costs ten seconds and it's the only step between you and the public seeing a mistake. Check it on a phone as well — most of your visitors are on one, and the layout that looks fine on a 27-inch monitor is where problems hide.
If you've already published something wrong
Don't panic and don't start re-typing from memory. WordPress keeps a history of every saved version of a page:
Open the page in the editor again
Same route — Pages → All Pages → the page title.
Find Revisions
It sits in the page's settings panel alongside the Update button. If you don't see a panel on the right, open it with the settings icon next to Update.
Slide back through the versions
The slider at the top steps through saved versions with a before-and-after comparison, so you can see exactly what changed.
Restore the good one
Restore This Revision. Restoring doesn't throw anything away — it saves the old content as a new version, so you can always go forward again.
They'll undo a wording change beautifully. They won't help if a plugin update takes the site down, or if a whole layout gets wiped by switching editors. That's what actual backups are for — ask us what's in place for your site if you don't know, and if the answer makes you uncomfortable, that's worth a conversation.
07 — LimitsWhat not to touch in WordPress
Everything in the "don't" column has cost someone a day's work at some point. None of it is guesswork.
This is the big one. The Advanced Layout Builder and the default WordPress editor store their content in two different formats, and there's no clean conversion between them. Flip a page that was built in the builder over to the standard editor and the layout doesn't come with it — you'll be looking at a wall of code fragments or an empty page, and rebuilding it by hand.
If a page looks like stacked blocks when you open it, it's a builder page. Leave it that way. If you've already done it — stop, don't save, and call us.
Fine to do yourself
- Edit text in a Text Block
- Swap an image for one the same shape
- Change a button's label or link
- Add an item to a list or accordion that already exists
- Duplicate an existing event or news post as a starting point
- Save drafts and previews, as much as you like
- Restore a revision
Leave to us
- Switching a page's editor
- WordPress, plugin and theme updates
- Installing or deleting plugins
- Enfold's Theme Options — logo, colours, fonts, global layout
- Appearance → Theme File Editor, and anything mentioning CSS or code
- Deleting a Color Section (it takes everything inside it)
- Menus, permalinks and page URLs
- Anything in Settings, Users or Tools
Why we ask you to leave updates alone
Plugin and theme updates are the part of WordPress that looks harmless and isn't. An update can quietly change how a page renders, and Enfold in particular needs its own attention: theme updates are tied to a purchase token, and any custom work belongs in a child theme so it survives the update. On a site we look after, we do these on a staging copy first, check the pages that matter, and only then apply them to your live site.
If you see the "updates available" badge, you don't need to do anything. If it's been sitting there for months and nobody's told you it's handled, that's worth an email — ask us who's responsible for updates on your site. It's a fair question and you should know the answer.
Updates, backups, checking the site after WordPress changes underneath it, and doing the content changes you'd rather not — that's the kind of ongoing work our Flex Retainer covers, alongside the rest of your venue's technology and marketing. One arrangement rather than a separate website invoice.
08 — Working with usWriting a change request we can action straight away
This applies to both kinds of site. The difference between a change that goes out today and one that takes three days is almost always how much back-and-forth the first email avoids.
Copy this into an email to support@cyberry.com.au
- Page
- Which page, and paste the link if you can — e.g. "the What's On page, yoursite.com.au/whats-on"
- What's changing
- Point at the existing words. "The line that currently reads 'Raffles every Friday from 6pm'"
- Change it to
- The exact final wording, spelled the way you want it published. "Raffles every Friday from 7pm"
- Deadline
- A real date. "Needs to be live before Friday 1 August" — or "no rush", which is just as useful to know
- Attached
- Any images at full size, any PDF menu, any logo — as attachments, not pasted into the email body
- Anything else
- Consents for photos, things that shouldn't be shown, related pages that need the same change
Nothing formal required — a plain email in this shape is enough. The point is that we can act on it without a phone call.
The things that slow a request down
- Text inside a screenshot or a PDF. We have to retype it, which means we can introduce a typo into your words. Send copy as text.
- "Can you make it look better?" Tell us what's bothering you about it and we'll have something to aim at.
- Images pulled off Facebook or a screenshot of a poster. They come out blurry at web size. Ask your designer for the original, or send us the source file.
- Five emails in a row as you think of things. One email with everything in it, or a reply on the same thread, keeps the whole change in one place.
- Copy that hasn't been signed off internally. If your GM or board needs to approve the wording, do that before it comes to us — otherwise we build it twice.
09 — HousekeepingContent that always needs a second look
Whoever makes the change, these are the things that quietly go wrong on venue websites.
10 — QuestionsThe ones we get asked
Can I get a login for a Caidence site?
There isn't one to give — the site is HTML files rather than a content system, which is precisely why there's nothing to keep patched. If self-editing matters more to you than that, say so and we'll talk about the options honestly rather than talk you out of it.
What if I break something in WordPress?
Tell us straight away and don't try to fix it by making more changes — that's what turns a five-minute repair into a long afternoon. Note what you were doing when it went wrong; it's usually the fastest way to the cause. Most content mistakes are one revision restore away from fixed.
Who owns the site and the domain?
You do. It's your domain, your content and your site. If you ever move to another provider we'll hand over what's ours to hand over — ask us and we'll set out exactly what that means for your particular build.
What do content changes cost?
Depends on the arrangement you're on — most venues have changes covered under a retainer, which is usually the cheapest way to do it if you change things more than occasionally. If you're not sure what your arrangement covers, ask and we'll tell you plainly. We'd rather you asked than sat on a change because you were worried about a bill.
Can we move an existing WordPress site to Caidence?
Usually, yes — and it's a rebuild rather than a conversion, so it's the right moment to fix whatever's been annoying you about the current site. Worth doing if you're paying for maintenance on a site nobody logs into, or if the site has broken after updates more than once. Not worth doing if you've got someone who genuinely uses the builder every week and likes it.
How often should we be updating the site?
Trading hours and prices: the moment they change. What's On: weekly or fortnightly. Photos: whenever you've got better ones. A site that changes gets visited again; one that never changes gets checked once and bookmarked never.
Can more than one person edit the WordPress site?
Yes, and they should each have their own account. Ask us to set them up as Editors rather than Administrators — they'll be able to do all the content work without being able to reach the settings that break things.
Will changing the website affect our screens or kiosk?
No — they're separate systems. Venue screens run on PixelSuite and kiosks are their own build, so a website change doesn't touch them. Do tell us if a promotion needs to appear in both places, though, so we can keep the wording and artwork consistent.
11 — Print thisBefore-you-publish checklist
For anyone with a WordPress login. Print it and keep it wherever the website gets edited.
Website edit — before you hit Update
Cyberry Know-How · cyberry.com.au/know-how
Before you edit
- Logged in as yourself, not a shared account
- Final wording signed off internally
- Images resized for web (under ~400 KB)
- Page opened in the Enfold builder — editor not switched
- You know which element you're changing
Before you publish
- Previewed, not just edited
- Checked on a phone as well as a computer
- Dates and days actually agree
- Prices and hours current
- Alt text added to new images
- No gaming machines in any photo
- Old version of what you replaced taken down
- Links clicked and working
Last reviewed 25 July 2026. WordPress and Enfold both change over time, and menu names move between versions — if what's on your screen doesn't match what's written here, ask us rather than guessing. Nothing on this page is a substitute for what your own arrangement with us covers; if you're unsure who does what on your site, that's a one-email question.
- Enfold documentation — intro to the layout builder
- Enfold documentation — Color Section and Grid Row
- Enfold documentation — theme updates and registration
- WordPress — restoring a revision of a page or post
- Patchstack — State of WordPress Security (vulnerability split between core, plugins and themes)
Tired of being the website person?
Hand it over and get on with running the venue.
Whether your site stays on WordPress or gets rebuilt properly, we can take the updates, the maintenance and the worrying off your desk.