Legal Community Landing Page - Widget ===================================== Widget files ------------ - LegalLandingPage-Widget.xml Scripted content fragment (Velocity + inline JS) - style.less Scoped LESS, TR brand palette, responsive + WCAG AA - visibility-check.vm.txt Same visibility guard used by "Generic content" What the widget renders ----------------------- Hero banner ("Connect with the legal community") Three-icon resource nav row (Access learning resources / Connect with peers / Product updates) Four "Find your starting point" cards with the final Lucid chart copy 01 Getting started -- Learn the fundamentals 02 Diving deeper -- Building confidence through practice 03 Your tools in action -- See how others are using it 04 Stay in the know -- Keep pace with what's next Weekly AI digest signup with anonymous/registered user handling Contact us section and page-specific footer All external links use target="_blank" rel="noopener noreferrer". All widget copy and every URL is exposed as an admin-editable property so non-devs can adjust without a redeploy. HOW TO WIRE IT UP IN VERINT COMMUNITY (Customer Communities only) ================================================================= Background ---------- The site has two entry points to the same /legal/ group: - Open Communities -> Legal (no landing page, unchanged) - Customer Communities -> Legal (show this landing page first, for anonymous users only) Both navigate to the same URL, so we distinguish them with a query-string marker on the Customer Communities link (default: ?via=customer). The widget only renders when that marker is present AND the visitor is anonymous. 1. Import the widget -------------------- Administration -> Widgets -> Import Widgets Upload Widgets/Legal Landing Page/LegalLandingPage-Widget.xml (Verint packages the sibling style.less + visibility-check.vm.txt automatically when the widget is exported/imported.) 2. Drop the widget on the Legal group's home page ------------------------------------------------- Manage -> Groups -> Legal -> Manage Pages -> Group Home Page -> Edit Page. a. Add "Legal Community Landing Page" to the Content region (top). b. Confirm its Options: Visible to = Anonymous users only (default) Required query-string key = via (default) Required query-string value = customer (default) c. On every OTHER widget already on the page (Recent discussions, sidebar widgets, etc.) set Visible to = "Authenticated members". Result: anonymous users arriving through Customer Communities see ONLY the landing page; anonymous users arriving through Open Communities see the existing content unchanged. Combined gate behaviour: URL hit Anonymous Signed-in ------------------------------------ ---------------- --------------- /legal/ (Open Comm nav) real content real content /legal/?via=customer (Cust Comm nav) LANDING PAGE real content /legal/ (direct / refresh / bookmark) real content real content No redirects, one URL, one group home page. 3. Point the Customer Communities "Legal" nav item at the marker URL -------------------------------------------------------------------- The mega-menu is rendered by the Navigation widget on the site banner. Edit that widget: Administration -> Site header / Navigation widget -> Options -> Links Under "Customer Communities", find the "Legal" entry. Set its URL to: /legal/?via=customer Leave the "Open Communities -> Legal" link (if any) as: /legal/ For Custom links in the Navigation widget, this is exactly the `url=` value on the link. Applies equally to the mobile menu variant. Optional: if the Customer Communities panel exposes "Legal" only as a section header, make that header a link to /legal/?via=customer. 4. Configure the widget content ------------------------------- Edit the widget on the page and set: - Legal Learning Hub URL (external, opens in new tab) - Join the discussion URL https://community.thomsonreuters.com/legal/ - View what's new URL (CoCounsel Community) - Card 1..4 URLs per the story - Digest group Id Numeric Id of the Legal group (Manage -> Groups -> Legal -> Settings) Required for registered-user subscription. - Digest management URL Defaults to /user/email-digests - Create-account URL Defaults to https://community.thomsonreuters.com/legal/ - Privacy / Terms / Contact URLs for the footer 5. Verification / test cases (use an incognito window unless noted) ------------------------------------------------------------------- a. Visit /legal/?via=customer -> Landing page visible; other Content-region widgets hidden (visibleTo=authenticated). Landing page ONLY. b. Visit /legal/ (no marker) -> Landing page hidden. Existing content only. c. Sign in, then visit /legal/?via=customer -> Landing page hidden (visibleTo=anonymous). Real content only. d. Refresh /legal/?via=customer while anonymous -> Landing page still shows (marker persists in URL bar). e. Click Ask the community / any card CTA -> Opens in a NEW tab (target="_blank" rel="noopener noreferrer"). f. Click Subscribe while anonymous -> Redirects to CIAM sign-in via $core_v2_urls.LogIn(ReturnUrl=). g. Click Subscribe while signed in -> POST to /api.ashx/v2/users/current/emaildigestsubscriptions.json with the configured Group Id. HOW REQUIREMENTS MAP TO IMPLEMENTATION ====================================== Scenario 1 Initial load -> single widget renders every section Scenario 2 Icon nav -> three tags with configurable URLs Scenario 3 Card copy -> hard-coded stakeholder-approved copy Scenario 4 External links new tab -> every external has target="_blank" rel="noopener noreferrer" Scenario 5 Registered digest signup -> jQuery.telligent.evolution POST to /api.ashx/v2/users/current/emaildigestsubscriptions.json using the configured Group Id Scenario 6 Unregistered digest signup -> button redirects to $core_v2_urls.LogIn(ReturnUrl=) which is the CIAM entry point Scenario 7 Contact -> Sign in -> $core_v2_urls.LogIn(...) Scenario 8 Contact -> Create account -> configurable Create-account URL (defaults to the legal community URL) Customer-Comm entry-point gate -> ?via=customer query check + visibleTo=anonymous Out of scope items -> not rendered