tUX LP Reusable Content 08.2024
Reusable Content Block (RB) Guidelines
The following blocks represent reusable content blocks (RBs) across the different types of tUX landing page (LP) templates.
NOTE: All hyperlinks, email addresses, and/or phone numbers on LPs (aside from the TY page), must be approved by the Growth Marketing team before implementing.
NOTE: Approved hyperlinks, email addresses, and/or phone numbers will be hidden from AF LPs unless the link is required for compliance. Otherwise, AF LPs will be the same aside from the additional “Highest Level of Education” RFI Field.
NOTE: Landing Page Header will display differently than the tUX Demo Site Header. Please refer to tUX Site Strategy for more details.
Common Reusable Content Blocks
All LPs: RFI Copy (Right Side)
NOTE: Below is the standard RFI copy. No changes should be needed unless there is a nomenclature change or need to remove the Oxford Comma.
[RB] Request More Information
Complete this form to receive information about coursework, admissions, tuition, and more.
Visual Example
All LPs (except Brand): About Us
[RB] About the School Header (H2, 75ch)
This is a reusable content block that gives a brief overview of the school, and the brand-level value props of the institution. Highlights to hit include the school values, mission, accolades, and any additional brand messaging that should be included. This block will be featured on all program, vertical and suite landing pages. This block will NOT be used on the brand LP.
The content in this block should not exceed 500 ch.
Visual Example
All LPs: OLE
[RB] Online Learning Experience Header (H2, 60ch)
This is a reusable content block that should briefly highlight the benefits and values of learning online, including statistics, school-specific info (special software, portal, etc.), and general info (student support, career services, etc.). This block will be featured on all landing pages.
The content in this block should not exceed 375 ch.
Visual Example
Suite/Multiprogram LPs: CTA
NOTE: Header and button wording should match the RFI.