I want to clarify one important point about the Advisory section.
Unlike Briefing Items, which are a collection of multiple entries, the Advisory is intended to be a single active item at any given time.
However, I’d still like it to have its own management page, just like the other content types.
Proposed Workflow
The Advisory management page should display a single Advisory item as a management card (or table row) with standard CMS actions such as:
* Publish
* Unpublish
* Edit
* Delete
This gives users full control over whether the Advisory is visible on the public website.
For example:
* If the Advisory is Published, the Active Advisory section appears on the public Sudan Today page.
* If the user clicks Unpublish, the entire Active Advisory section should disappear immediately from the public page.
The behavior should be similar to what already happens with the Featured section.
I tested this by publishing a Featured article and then unpublishing it.
When I unpublished it, the entire Featured section disappeared automatically, leaving only the Latest Developments section.
That’s exactly the behavior I want for the Advisory as well.
Content Management
This also gives the editors complete control.
For example:
* When an advisory is no longer relevant, they can simply Unpublish it so it disappears from the website.
* If the situation changes, they can edit the advisory and update its status (for example, changing it to Resolved).
* If an entirely new advisory needs to replace the old one, they can remove the previous advisory and create a new one.
The goal is to keep the workflow simple, intuitive, and easy for embassy staff to understand while giving them complete control over what appears on the public website.