I'm planning a public-facing directory website with several content sections: recipes, restaurants, food suppliers, and drinks suppliers. Recipes may also work like blog posts, while each restaurant and supplier would have its own profile page with descriptive information.
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 suited to this kind of structured content, but I found the interface complicated and the learning curve too steep.
I've built a basic prototype in Airtable, and the data structure seems to work well. However, Airtable itself doesn't provide the public-facing website experience I need. Could I realistically use Airtable as the database or CMS and connect a separate no-code website builder on top of it? I'm particularly interested in options that support search, filters, individual profile pages, and linked records—for example, connecting a recipe with a restaurant or drinks brand. Manual linking would also be acceptable if automatic relationships become too complicated.
I'm not interested in using AI website builders or having an AI generate the site. I'd prefer visual tools that I can understand and maintain myself. What platforms or combinations would be practical for this type of project and budget?
3 Answers
Since your Airtable model is already working, I’d keep it as the backend or at least as the prototype for your content structure, then choose a separate no-code frontend. Softr is probably the closest fit: it connects to Airtable and supports directory templates, search, filters, and detail pages for individual records. Glide and Stacker are also worth comparing, although they handle layouts and record relationships somewhat differently.
Before committing, build one complete example from start to finish—such as a restaurant listing with filters, a profile page, and an Airtable edit. That will reveal the real setup effort and ongoing cost much better than comparing feature lists.
The important choice is less about finding a perfect stack and more about testing the actual content workflow. A directory with several content types can look simple but still become awkward when you need relationships, filtering by location or category, profile pages, and easy editing.
Try creating a small sample of each type in the platform you’re considering. Check whether an Airtable record automatically gets a clean public page, whether linked fields display properly, and whether you can update content without rebuilding pages. Also check the limits and pricing for Airtable requests, records, users, and published pages before investing too much time.
A visual builder such as Framer could handle the presentation, but I’d be cautious about relying on generated code or an AI assistant when you don’t have the technical background to verify its work. A conventional no-code tool with visible collections, fields, and page templates may take longer initially but should be easier for you to understand and maintain.
For this project, I’d prioritize a platform that clearly exposes its CMS relationships and filtering controls rather than one that can produce an attractive homepage quickly.
That’s my concern with AI-assisted building too. I wouldn’t necessarily notice if it introduced a technical problem, and sometimes it seems faster to use understandable visual controls than to keep correcting an AI-generated result.
Thanks, I’ll compare those options. Ideally, I’d like to preserve Airtable’s linked records so recipes can be associated with restaurants and drinks brands, such as for pairing suggestions. If linking is difficult on the frontend, I could also manage those relationships manually since the content probably won’t change very often.