Repository navigation
1.0.13
What changed since 1.0.12
Added
- Settings is built for a base with plugins. The base comes first (General, Navigation, Buttons, Command order, Styles as one entry), then the plugins by family, each row with one state (Ready, Not active, Not installed, Needs settings) and one next action, under one filter with chips for "Needs attention" and "Updates" (#231, #233, #265).
- A page per plugin,
/settings/plugin/<name>: its state, the steps that are left as one guided list (with "activate with its needs"), what it needs, its settings form with the fields that still hold a placeholder marked, what it ships, and removal (#235, #269). - Settings → Plugins is the catalogue, by family, where a plugin is added (#237, #267).
- Settings says when a plugin has a newer version on npm and offers the update (#243).
- A plugin can say where Settings lists it and what its one line is: the manifest's
familyandsummary(#231).
Changed
- A command never opens a terminal at the bottom of the page: commands run in screen sessions only. The page shows a short notice with "Open in Screens"; the session is first on the Screens page, and its log stays readable after it ends. When no screen session can be started, the command is not run and the notice says what is missing, how to fix it, and gives the command line to copy (#249, #253).
- On a dark page the logo is the white mark (#277).
Fixed
- Keyboard focus can be seen on buttons and fields in both styles, is not hidden under the top bar, and fields have a visible edge (#263). The settings modal takes focus when it opens and gives it back when it closes (#271). Error messages stay until closed (#273).
- "Needs settings" also sees a quoted placeholder (#247); a plugin's page follows a save and a step without a reload (#251, #257); a focused field keeps the dark surface in the dark style (#255).
Reviewed by a design critic and an accessibility tester before release; axe finds no violation on the six Settings pages in both styles at desktop and phone width. Not done: a screen reader run, and the settings modal's phone layout.
Running the dashboard with node on a machine (not in its container) needs screen installed there. Plugin types: @webship.co/workspace-plugin-api 1.0.11.
Install or update: npm install -g @webship.co/workspace@1.0.13, then webship-workspace update ~/workspace.