I'm planning a public-facing directory website with several sections: recipes, restaurants, food suppliers, and drinks suppliers. Recipes may work somewhat like blog posts, while the restaurants and suppliers would each have their own profile pages with bios and other details.
I have no coding experience and almost no budget, so I'm looking for a genuinely no-code or WYSIWYG solution. I tried Webflow because its CMS seemed promising, but the interface felt too complicated and the learning curve seemed steep.
I've built a basic prototype in Airtable, and the data structure works well, including linked records. Ideally, recipes could be associated with restaurants or drinks brands, such as for food pairings or wine recommendations. I'm wondering whether Airtable can realistically be used as the backend while another no-code tool provides the public website, with search, filters, and individual profile pages.
I'm not interested in building the site with AI website generators. What tools or combinations would be practical for this kind of project, especially given the limited budget and my lack of coding experience?
3 Answers
Because the project could mean several different things, it’s worth testing one complete workflow before committing to a platform. For example, build one directory, add filtering by region, create a profile page, and edit a recipe from the backend. That will show you how difficult the setup is and what the ongoing costs look like. Airtable can work well as a prototype or content-management layer, but the public-facing tool should be chosen separately.
Softr is probably the closest match. It connects to Airtable and can turn the records into a public directory with search, filters, and detail pages for restaurants and suppliers, without requiring code. Glide and Stacker are also worth comparing, since they handle record-based profile pages and linked data somewhat differently. Your Airtable structure gives you a useful head start.
For linked content, Airtable relationships should be usable if the front-end tool supports them. If that becomes awkward, manually associating recipes with restaurants or drinks brands is still manageable when the relationships don’t change often.
Framer can also be considered for the front end, but it may not be the simplest fit if you need a database-driven directory with lots of records. A dedicated Airtable-to-directory tool is likely to be easier for profile pages, filtering, and content management, especially if you want to avoid relying on generated code.
Linked records would be ideal, particularly for recipes connected to restaurants or drinks brands, but I could maintain those associations manually if the tools don’t handle them cleanly. They should not need frequent updates.