Choosing the right technology for your project
Start with the workflow, editing needs and maintenance team before choosing frameworks.
Part of the series: Smart Decisions
Part 2 / 4
Contents
A technology choice affects how a project is built, who can maintain it and what it costs to change later. Start with the tasks the product must support. A framework name on its own tells you little about whether those tasks will be handled well.
Describe what the system needs to do
Separate public content from application behaviour. A service page may only need to change when an editor publishes. A stock-management screen needs current data, permissions and a reliable way to save changes.
The main parts are the interface, server logic, data storage and hosting. Some projects need all four; a simple static site may not need its own backend or database.
Compare approaches
| Need | Approach to consider | Question to settle |
|---|---|---|
| Articles and service pages | Prebuilt pages, with an optional CMS | Who edits and approves content? |
| Customer accounts and workflows | A web application with backend services | How are permissions and data handled? |
| Online sales | A commerce platform or custom integration | Are payments and fulfilment supported? |
| Mobile or field use | Responsive web, PWA or native app | Which device features are essential? |
Hugo and Astro can suit content-led sites. Next.js and SvelteKit are options for applications. Commerce tools such as Shopify, WooCommerce or Medusa have different operating models. These are starting points for comparison, not a ranking of products.
Include the people maintaining it
Ask an editor to try the proposed content workflow. Check whether developers with the necessary skills are available and whether the system has documentation, tests and an understandable deployment process.
A static site with a CMS still needs updates to its tools, integrations and accounts. An application framework does not supply a complete secure sign-in system merely because it supports server-side code.
Look beyond the build price
Estimate hosting, support, subscriptions, upgrades and the cost of exporting data. Test any essential integration before committing to the full implementation. For an Albanian shop, payment-provider compatibility is an early decision.
Rendering choices also need context. Prebuilt HTML can support rich JavaScript interactions, while a poorly implemented server-rendered page can still be slow. Measure the finished workflow rather than judging by a label.
We use Hugo on this site because it fits the content. For a different project, we assess the requirements again.
Take the quiz for an initial direction or send us your requirements for a more detailed discussion.