Can I edit my website without breaking it?

Your prices went up in January. The website still shows last year's. Changing one number should take a minute, but you're not sure what else moves when you touch it, so it goes on the developer's list. Again.

Safe content editing depends on two things: what your editor lets you touch, and how much room the design leaves for what you put in.

What does your setup let you change?

Start with your editor and what your login is allowed to do.

You can edit a website safely when the editor gives you content to fill in (text, images, list entries) inside a layout built to hold it. If your login can also change styles, sections or code, the same editor can change the design.

Log in, find your role under account, team or users, then open a page you want to change. Labelled fields such as Title, Price and Photo mean a content editor. Handles to drag, resize and restyle mean you can change the design too.

Here's what common setups usually allow:

Setup	What you can change	What needs a developer
Custom-coded site with a CMS	The fields and lists set up for you	Anything without a field
Webflow or Framer, content editor role	Text, images, links, CMS items	Layout, styles, components, code
WordPress or Shopify, staff role	Posts, pages, products, if your role allows	Themes, plugins, theme code
AI builder such as Lovable	Text, through inline edits	Everything else is a code change
Hard-coded site, no editor	Nothing directly	Every change, even a typo

The limits come from Webflow, Framer, WordPress, Shopify and Lovable documentation.

Which edits are content, and which aren't?

Filling an existing slot is content. Adding a new one is design or development.

Content you should be able to change yourself:

• Text in existing sections: headlines, service descriptions, prices, opening hours, FAQ answers.
• Images in existing places, such as a new team photo or product shot.
• Entries in lists: blog posts, team members, services. A fifth team member is content when the page is built to list them.
• Page titles, descriptions and share images, which shape how a page looks in Google and in WhatsApp previews.

Work for a designer or developer:

• A new kind of section, or moving sections around.
• Colours, fonts, spacing and button styles.
• Anything that does something: forms, booking, checkout, logins, connections to other tools.

That's also how we scope our own builds. A custom site can include a CMS for blog posts, images and other agreed sections, such as a team page or a services list. Changes to structure, layout, design or functionality are code work.

Some settings look like content and act like switches: one wrong visibility tick can keep a page out of Google.

What does long content do to a layout?

Even permitted content can break a layout built around shorter text or different photos.

Content edits break a layout when the design didn't plan for them: a longer headline, a word that can't wrap, a longer bio or a photo of a different shape.

We built a test page for a hypothetical physiotherapy clinic, opened it in Chrome at phone width (375 pixels) and changed only the content:

• A longer headline (32 to 138 characters) grew from 132 to 440 pixels tall and pushed the "Book a session" button to the bottom edge of the screen.
• An email address in the headline couldn't wrap. The page became 824 pixels wide and scrolled sideways.
• A longer button label was set never to wrap, so it ran off the screen.
• A longer team bio in a fixed-height card was cut off mid-sentence, with no sign anything was missing.
• A portrait headshot in a wide 16:9 frame lost the face to cropping.
• A photo at phone-camera size (4032 by 3024 pixels) weighed 2.6 MB. An 800-pixel copy that looked the same weighed 66 KB.

None of these were editing mistakes. Three small style changes (letting the headline and button wrap, and the cards grow) made the same text fit. Like other mobile layout problems, that's settled when the page is designed and built.

Which editing habits keep the live site safe?

A few habits catch content problems before visitors see them.

• Draft first, then preview on your phone. In WordPress, someone without publishing rights gets Submit for Review instead of Publish. Framer changes reach the live site only after someone with publishing rights publishes them.
• Know where the undo is. WordPress keeps revisions with a Restore button. Shopify suggests you duplicate a theme before customising it.
• Resize photos before uploading, to about twice the width they appear on screen. Some platforms make smaller copies for you; others publish what you upload. PageSpeed Insights flags oversized images, as our guide to slow mobile pages shows.
• Write alt text that does the image's job. The W3C's alt text decision tree says to describe images that carry information and leave decorative ones empty. If a portrait identifies a team member, "Ana, sports physiotherapist" gives more useful information than "Team photo". If the same name is already next to it, empty alt text may be appropriate.

If you're planning a new site and want the editor shaped around what you'll actually change, we can work that out before anything is built. We agree which sections you'll edit through the CMS, and you approve every screen before development starts. If content edits already break the layout of a custom-coded site, that's a repair we'd quote once we've seen how deep it goes. On Framer we can fix it in place, though we'd recommend moving to custom code; for Webflow or a marketing site built with an AI tool, we'd talk about a rebuild. The first intro call is free and needs no brief, or write to hi@aruno.studio, message us on WhatsApp or find us on Telegram at @mihaipostelnicu.

What should you agree before the site is built?

The cheapest moment to get the right editor is before the design is approved.

1. List what you'll change and how often: prices every January, the team twice a year, the blog weekly. Each item needs a field or a list in the editor.
2. Hand over real content, not placeholder text. Your longest service name and bio, a price with "from" and "+ VAT", and the shape of your photos.
3. Ask for rules in the editor. Many CMSs can make fields required or cap their length. Sanity, for example, can require a title of 10 to 80 characters and block publishing until it fits.
4. Agree who publishes, how you preview and how you undo, plus a one-page guide with screenshots.

Send this to your developer:

Before we approve the design, can we agree what I'll edit myself after launch? I'll need to change prices, team members and blog posts. Here are the longest real examples of each. Can you show me those sections with this content on a phone, and show me how to preview and undo a change?

Put that list in the quote alongside the page list.

How do you stress-test your editor?

Test your editor with worst-case content. Use a draft or preview of a page you edit often, checking each change on your phone:

• Replace the headline with the longest version you'd realistically use
• Put an email address in a heading or button
• Add a team member or service with your longest description
• Swap a wide photo for a portrait one, and the other way round
• Leave an optional field, such as a subtitle or photo, empty
• Discard the draft or restore the previous version

If everything fits, keep editing. If the page scrolls sideways, text is cut off or a button leaves the screen, shorten the content for now and ask for the styling to allow longer text. If you couldn't work in a draft or undo, fix that before the next edit.

Frequently asked questions

Can I edit my website if it doesn't have a CMS? Not directly. On a hard-coded site, every change means editing and publishing code. A CMS can usually be added later, once the code is in good enough shape to build on; we add Keystatic or Sanity to custom-coded sites after any cleanup they need.

Can I change a page's address myself? Many editors let you, but links to the old address then break, including Google's. Google recommends a permanent redirect from old to new, so ask whoever manages the site to add one.

Do I have to pay a developer for every change? No, not for content your editor covers. Layout, design and new features are paid work. With Aruno, later changes are quoted as a project or covered by the monthly partnership; our guide to maintenance costs explains upkeep budgets.

How do I give my team access without risking the design? Give each person the lowest role that covers their job. In WordPress, a Contributor can write posts but not publish them. In Shopify, leave out the Themes and Edit code permissions for staff who only manage products.

Last year's prices don't have to wait for the developer. Run the stress test on your pricing page this week, and you'll know whether that change is yours to make.