Kalendrio

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.