docs(website): add Docusaurus documentation site

Scaffold a Docusaurus site under website/ with custom landing page, branding, and documentation across getting-started, guides, concepts, reference, and community sections.

Author: josedab

website/.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

website/README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+## Installation
+
+```bash
+yarn
+```
+
+## Local Development
+
+```bash
+yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+## Build
+
+```bash
+yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+## Deployment
+
+Using SSH:
+
+```bash
+USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```bash
+GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

website/docs/community/changelog.md

@@ -0,0 +1,58 @@
+---
+title: Changelog
+sidebar_position: 5
+description: Release history and upgrade notes.
+---
+
+# Changelog
+
+All notable changes to VisitRomagna are documented here. Versions follow [Semantic Versioning](https://semver.org/) — `MAJOR.MINOR.PATCH`.
+
+While VisitRomagna is pre-1.0 (`0.x`), minor versions may include breaking changes; check the upgrade notes for each release.
+
+## Unreleased
+
+### Added
+
+- Public Docusaurus documentation site under `website/`.
+- Mermaid architecture and lifecycle diagrams.
+- Comparison page versus Airbnb, Booking.com, GetYourGuide, and Agriturismo.it.
+
+### Changed
+
+- Improved `BookingService.confirm` to be idempotent on Stripe webhook replay.
+
+### Fixed
+
+- N/A.
+
+## 0.1.0 — Initial public release
+
+The first publicly visible commit. Includes:
+
+- **Experience catalog** with six categories and rich filtering.
+- **Booking engine** with availability calendars and a full status lifecycle (`pending_payment` → `confirmed` → `completed` → `refunded` / `cancelled` / `disputed`).
+- **Stripe Connect** marketplace payments with simulated fallback.
+- **Italian VAT (IVA)** computation per category and **FatturaPA XML** invoicing.
+- **Host dashboard** for listings, calendar, pricing rules, bookings, payouts, messages, and reviews.
+- **Cycling module** with GPX routes, Strava OAuth, and Komoot deep-links.
+- **AI itinerary builder** with map-based browsing and multi-stop checkout.
+- **Real-time messaging** via Server-Sent Events.
+- **CRM & loyalty** — segments, tiers (Bronze/Silver/Gold), referrals, gift cards.
+- **B2B portal** for travel agents and group bookings.
+- **Admin console** with moderation, disputes, feature flags, and A/B experiments.
+- **Five locales** — IT, EN, DE, FR, ES with hreflang SEO.
+- **Vitest** suite with coverage thresholds enforced in CI.
+
+## Upgrade notes
+
+### Coming from 0.0.x prototypes
+
+- The data model now uses Prisma 7 with `cuid()` primary keys. If you had hand-rolled fixtures, regenerate them via `npm run db:seed`.
+- The `payments.ts` module replaces the older `pricing.ts`. Import sites changed; run `npm run lint` to surface broken imports.
+
+### Conventions going forward
+
+- Conventional Commits drive this changelog (see [Contributing](./contributing)).
+- Each release tag triggers a CI build and a deployment to the demo environment.
+- We squash-merge PRs; squashed commit message becomes the changelog entry.

website/docs/community/code-of-conduct.md

@@ -0,0 +1,48 @@
+---
+title: Code of Conduct
+sidebar_position: 4
+description: How we treat each other in this community.
+---
+
+# Code of Conduct
+
+## Our pledge
+
+We — contributors and maintainers — pledge to make participation in VisitRomagna a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Using welcoming and inclusive language.
+- Being respectful of differing viewpoints and experiences.
+- Gracefully accepting constructive criticism.
+- Focusing on what is best for the community.
+- Showing empathy towards other community members.
+
+Examples of unacceptable behavior:
+
+- Trolling, insulting/derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing others' private information, such as a physical or electronic address, without explicit permission.
+- Conduct which could reasonably be considered inappropriate in a professional setting.
+
+## Our responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and also applies when an individual is representing the project or its community in public spaces. Representation includes using an official project email, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening a private issue or contacting the maintainers directly via the contact channels listed in the repository. All complaints will be reviewed and investigated promptly and fairly.
+
+Maintainers are obligated to respect the privacy and security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.

website/docs/community/contributing.md

@@ -0,0 +1,113 @@
+---
+title: Contributing
+sidebar_position: 3
+description: How to file issues, propose changes, and ship pull requests.
+---
+
+# Contributing
+
+VisitRomagna is built in the open. Contributions of every size are welcome — typo fixes, new test cases, whole features.
+
+## Before you start
+
+1. **Open an issue first** for anything bigger than a typo. Describe the problem, the proposed fix, and any open questions. This avoids duplicated work and dead-end PRs.
+2. **Search existing issues** — your idea may already be in motion.
+3. **Read the [Code of Conduct](./code-of-conduct)**.
+
+## Local setup
+
+Follow the [Quickstart](../getting-started/quickstart) — Node 20+, `npm install`, `cp .env.example .env`, `npx prisma generate`, `npm run dev`.
+
+Run the full CI check before pushing:
+
+```bash
+make ci
+```
+
+That's lint + typecheck + tests + production build.
+
+## Branching
+
+We use trunk-based development against `main`.
+
+```
+feature/<short-kebab-name>     # new functionality
+fix/<short-kebab-name>         # bug fixes
+docs/<short-kebab-name>        # docs only
+```
+
+Examples: `feature/group-booking-discount`, `fix/sse-reconnect-loop`, `docs/payments-iva-rates`.
+
+## Commits
+
+We follow Conventional Commits:
+
+```
+feat: add group booking discount engine
+fix(payments): correct IVA rounding on €0 bookings
+docs: clarify Stripe webhook setup
+test(booking): cover same-day cancellation policy
+chore(deps): bump prisma to 7.8.1
+```
+
+Why this matters: the changelog and release notes are generated from commit messages.
+
+## Pull requests
+
+A great PR is:
+
+- **Small.** < 400 lines diff is the target. If yours is bigger, consider splitting.
+- **Test-covered.** New behavior ⇒ new tests. Bug fixes ⇒ a regression test.
+- **Self-explaining.** A reviewer should understand *why* from the description, not just *what*.
+- **Green on CI.** Don't ask for review with red checks.
+
+PR template (auto-applied by GitHub):
+
+```markdown
+## What
+One sentence on what changes.
+
+## Why
+The user-facing or technical reason.
+
+## How
+Notable design choices.
+
+## Test plan
+- [ ] Unit tests added
+- [ ] Manual smoke test:
+- [ ] CI green
+```
+
+## Coding style
+
+- **TypeScript strict.** No `any`. If you must, justify in a comment.
+- **No dead code.** Delete it; git remembers.
+- **Prefer pure functions** in `src/lib/`. Side effects belong in domain services or subscribers.
+- **Error handling is structured.** Throw typed errors (`InvalidStateError`, `NotFoundError`) — the API serializer maps them to status codes.
+- **Comments explain *why*.** The code already shows *what*.
+
+## Reviewing
+
+If you're reviewing someone else's PR:
+
+- **Run it locally.** "LGTM" without running the change isn't a review.
+- **Test the edge cases.** Empty inputs, max sizes, concurrent requests.
+- **Be kind and specific.** "This could be clearer" → "Consider extracting the IVA logic into a helper named `calculateIva(category, amount)` so the test names read more naturally."
+
+## Release process
+
+Releases ship from `main` whenever we have a meaningful batch of changes. The release commit:
+
+1. Bumps `package.json` version.
+2. Regenerates the [Changelog](./changelog).
+3. Tags `v0.x.y` and pushes.
+4. CI builds and deploys to the demo environment.
+
+## Hall of fame
+
+Significant contributors get a permanent line in the README and a `CREDITS.md` mention. Thank you for shipping with us.
+
+## Questions
+
+Open a [Discussion](https://github.com/ForliLabs/visit-romagna/discussions). For private inquiries, the maintainers are reachable through the repository's contact info.