Skip to main content

Weblink 2.0: Setup Best Practices

Updated

Purpose: This article explains recommended setup practices for WebLink 2.0 so your storefront is easier to maintain, performs predictably, and gives learners a consistent experience across catalog, course, and checkout pages.

WebLink 2.0 works best when you treat it as a configured storefront rather than a heavily customized web application. In practice, that means keeping structure, branding, and content clean in Administrate before you embed or publish the experience.

Table of contents

Start with the learner journey

Before configuring WebLink 2.0, decide what the learner should do from start to finish.

  • browse a catalog
  • open a course or event detail page
  • choose a date or delivery option
  • complete checkout or submit a request

This matters because WebLink setup is easier when you design around the intended journey instead of configuring widgets in isolation.

Use supported configuration first

Use supported WebLink configuration options before considering any custom front-end changes.

  • Use the WebLink Builder where available
  • Use supported widget options to control behavior and layout
  • Avoid relying on CSS overrides to hide or alter built-in widget elements

This reduces maintenance risk and makes future updates less likely to break your implementation.

Prepare course content for WebLink

Course content should be concise, scannable, and written for storefront use.

Recommended field usage:

  • teaserDescription – keep this to about 250 characters, or approximately 2–3 sentences, for optimal display
  • description – use this for the main course explanation
  • outcomes – use short bullet-style statements where possible
  • topicsCovered and prerequisites – use these only where they add genuine buying or learner decision value

Well-structured content improves readability in catalog cards, detail pages, and shared links.

Keep branding consistent

WebLink 2.0 should feel like part of the same learner experience as your public site, portals, and checkout flow.

  • Use supported branding settings instead of ad hoc visual overrides
  • Confirm whether the same brand is used by Student Portal or Booking Portal
  • Test logos, colors, and background assets on real pages, not just in setup screens

A consistent brand reduces confusion and makes the storefront feel more trustworthy.

Configure catalog and event display carefully

Catalog and event presentation should match how you actually sell training.

  • Only show categories that belong in the storefront
  • Make sure event pricing and currency match the intended portal configuration
  • Review date, time, and location display for clarity
  • Prefer supported display options over custom page manipulation

If learners see the wrong events, wrong currency, or incomplete data, the root cause is often upstream configuration rather than the widget itself.

Test checkout and order data end to end

Always test the full WebLink 2.0 flow before launch.

  1. Open the live page that contains the widget or embedded storefront
  2. Browse to a real course or event
  3. Proceed through selection and checkout
  4. Confirm pricing, currency, and required fields appear correctly
  5. Submit a test booking or request
  6. Verify the resulting data is correct in Administrate

This is the fastest way to catch issues with content, visibility, order fields, or payment setup before learners encounter them.

Avoid common setup mistakes

  • Writing teaser content that is too long for preview use
  • Using one widget where a simpler widget would do
  • Overriding widget behavior with custom CSS instead of supported options
  • Publishing before testing the full learner journey
  • Changing shared branding without checking where else it is used
  • Assuming storefront issues are front-end only when the real problem is catalog or event setup

Related articles