This guide walks you through the decisions you’ll to make as you plan a multi-site JUNO platform.
...
Your JUNO experience can go beyond a single, static website. Instead, think of your JUNO Single Destination Platform as a home base for your events, users, content, and data. Everything is stored in one content management system. From there, we design and launch multiple sites to create many different user experiences.
You might start your JUNO journey with a single live event before expanding to a multi-site platform. Or you might start with a single 365 site to engage your community year-round, then add more sites that host temporary events or communities.
...
365 sites are for year-round content and engagement. Think of your 365 site as the hub for your Single Destination Platform. Your community visits the site whenever they’d they like, whether to find information, earn certifications, or connect with others. You can host gatherings that draw people to the site at scheduled times.
...
Once someone clicks a link, they are taken to the other site if they have access.Access is what you’ll learn about next!
...
| Expand | ||
|---|---|---|
| ||
A user must log in to the 365 site to see anything there. They may be given a direct link to preview the Event site without logging in. But if they try to interact with content on the Event site, they will be prompted to log in. This scenario is most common when the 365 site is a member-only benefit, while ticketed events are advertised to the general public (non-members). In this case, we often hide the site-switching link from non-members.  |
...
| Expand | ||
|---|---|---|
| ||
All sites are allow public preview. A user does not need to log in to preview sites. But if they try to interact with content, they will be prompted to log in.  |
...
...
Or control what people see before the event starts, while you’re still building the site. For example, give exhibitors a curated experience while they set up their suites. Or make a stripped-down experience for all attendees before the event.
We do this configure these experiences by creating a duplicate version of a site with some configuration changes and a unique URL. Then we give users a direct link to the site. Or, if it’s just a matter of restricting specific pages, we use curtains to keep out users who shouldn’t have access.