Kalendrio. Built for software that shows its product, instead of describing it

The structure carries any SaaS with an interface: features, how it works, integrations, pricing, FAQ, blog, changelog, customers, contact. The four mockups are cut for scheduling and live as HTML in four files. Whoever shows a different product rebuilds them or replaces them with views of their own, the grid around them stays. The start skill says up front how big the rebuild will be.

As one Astro component: the data for days, times and the mini month at the top, below it the markup with sidebar and seven columns, the rules at the bottom. An event is one line with column, start row and duration and gets its color from one of five classes. Times, names and calendars are text. There is no image.

Yes, but it is work, not a switch. Ground, surfaces, lines and text sit as variables in one file, so the base is light within an hour. The arc of light, the stars, the glowing surfaces and the shadows of the mockups are built for the dark ground and need values of their own. The design-system skill knows both routes and checks the contrasts along the way.

They get replaced or deleted. Testimonials, key figures, case studies, the timeline and every person are examples and are labelled as such on the page. The knowledge layer explains why unlabelled invented reviews break competition law and why statements about data centers and certificates are contracts, not marketing.

Only in the draft. The six portraits and the office and team photos ship in the package so the site looks finished when unpacked. There is no model release, so no right to show real people under an invented name. Before going live your own photos go in, and the template-setup skill swaps them in every size.

In the package the form shows a success message after submitting, nothing more. That is deliberate, so the site runs on any host. For production you connect a form service, a script from your host or your own endpoint; the knowledge folder describes three routes. The same applies to the two newsletter fields.

Any host that serves files. Astro builds static HTML pages from the project, which belong on web hosting for a few euros a month or on a free static service. There is no database, no application server and no service that creates running costs.

Yes. The Manrope font sits in two files inside the project, the 25 photos likewise, the mockups are HTML, and there is no map and no embedded video. The consent dialogue with three categories blocks the page until a choice is made and is the preparation for services you add. Without consent no connection to third parties happens.

English has no such split, so the English edition simply speaks to the reader as you. The German edition uses the formal Sie because it is written for selling to teams and companies. Switching it to the informal form is a copywriting skill task and takes minutes; the address is a decision in the text, not in the code.

Everything in the package. Code, copy, design, mockups and skills may be used for your own and for client projects without any unit limit. Only reselling the template itself is excluded. The Manrope font is licensed under the SIL Open Font License, and the license file sits next to the font files.

The three legal pages are fully written and carry a visible note that the company, register and people are invented. They are a starting point, not legal advice. The knowledge folder names which details are mandatory and where a lawyer should check, for example the terms for a subscription.

Yes, as its own ZIP with the same website in English, plus the guide, the knowledge folder and the seven skills in English. Calendar, dates and numbers are labelled in English there. The page addresses stay the same in both editions, so one project can carry both.