# data[].attributes.headline
Enable hyperlink for Agenda and Speaker descriptions

# data[].attributes.subject
Enable hyperlink for Agenda and Speaker descriptions

# data[].attributes.body
On Gevme Virtual, there is a function that allows for clearing of cache on page and project level. At times, if you notice that changes are made but not reflected on the live page, clearing cache might be the solution you need :)

Understand more about what is cache and why it is a good practice to clear cache

# data[].attributes.headline
Always save your documents in the Shared PS drive

# data[].attributes.subject
Always save your documents in the Shared PS drive

# data[].attributes.headline
Mux is now the default player under Channels

# data[].attributes.subject
Mux is now the default player under Channels

# data[].attributes.body
If you haven't notice, the creation of channels is now a bit different. The default player is now Mux instead of AWS IVS

# data[].attributes.headline
Multiple Language Journey (Registration to Virtual) for Same Event

# data[].attributes.subject
Multiple Language Journey (Registration to Virtual) for Same Event

# data[].attributes.body
To customize a language journey for the same event in different languages - Create 4 Reg Events, then Link all 4 to the Virtual Platform. Then have a unique URL for the each page (-en, -cn, -kr, -jp) and each language page is linked to that Registration Language Event. So for the user, the whole journey is is their specific language. And for us we use 1 platform instead of 4.

# data[].attributes.body
Ability to link attendee profile to speakers so that if attendees wish to message a speaker, they do not need to search for the speaker's name under People Directory

# data[].attributes.body
One of the common issue for Paid Events on Gevme Reg is the inability to manual import data. The trick is to clone the Paid Event, remove the payment related configurations (e.g. ticket price, promo codes) and use it for manual import.

# data[].attributes.body
Before creating sponsor packages, always make sure you update the settings. The settings allow you to determine the Page Title and URL Slug for individual sponsor live pages are created - this way, you do not have to manually update them :)

# data[].attributes.body
Having a search button under Agenda module to find sessions easily (there is a search button for Speakers lol)

# data[].attributes.body
Got many live pages? Use labels to organise them in different categories so that you can differentiate them easily.

# data[].attributes.headline
Always check with the client if they are planning for a livestream backup

# data[].attributes.subject
Always check with the client if they are planning for a livestream backup

# data[].attributes.body
While a live stream backup might mean additional costs (due to possible add on to AV setup), having a backup will be a good contingency plan.

The backup can be on another livepage (as per screenshot) but using another player option (e.g. Zoom).

# data[].attributes.body
If you have a dropdown menu but you want to make the main item non-clickable, input a symbol, e.g. # instead of having the livepage URL

# data[].attributes.headline
Rename title and label of Live Bar Features

# data[].attributes.subject
Rename title and label of Live Bar Features

# data[].attributes.body
You can rename the title and label of all Live Bar features to your own preference.

Go to Live Bar > Select any feature and rename it accordingly for both title and label > Save and publish changes

# data[].attributes.headline
Toggle button to make Live Bar settings applicable to all livepages

# data[].attributes.subject
Toggle button to make Live Bar settings applicable to all livepages

# data[].attributes.body
Live Bar features are amendable per livepage. It will be good to have a toggle button if user wants to apply the same set of Live Bar settings across all livepages instead of setting them page by page.