This guide walks you through the decisions you’ll make as you plan a multi-site JUNO platform.
...
Access type: Public preview, Private, and Content-specific
| Anchor | ||||
|---|---|---|---|---|
|
Public preview: 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: 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 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.”
...