5jabs lays the groundwork for community workflows and real inbound leads
The sterlex fork is preparing two public-facing flows, but neither is live in this snapshot.
5jabs has added the data foundations for a moderated community workflow library and a proper contact channel for the product site.
- A workflow submission queue, built for contributors to propose workflows for publication and for the team to approve or reject them. It is not yet connected to a user-facing submission flow.
- A contact-message store, ready to capture names, email addresses and enquiries from the landing page. That form is also not yet wired up here.
Both queues are restricted to trusted backend access, with duplicate pending workflow submissions blocked. This is early plumbing, but it points to a product that expects outside contributions and wants a more credible route for prospective users to get in touch.
So what Legal-tech teams watching sterlex should track the next few changes: the useful part arrives when these contributor and contact flows reach the product.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?