I'm fairly new to Airtable but very familiar with data structures from a development perspective. I have a Pro plan and I'm building a community directory on a website. It will have business listings and categories, member data and profiles, a calendar of events and some maps to be displayed as they relate to groups of community members. I'm looking for advice on the best way to structure the bases for this data from an Airtable pricing and access perspective.
I know I can have one base and build multiple tables within that base to support a website. Or I can also build multiple bases and have the data in separate bases. In the future I might want to use segments of the data and share them among other community websites.
Is there a preferred way or optimal way of mapping this data? Or is it interchangeable and both ways work well in the Airtable environment? I believe pricing is irrelevant since there are unlimited bases. Record counts in the bases may be a factor but the counts are likely to be 20,000 or less. I have a Pro plan.
I appreciate feedback from some of you experienced users. Thanks!
