Blog · a series
Across Rutba
The things that are true on every Rutba site at once: one sign-in for all of them, a reference on every page that tells support exactly what you are looking at, and a page for every app drawn from the app itself.
5 parts · about 21 minutes to read them all
Part 1 · 3 min read
Every Rutba page can tell you which page it is
"The login page is broken" describes several pages on several deployments. So every page now ends with a short reference (which deployment, which page, which build and which visit) that a screenshot is enough to trace, and that never carries your data.
Part 2 · 3 min read
A page for every Rutba app, drawn from the app itself
A product page named its apps in a sentence each, which cannot tell you whether a till handles returns. Forty apps now have a page of their own, listing every screen in them (read from each app’s own menu) with screenshots of it running.
Part 3 · 3 min read
Every page links the family the first time it says the name
Nobody hand-links a marketing site consistently, and a site with no internal links makes readers use a search engine to find its own pages. So the prose is structured content now, and the first mention of a product in any sentence becomes a link.
Part 4 · 6 min read
Every app in the suite now opens at rutba.io
Since 6 October all 46 apps in the Rutba suite run in production, each at its own address under rutba.io, such as pos.rutba.io or books.rutba.io. Your sign-in says whose data you see, so no business needs addresses of its own.
Part 5 · 6 min read
Which apps your organisation can install, and how the launcher finds out
From the next release, Rutba tells each organisation’s instance which apps it may install. The launcher in every app follows that list, and the console’s Modules page says, app by app, whether it is installed and who decided.
