Interface: pages with a side menu instead of a single workbench #25

Open
opened 2026-11-17 08:51:49 +00:00 by claude-bot · 0 comments
Member

The interface is one workbench screen plus a settings dialog with tabs. It is awkward to use and every new function piles up on the same screen.

Direction (chosen by the maintainer)

A side menu with the tenant selector at its top, and one page per activity:

  • To review: drop documents, follow the ingestion queue, correct a document before it is published.
  • Library: browse, filter by the declared facets, search, open a document page (preview and metadata).
  • Taxonomy: themes and facets.
  • Extraction, Activity.
  • Tenant: members, resources.
  • Instance (administrators): tenants, accounts, settings, as pages instead of a dialog.

Adding a function means adding a menu entry and a page.

Steps

  1. Facets from the configuration (separate issue): the pages are driven by it.
  2. Application shell: side menu, routing, session and tenant context; administration moved to pages.
  3. To review and Library pages, with the document page.
  4. Taxonomy, Extraction and Activity pages.
  5. Tenant selector made effective with the per-tenant resources.

Each step is its own pull request.

The interface is one workbench screen plus a settings dialog with tabs. It is awkward to use and every new function piles up on the same screen. ## Direction (chosen by the maintainer) A side menu with the tenant selector at its top, and one page per activity: - **To review**: drop documents, follow the ingestion queue, correct a document before it is published. - **Library**: browse, filter by the declared facets, search, open a document page (preview and metadata). - **Taxonomy**: themes and facets. - **Extraction**, **Activity**. - **Tenant**: members, resources. - **Instance** (administrators): tenants, accounts, settings, as pages instead of a dialog. Adding a function means adding a menu entry and a page. ## Steps 1. Facets from the configuration (separate issue): the pages are driven by it. 2. Application shell: side menu, routing, session and tenant context; administration moved to pages. 3. To review and Library pages, with the document page. 4. Taxonomy, Extraction and Activity pages. 5. Tenant selector made effective with the per-tenant resources. Each step is its own pull request.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
modaka/studio#25
No description provided.