Time Slots
This view lists all saved time-based schedules. These are the slots that pipelines attach to in order to control when posts are published.
The original Fedica interface calls this section “Hours,” but that term doesn't really describe what it does. It's not a clock. It's not a timer. So here it’s renamed to something clearer: Time Slots.
Cleaned-up UI
Fedica’s layout includes a bloated timezone selector, excessive guidance text, and a floating input field paired with a Save button.
All of that was removed:
- No embedded video player
- No dropdown containing hundreds of GMT options
- No input field demanding attention before anything else
Instead, the screen shows saved time slots — and offers a way to add new ones.

Adding a new slot
Fedica uses a single “Create New” button that opens on hover. Here, two separate buttons are shown instead:
- Add Time Period
- Add Exact Time
Both are valid scheduling types, but they work differently — so it’s better to make the distinction up front.
What each row displays
Each slot in the list includes the following:
- Name – Assigned by the user
- Timezone – Defined when the slot is created
- Type – Either "Time Period" or "Exact Time"
- Days – Days of the week when posts are scheduled (e.g. Mon, Wed, Fri)
- Posts – Approximate number of posts per day (for Exact Time: number of defined times)
- Actions – Edit or delete, aligned to the right

About that timezone selector
The original version includes a timezone dropdown — possibly with hundreds of entries. But:
- It didn’t filter the list
- It didn’t change what was shown
- It didn’t help
So it's gone. Each slot stores its own timezone. No need for global overrides.
Special case: the default slot
There’s always at least one item in the list. If only one time slot remains, it can’t be deleted — only edited.
This prevents users from removing the last available schedule, which is often needed as a fallback when no specific slot is selected elsewhere.
No visual highlight is added (yet), but the delete option for this item is disabled with a short explanation.
That’s enough to keep the interface predictable and avoid accidental confusion.