A Farm Website Without a Content System
A project where the right decision was to add nothing. No CMS, no store, no plugins — only as much as it takes for the farm to be found in search and called.
Updated
aronijos.lt
HTML • Tailwind CSS • SEO
What mattered most here
The decisions on this project were made by subtracting rather than adding.
The content barely changes
The produce, its properties and the delivery terms are constants. For content like that a CMS is a maintenance burden with no benefit — so there is none.
No store was needed
Orders are placed directly by phone, and delivery runs once a week within the region. A cart and payments here would solve a problem that does not exist.
Local search
The farm works in a specific region, so what matters is not general traffic but being found by someone looking for organic berries near them.
What this site is
Aronijos.lt is the website of an organic farm. The farm grows certified organic berries — chokeberries, guelder rose and elderberries — and produces honey. The site has information about the farm and its approach to farming, descriptions of the produce, a section on the properties of the berries, frequently asked questions and contacts.
Delivery is made by the farm’s own transport once a week in the Kaunas and Marijampolė regions, above a certain order size. Orders are placed directly, by phone or through the contacts.
Technically it is hand-written HTML with Tailwind CSS, with no content system and no online store.
Why there is no content system
This is the only project in the portfolio whose main decision was to add nothing. A content system makes sense when the content changes and when the client is the one changing it. Neither is true here.
The produce list, the properties of the berries and the delivery terms are constants. Seasonal changes happen a few times a year, and that volume does not justify a system that has to be updated, maintained and secured all year round.
Three practical consequences follow: the site loads fast, because there is nothing superfluous on the page; there is nothing to break into, because there is neither a panel nor plugins; and there are no recurring maintenance costs.
Why there is no online store
The farm sells directly: a call, an arrangement, delivery in its own region once a week. A cart, a payment integration and delivery options would solve a problem that does not exist here, while bringing along everything that comes with a store — payment systems, delivery rules and legal texts to keep current.
A store has to pay for itself. If orders are not being held back by the absence of a cart, adding one changes nothing except the costs.
What SEO was solving here
The farm works in a specific region, so what matters is not general traffic but that the site is found by someone looking for organic berries near them. That needs clearly named produce, a stated delivery area and contacts — the same things a person is looking for and a search engine reads.
Speed adds to it. Plain HTML with Tailwind CSS is the fastest option available precisely because there is no system assembling the page on every request.
Who the same solution fits
If your site will have a few pages, the content will change a few times a year, and orders come in by phone, you need neither a CMS nor a store. A project like that costs less, loads faster and needs no ongoing maintenance.
When the content starts changing regularly and the client fills it in themselves, the answer goes the other way — as it did on Šviesi galva. And if you already have a site that has grown slow, the place to start is an audit.
FAQ
Questions this kind of solution raises.
Without a CMS, can the site be updated at all?
It can — it is just done by me rather than by the client. When changes happen a few times a year, that is cheaper and simpler than maintaining a system nobody logs into. Hourly maintenance starts at €8 per hour, billed only for work done.
What does a site like this cost?
A small site of 1–3 pages starts at €120. That includes a responsive layout, image and font optimization, basic SEO and submission to Google Search Console.
Could a store be added later?
It could. But it is worth starting with the question of whether orders are really being held up by the absence of a cart. An online store adds payments, delivery rules and legal texts to maintain, so it has to pay for itself rather than be added in advance.
Why is a plain HTML solution faster?
Because there is nothing on the page that does not need to be there. No system assembling the page on request, no plugin code, and no theme bringing in features for every conceivable case.
What is next
- Website speed optimizationGot a site that is slow? The audit comes first, the decision after.
- Business website developmentThe other end of the scale: Astro.js with a headless CMS when content changes often.
- Šviesi galva — a school websiteThe opposite case: a project where a content system was essential.
Not sure what you need?
Write what the site has to do — if something simpler and cheaper is enough, that is what I will tell you.
Get in touch