Actions
User Story #922
openEPIC #670: Package Catalogue Management - 2 days front end and 2 days backend
Feature #915: Travel Guide Management
backend Travel Guide Publishing
Start date:
Due date:
% Done:
0%
Estimated time:
Description
As a Super Admin, I want to publish or save Travel Guides as drafts so that only approved travel content is visible on the website while unpublished content remains editable.
Feature Background¶
The Travel Guide Publishing module controls the visibility of Travel Guide content. It enables administrators to save guides as drafts during content preparation and publish them when they are ready for public viewing. Only published guides will be available through the public APIs consumed by the frontend.
In Scope¶
The backend shall provide functionality to:
- Save a Travel Guide as Draft.
- Publish a Travel Guide.
- Change the status between Draft and Published.
- Retrieve only Published guides for the public website.
- Retrieve both Draft and Published guides for the Admin Portal.
Out of Scope (Phase 2)¶
- Archived Status
- Scheduled Publishing
- Automatic Publishing based on Publish Date
- Publishing Approval Workflow
- Version History
- Rollback to Previous Versions
- Publish Notifications
- Publishing Audit Timeline
Business Rules¶
- A newly created Travel Guide shall default to Draft status.
- A Travel Guide can only be Published after all mandatory fields are completed.
- Only Published Travel Guides shall be returned by public APIs.
- Draft Travel Guides shall be visible only to authenticated administrators.
- Administrators may change a Published guide back to Draft if required.
Backend Responsibilities¶
- Develop APIs to publish and unpublish Travel Guides.
- Validate mandatory content before publishing.
- Store and update the publication status.
- Filter public API responses to return only Published guides.
- Record audit information for status changes (Created By, Updated By, Created Date, Updated Date).
Acceptance Criteria¶
- Administrators can save a Travel Guide as Draft.
- Administrators can publish a valid Travel Guide.
- Published guides are accessible through public APIs.
- Draft guides are restricted to the Admin Portal.
- Status changes are successfully persisted and audited.
- Publishing is blocked if mandatory content is incomplete.
Actions