This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Papa-Kind-Treff – Project Context
|
||||
|
||||
Updated: 2026-08-05
|
||||
Updated: 2026-08-07
|
||||
|
||||
## Summary
|
||||
Papa-Kind-Treff is a PHP-based platform for fathers. Core areas are local events, appointments, and meetups, a community forum, member profiles with optional child information, and a moderation/admin area.
|
||||
@@ -23,6 +23,7 @@ Papa-Kind-Treff is a PHP-based platform for fathers. Core areas are local events
|
||||
- Profile address can be completed via address search or browser-based location import.
|
||||
- The `Events` area is limited again to real own events and event participations.
|
||||
- The `Events` area now also provides a manual ICS export and a personal subscribable calendar feed for all own events and event participations.
|
||||
- The `Events` area is now separated in the UI into `My Events` and `Synchronization` so that event management and calendar tasks stay clearly separated.
|
||||
- Places and event-like outing targets were moved for now into a separate member-area section `Outings`.
|
||||
- The `Events` input flow should stay as simple as possible and therefore only shows fields relevant for real scheduled events.
|
||||
- Categories in the member area are handled via a search input with existing suggestions and automatic creation when needed.
|
||||
@@ -39,6 +40,10 @@ Papa-Kind-Treff is a PHP-based platform for fathers. Core areas are local events
|
||||
- Goal: later distinguish between own event, partner offer, general place, and editorial event entry
|
||||
- Google is not integrated productively yet; the system is only being prepared for it via settings and data fields
|
||||
|
||||
## Deferred To-dos
|
||||
- Large calendar-provider integrations should be added later in addition to the ICS feed, starting primarily with Google and Microsoft/Outlook.
|
||||
- The target model is no reverse sync, but a user-side OAuth login through Papa-Kind-Treff followed by a direct calendar connection or event synchronization at the respective provider.
|
||||
|
||||
## Maintenance Note
|
||||
- Whenever one of these files changes, the matching files in `Internal/de/` and `Internal/en/` must be kept aligned.
|
||||
- The root `README.md` acts as the startup document for new chats and should be reviewed alongside major context changes.
|
||||
|
||||
Reference in New Issue
Block a user