Portal modules
The building blocks of a Portal: what each module does, grouped by purpose, and the sixteen journey templates built from them.
A module is one block of a Portal: a music player, a gallery, a ticket, a signup card. This page sets out every module, grouped by purpose, and the sixteen journey templates built from them. There are 22 modules: 21 available today and Collection coming soon, with more on the way.
How modules work
A Portal is a feed of modules, stacked in the order the client chooses, under one theme. Modules are added, reordered and changed without code, and without reprinting a tag. Where a module comes in versions, such as landscape or portrait video, those are variations of one module.
Gating is set per module, so any module can be open, teased or members only.
Categories
Modules are grouped by purpose into five categories, the same five the Portal Design Studio uses.
| Category | What it is for | Modules |
|---|---|---|
| Content | Words, links and people | Content, Profile, Links and socials, Notifications, File download |
| Media | Sound, video and images | Gallery, Music player, Video |
| Commerce | Selling, claiming, events and unlocking | Ticketing, Event response, Product and DPP, Physical ordering, Collection, Page Lock |
| Membership | Joining and member benefits | Signup card, Membership tiers, Credits, Studio booking |
| Community | Fans with each other and with the artist | Share card, Raffle and competition, Push notifications, Fan Voice |
Standard and Advanced
Every module is also one of two classes:
- Standard publishes words, pictures and links: Content, Profile, Links and socials, Notifications, File download, Gallery, Collection, Membership tiers and Share card.
- Advanced talks to Core: it sells, checks, counts and remembers. Music player, Video, Ticketing, Event response, Product and DPP, Physical ordering, Page Lock, Signup card, Credits, Studio booking, Raffle and competition, Push notifications and Fan Voice.
A Standard module is ready as soon as the copy and media are in. An Advanced module needs something behind it: a ticket inventory, a product record, a member's balance or a consent.
All modules
Open a module to see what it does, what a fan sees, its options and what it needs, then real client Portals that use it. Most link to their live page in the Portal Design Studio, which is a work in progress.
Two Core capabilities sit alongside the modules and are available: coming soon doors, in Core Connect, and the refusals register, in Core Commerce.
Journey templates
A journey template is a ready made Portal: a set of modules arranged for one job. There are 16. Fourteen are our ready to deploy experiences, and two more, Collectible claim and Raffle entry, complete the set. Each takes 1 or 2 weeks to build.
| Template | Leading Core module | Build time |
|---|---|---|
| Membership Profile | Core Identity | 2 weeks |
| Event Touchpoint | Core Access | 1 week |
| Tap to Enter Tickets | Core Access | 2 weeks |
| Music Player | Core Media | 1 week |
| Set Times | Core Media | 1 week |
| Post event Content | Core Media | 2 weeks |
| Scavenger Hunt | Core Gamify | 1 week |
| Raffle entry | Core Gamify | 1 week |
| Waitlist Form | Core Connect | 1 week |
| External Links | Core Connect | 1 week |
| Brand Partner Experiences | Core Connect | 2 weeks |
| VIP Segmentation | Core Intel | 2 weeks |
| Early Access Ticket Link | Core Commerce | 2 weeks |
| In App Ticket Purchase | Core Commerce | 2 weeks |
| Collectible claim | Core Collect | 2 weeks |
| Product Authentication | Core Product | 1 week |
To see modules and templates in client work, see Solutions. Each solution there shows a journey you could run, screen by screen, with the modules on each screen.