I know you asked a more narrow question about a good template to start out with. And then the nitty gritty details of commenting and approval can be handled by a system that is designed for that purpose. Or do you want to use Softr as a portal onto a separate document management/workflow system? Softr can be a great “front end” to one or more separate systems and bring them all together by offering one place that users start out. And it will mean a fair amount of integration with a tool like Zapier or Make to handle some of the workflow functions and perhaps the integration of the documents themselves, if they are not stored as attachments in Airtable. So with all that in mind, you’re going to need to make a big decision up front.ĭo you want to build the application natively in Softr, and accept the limitations of tabular data? This will mean, for example, that comments can’t be in the document, they will have to be next to it. This could be in Softr custom code but is more likely to live in either Airtable or Zapier or Make. Similarly, to implement document approval (i.e., workflows), you’ll need to write code somewhere that handles the approval/reject logic. Comments in a Google Doc or a Word file are what I’m picturing here. For users to have a great commenting experience, they need to be able to comment directly in a document, which requires tight integration with a document editor. However, a document management application like you’re describing doesn’t usually fit into rows and columns in an Airtable base, at least not directly. To the extent that your application’s data looks like rows and columns and linked records in an Airtable base, Softr will really shine. At the core of Softr is the ability to let users see and interact with a website of data from tables from an Airtable* base.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |