A website in Catania: a 2019 figure and hours that change with the season

A business site in Catania has to show today's hours at once, and the season those hours belong to. The population figure needs its year, because ours is from 2019 and does not get younger.

Catania has 311,584 residents on the 2019 figure, in the Città metropolitana di Catania, Sicilia: the oldest number of the five cities we publish, read from Wikidata Q1903 on 1 November 2026. Bari, with 315,473 residents on the 2025 figure, carries almost the same number from a figure six years newer: the difference is not size, it is the date.

The pages a Catania business actually uses

An hours table with a single column goes stale twice a year. You need two columns, season and validity period, plus one row for closures. Someone reading on a phone must know in two seconds whether you are open today: if the answer is "it depends on the season", the page has not finished its job.

A 2019 figure shown as current is a mistake, not a shortcut

Nobody updates a population count by hand, and that is fine. The problem starts when the page shows it undated: the reader assumes it is today's, and six years of drift become a false promise. The correct form is one sentence: "311,584 residents, 2019 figure, source Wikidata Q1903, read on 1 November 2026". If the number decides nothing for the customer, drop it entirely. The comparison with Bari shows why the year matters more than the number.

• Year and date read in the same sentence as the number.
• A clickable source, so anyone who cares can check it in one click.
• No rounding by ear: if the figure is 311,584, that is what you write.
• Seasonal hours in a table, with the validity period alongside.
• The current season stated on the home page, where people look first.

OpeningHoursSpecification: the season inside structured data

The LocalBusiness type accepts openingHoursSpecification, and each entry can carry validFrom and validThrough. That is how you say "June to September 8–13 and 17–20, October to May 9–13" without duplicating the page. Exceptional closures stay out of the schema and go on the page: a readable line beats a structured value nobody updates. The detail is in how to add schema markup.

curl -s "https://ui.eneawork.it/api/blocks/category/faq?limit=200" | jq '.category.count, (.blocks | length)'

Blocks from the catalogue

Three records worth opening now. Table 01 from ephraimduncan is the table to fill with season, days and hours: headers on top, one row per period. FAQ 01 from Shadcn Space holds five questions with open answers, which is exactly what the hours page needs. The faq category holds the alternatives, including accordions that take less room on a phone.

The limitation to state up front

The catalogue holds React and Tailwind components: no opening calendar, no holiday handling, no sync with Google Business Profile. The hours table is interface, the data stays on the site and gets edited by hand. On WordPress these blocks do not install as they are: they work as a structural reference. Previews are free, the full code sits in the Pro part.

Cost and timing

The national 2026 ranges: a landing page 400–1,200 euro, a five to ten page showcase site 1,500–4,000 euro, a structured company site 4,000–10,000 euro. Yearly maintenance for a small CMS site sits between 300 and 1,200 euro, the domain between 10 and 20 euro a year. These are national figures, not Catania prices, and no city has its own list. The full picture is in what a website costs.

For the minimum structure read what a company website needs, for the base choice WordPress, Wix or React components, for the template how to choose a template.