User Story #920
Updated by Islam Mansoori about 1 month ago
**As a Super Admin, I want to create and publish Travel Guides so that informative destination content can be displayed on the website without using package-specific information.** --- # Feature Background The Travel Guide module will reuse the existing **Package Management** backend framework to minimize development effort. The module will only retain content-related fields and remove all booking and package-specific functionality. Published Travel Guides will be available for display on the website. --- # In Scope The backend shall provide APIs to: - Create a new Travel Guide. - Update an existing Travel Guide. - Retrieve a Travel Guide by ID. - Retrieve all published Travel Guides. Reuse Package Management module. - Save a guide as **Draft** or **Published**. ### Supported Fields - include: Guide Title - Destination - URL Slug - Featured Image - Thumbnail Image - Rich Text Content - Category - SEO Title Tags - SEO Description Metadata - Author (System Generated) - Publish Date Status (Draft / Published) --- # Out of Scope (Phase 2) - Scheduled Publishing - Version History - Archive Management - Tag Management - SEO Keyword Management - Canonical URLs - Comments and Ratings - Content Approval Workflow - Multi-language Support - Analytics and View Count --- # Business Rules - Guide Title is mandatory. - Destination is mandatory and must reference an existing Country/City. - URL Slug must be unique and automatically generated from the Guide Title (editable by Admin). - Featured Image is mandatory for published guides. - Rich Text Content is mandatory before publishing. - Category is mandatory. - Author is automatically assigned from the logged-in administrator. - Only guides with **Published** status are exposed through public APIs. --- # Backend Responsibilities - Reuse the existing Package Management service structure. - Exclude all package-specific fields (price, itinerary, inclusions, halal facilities, booking details, etc.). - Validate mandatory fields before saving. - Generate and validate unique URL Slugs. - Store rich text content securely. - Integrate with the existing image upload service. - Maintain audit information (Created By, Created Date, Updated By, Updated Date). --- # Acceptance Criteria - Administrator can create and edit a Travel Guide. - Draft and Published statuses are supported. - Package-specific fields are not available. - URL Slug is unique for every guide. - Rich text content is stored successfully. - Published guides are available for frontend consumption. - All create and update operations are logged with audit information. removed.