See BookStack in featkpr, privately.
A half-hour call with Tim, who builds featkpr: BookStack’s map, its flows and its runs, live, and your questions first.
- You asktodayone email is enough; a product of your own is optional
- A live walkthrough of BookStacktodayTim writes back by hand with times for a call
- A public demoan idea, not decidedopen question: whether a public demo comes before or after the private read-only one
sent
Request received #
Tim will write to , usually within two working days, with times for a 30-minute call.
A second email asks you to confirm the news. Nothing arrives until you press it.
What the call shows #
Screens of featkpr's app on this page run on sample data, so the numbers inside them are examples, not BookStack's. Screens of BookStack are the crawl's own captures. On the call they show BookStack as it stands.
What does it do?
Its 298 features by module, each traced to the code it was named from.
Features How do people use it?
A drafted flow, screen by screen: what a person types and presses, and what a test would check.
Flows · Create a book, step 3 of 4 Who may do what?
One feature’s outcomes with and without each permission; each becomes a test, and each test is sent again as the wrong user.
a feature's outcomes