This guide walks you through the decisions you’ll make as you plan a multi-site JUNO platform.
...
Site type: 365 or Single-use Site-switching links Access type: Public preview, Private, and Content-specific URL customization Welcome page design User authentication Site content and configuration
...
Once someone clicks a link, they are taken to the other site if they have access. Access is what you’ll learn about next!
Access type: Public preview, Private, and Content-specific
| Anchor | ||||
|---|---|---|---|---|
|
Public accesspreview: Make your site public preview to show potential users what they could get once they register, subscribe, or upgrade. They can navigate to other pages, but once they try to open or interact with content, they will be prompted to log in on the welcome page. Watch a demo in this video:
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
An example public preview site. You can preview pages but must log in once you try to open content.
Private access: Or keep your site privateso that users only see the welcome page before logging in.
...
An example private site. You only see the welcome page before logging in.
Content-specific restrictions: In addition to the above site-wide access options, you can restrict individual pieces of content with an access level tag. It doesn’t matter if the site is allows public preview or is private. Even if someone is logged in, they can only open the content if they have the correct access level. For example, within an event site, you might create multiple ticket levels. If a user has access to a site, but not that content, they are alerted and can be prompted to upgrade.
For a multi-site platform, public preview and private sites can be combined in creative ways. In the following examples, imagine that you have a platform with two sites: a 365 site and a single-use site called “Event.”
...
| 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 | ||
|---|---|---|
| ||
A user does not need to log in to preview the 365 site. But if they try to interact with content, they will be prompted to log in. They will also be prompted to log in when they try to switch sites because the Event site is private. This scenario is most common when the 365 site will be open for the general public to join open webinars or view basic content.  |
| Expand | ||
|---|---|---|
| ||
All sites are 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.  |
...