Consider this case:
We manage a very very long hiking trail across many states. It's divided in 20 sections. To get the digital maps, section coordinator contacts, section emergency alerts, section online updates, right to access private land, people have to signup and select as many sections as they want during the signup process. For each section there will be specific email sent and online content available (1 page per section to start with, maybe a blog + forum + chat per section in the future). Some hikers might decide they need them all. Some only need a couple of the sections.
Hikers are then subscribed to the selected sections for 1 year, renewable. There is a specific cost associated per section. They pay for the total + a national annual membership fee.
Can we use CiviCRM for this purpose? It's mostly online digital subscription which is close to the concept of membership, IMHO. But I'm not clear on the data mapping and which entities to rely on.
Is each of the 20 section a different membership type? Or a different price in a price set? or a different priceset?
Should we use CiviRule to add contact to groups based on the membership types they selected (or priceset element?) Creating 20 membership types seems overkill, isn't it? Do I have to then create 20 organisations in CiviCRM to map the 20 sections?
I've used CiviCRM in the past for traditional NGO, so I'm keen to also reuse all the other features too. I have development background and will hire Drupal devs to help out.