A platform choice affects the first build and the next few years of updates. Before choosing one, I want to understand the content, who edits it, what customers need to do and which systems the business already relies on. A familiar platform can still be the wrong fit for the job.
Describe the job before naming the software.
Write down the important tasks: explain services, publish project work, manage a range, take orders or receive a detailed enquiry. Include what happens after the visitor acts. Who receives the information, and which record is the one the business trusts?
Content Design London starts from specific user needs. That is a useful discipline for platform decisions too. A requirement such as updating a product specification means more than saying the business needs a modern website.
Reading behind this section: Sarah Winters / Content Design London
Understand what each approach asks of you.
Astro can suit a content-focused site with a controlled publishing process and selected interactive pieces. Its islands approach allows interactive components to be loaded where needed. It does not automatically provide the editing workflow or business integration a team needs.
WordPress can support an editor-led publishing workflow; Shopify brings store operations into the platform decision. The actual theme, applications, permissions and implementation still matter. None of these names, by themselves, establishes performance, usability or lower whole-of-life cost.
Reading behind this section: Astro documentation
Try a normal update before approving the workflow.
Use a real example: replace a staff profile, add a service page or change a product option. Check whether the editor can update the facts consistently without damaging the layout. A structured field can help, but too many fields can make a simple job cumbersome.
Include image preparation, preview, approval and publication in the trial. The person maintaining the site needs clear boundaries around what they can change and when specialist help is appropriate. A handover should describe that process, not just provide a login.
Account for the parts around the build.
Hosting, subscriptions, extensions, access and data export all deserve a place in the decision. Identify who owns the accounts and what happens if the business changes provider. A migration needs its own checks for URLs, content and enquiry paths.
Search configuration also varies by platform. Aleyda Solis's learning roadmap includes separate CMS guidance, which is a useful reminder to check the implementation rather than assume one universal setup. Choose the platform when the trade-offs are clear.
Reading behind this section: Aleyda Solis / LearningSEO.io
Put it to use
A useful check for your business.
- Write down the customer task and normal editing tasks.
- Try one realistic content update before handover.
- Identify account owners, recurring costs and an exit path.
The thinking behind this guide
Sources & further reading.
Our practical interpretation, with the references below for the specific principles and further detail.
- How to work with user needs
Choose and structure content around a specific user task, rather than a broad subject.
- Islands architecture
Selective interactive components; this describes architecture, not an endorsement for every business.
- The SEO Learning Roadmap
A practitioner-curated learning route through content, technical SEO and measurement; further reading, not proof of a ranking gain.
