Kehrwelt

From a stage between 20 and 52 km and your own speed between 12 and 22 km/h it works out the riding time, the arrival at the house and the free hours before dinner. The start is at nine, and it adds two and a half hours for breaks, lunch and a swim. Climbing is deliberately left out, and the note below says how much time 300 m of climbing costs without a motor. The stages come from the trip data, the calculation sits in src/lib/tempo.ts.

As a rule yes, and the template is built for it. Trip planning names the standard information form and the insolvency protection certificate before the deposit, the cancellation charges are flat rates under German package travel law (§ 651h of the German Civil Code) with notes on lower actual costs, unavoidable circumstances and a substitute traveller, and the legal notice explains the duties of a package organiser in Germany. Check customer money protection, travel terms and your cancellation rates before going live, these notes are not legal advice.

Every date sits as day and month in src/data/site.ts, and the build works out the year for each date, this year if the date is still ahead, otherwise next year. So every trip always shows its next departures, and the page adds sample dates with the year. Anything that has passed is hidden by the script everywhere in case the site has not been rebuilt for a while, and trip planning only offers future dates. The info evenings on the contact page are the first Thursdays from the build date, three of them shown, and the year in the footer comes from the build date too.

Three groups, month from April to October, pace easy, moderate or hilly, and length seven to eight or nine days. A counter says how many trips match, if none does a sentence with a link to the enquiry appears, and a button resets everything. The months come from the dates of each trip, and the build checks that travel months and dates agree.

A typical cycling day in seven stations, from breakfast at seven to the harbour at ten. A slider picks the time, the matching station lights up, and from the evening on the picture changes from the bike on the coast to a lane in the city. Without scripts the whole list stands there with both pictures.

With an entry under reisen in src/data/site.ts, with country, day side and evening city, days, distance, climbing, price, day by day plan, journey legs, CO2, dates and questions. That creates the trip page, turning line, card, departure board, filter, comparison, month table, trip planning and footer. The alt texts of the pictures sit in src/data/alt.ts.

No, there is no booking system built in. Trip planning collects a non binding enquiry with trip, date, bike and room, and the booking follows after the conversation with the standard information form and insolvency protection certificate. If you use a booking system, let your AI put its link or embed on the form and buttons and add it to the privacy policy and consent.

Both forms check name, email and the privacy policy tick box, the contact form checks the message too. They mark errors at the field, and the message disappears as you type. Afterwards a confirmation appears that says plainly the template sends nothing. The forms are set up with method="post", your AI sets up the sending.

Yes, with some rework. Day side and evening side carry any trip with two parts, walking and a city, say, or sailing and a harbour. Your AI renames bike, stages and climbing and drops the Pace calculator and the bikes, while the turning line, dates, journey legs and trip planning stay.

No. Operator, team, prices, dates, CO2 figures and sample reviews are invented, and the footer of every page says so. The address in Münster is a sample, the phone number comes from the range the German Federal Network Agency keeps free for media use. Regions, cities, stations and ferry routes such as the Alentejo, the Douro, Bornholm, Vis, Naxos, the Amalfi Coast or Ancona to Patras are real, houses and restaurants are not named.

The 66 photos come from Pexels under the Pexels licence, none of them is AI generated. They show neither the trips described nor the team. People appear on 21 photos, none with a recognisable face, and there is no model release. src/data/bildnachweis.json and the legal notice name the photographer of every picture, the file adds source and licence.

Because no stock photo should sit next to a real name. The four people in Münster appear as initial plaques with role and a line of their own, and the note below says that your own team photos belong there. Reviews appear without faces and are marked as sample reviews.

No. Brygada 1918 and Manrope sit in public/fonts/, the photos in the project, while mark, map and bars are drawn. The browser runs its own JavaScript without a library, around 6 KB gzipped. The cookie window writes the choice to the dataLayer, and statistics and marketing are not connected to any service.

Yes. Every page has its own title, description and breadcrumbs, plus a TravelAgency schema with address and opening hours. Every trip carries TouristTrip with an offer and FAQPage, the trips page ItemList, the articles BlogPosting, About us AboutPage and Contact ContactPage. Astro builds the share images at 1200 by 630 pixels from a photo of each page. Legal notice, privacy policy and 404 are set to noindex and left out of the sitemap.

Informally throughout, and the operator speaks as we. The script texts sit in src/data/texte.ts, the openings of all pages in src/data/heros.ts, the content in src/data/site.ts, inhalte.ts and journal.ts. Your AI switches to a formal tone if your business prefers it.

Yes. In the English package the whole website is in English, with an English knowledge layer and English skills. The scripts format numbers, euros and times through the browser in the language of the page.

Anywhere static files are allowed. Astro builds the site into a folder of finished HTML that you upload to your host. Before that your AI sets your own domain in astro.config.mjs and robots.txt, and the website derives every other address from it.

Yes. Pay once, yours forever, for your own projects and client projects. You get the complete source code without a watermark.

No. You tell your AI in the project folder what should change, and it finds the place through CLAUDE.md and the seven skills. If you want to make changes yourself, trips, prices, dates and supplements sit in src/data/site.ts and team, history and packing list in src/data/inhalte.ts.