docs/cms-api.md describes the endpoints TYPO3 serves to MyE&P and the chatbot (/api/hotel, /api/product, /api/calendar-hotels, /api/content/*): key, parameters, responses, errors. It is the other side of MyE&P's API consumer guide. docs/calendars.md covers the price calendar, the Belegungskalender and the iCal feed: which product gets which, the MyE&P endpoints behind them, caching, troubleshooting, and the rule that a product's calendar hotel must carry the BusPro code, not a group house's CMS code (which broke three example trips). The README replaces the TYPO3 base distribution boilerplate and links both. The plugin renaming SQL in ep_products' README is obsolete since the migration. The cmsApiKey description names /api/calendar-hotels. Co-Authored-By: Claude Opus 5.5 <[email protected]>
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
# E&P Reisen websites (TYPO3 13)
|
|
|
|
TYPO3 13 LTS for www.ep-reisen.de and its subsites (ski-boarderweek, snowzone, semesterende-skireisen,
|
|
ski-wochenenden, …). Products, hotels, regions and dates live in `packages/ep_products`, templates
|
|
and assets in `packages/ep_theme`. Dates, prices and availability come from **MyE&P** (`EP/myep`),
|
|
which in turn reads bpn-connect.
|
|
|
|
## Local setup
|
|
|
|
DDEV project: `ddev start`, then `ddev composer install` and `ddev npm install && ddev npm run build`.
|
|
Rebuild the assets after template changes: Tailwind purges classes it does not find in the
|
|
templates.
|
|
|
|
## Documentation
|
|
|
|
- [docs/cms-api.md](docs/cms-api.md): the API TYPO3 serves to MyE&P and the chatbot
|
|
(`/api/hotel`, `/api/product`, `/api/calendar-hotels`, `/api/content/*`).
|
|
- [docs/calendars.md](docs/calendars.md): price calendar, Belegungskalender and iCal feed: where
|
|
the data comes from, caching, and what to check when a calendar does not load.
|
|
|
|
## Deployment
|
|
|
|
`deploy.php` (Deployer). A deploy runs `extension:setup`, resets OPcache and flushes all caches.
|
|
|
|
## License
|
|
|
|
GPL-2.0 or later
|