[Feature Request] Implement to adjust theme to either "Single Group" or "Multi Group" view

[chrisreddington]

The theme originally started as a theme for a Single Group, but has quickly pivoted to be flexible enough for a multi-group scenario, i.e. a platform for groups in a community.

Moving forward, the theme should offer flexibility for both scenarios. Firstly, consider whether this is just a documentation issue, or whether configuration changes need to be made.

For example -

• Multi-site is how the usage scenarios and theme are currently configured. If we adjust the file structure of the repo as follows, then this may help -
• Create a top level folder in the repo called sites.

• In that top level folder, create a subfolder for "emptysites" and "examplesites"

  • emptysites - This folder would contain a couple of additional folders.. SingleGroup and Multigroup. As part of the setup process, a user creating a new site could just copy one of those folders. The intent behind that is that the single group / multi-group views would have slightly different _index.md files, and may have a pre-created group in the single group structure. The difference in those files, is which files contain frontmatter on menus (i.e. instead of groups/_index.md) having the menu items, it's just groups/group-name/_index.md

    • [ ] Need to evaluate the impact of SEO in that scenario.

  • exampleSites would contain two folders - SingleGroup and MultiGroup, similar to the current scenario. However, there'd be an example of each as a demo site.

Alternatively, if the above wouldn't work (e.g. for SEO reasons), then this may need to be driven through a site configuration parameter, such as site_mode, which could be set to SingleGroup or MultiGroup, and adjust views as necessary.

These are some top of mind thoughts, but would love additional comments/thoughts on these approaches.

[chrisreddington]

I think there's a few scenarios in this one -

• Single Group (i.e technical user group scenario)
• Platform Approach (i.e. current example Site view)
• OSS Conference view (think like a kubecon type event. Very similar to platform approach. If not, identical, as groups could be used in a different way (is communities within the broader ecosystem). May just need some guidance on adding additional information to the site.)
• Single Event/Conference view (i.e AWS Reinvent 2020. As it's a single event rather than ecosystem, wouldn't really need groups. Also wouldn't need multiple events. Would still likely have a speakers view, but have the main menu link to one event page, and would need additional information on the site, eg about etc)

The devil will be in the detail on handling the "single event" or "single group" scenario for scenario 1 or 4 respectively, which will determine either config-driven or underlying template driven approach I believe.

[chrisreddington]

As per #48, menu configuration has been pulled out of frontmatter into the config. There are now two main menu sections, one called mainsingle, one called mainmulti. Will need to have a similar scenario for the footers.

There is also a Site Config Parameter which determines whether the layout should be in single or multi mode, and pulls the appropriate nav accordingly. This will be used for other functionality (e.g. whether to display the groups section on the homepage).

This should also be applied to the footer nav as well.