Skip to main content

Functional Specification

Easily Assemble Lead Pages On The Fly With Existing Website Content​

FUNCTIONAL SPECIFICATION​

Key Functionality of the engine:

  • Floating sidebar UI for easy construction of lead pages from anywhere on the site
  • Taxonomy used to organize resources (posts) in the site
  • Simple interface with basic controls to shop for, and arrange content into custom configurations
  • Resources enabled with categorization and tagging in admin UI to apply taxonomies to content, making it available to the builder

ROLL-OUT LAUNCH STRATEGY​

GET OPERATIONAL WITH ADMINS/SITE PUBLISHERS, THEN EXPAND

While the UI will be very simple and easy to use, we suggest getting a first version of the engine up and running with current admins like Nicole and Mighty Digital initially creating pages. Get regularly published content up and running to gauge and measure effectiveness, and learn what works best. As the program gets operational & documented, other users can be added.

This will be a private feature of the site, available to staff, vendors, and partners. It will not be a publicly accessible tool. The pages that are generated will be for public viewing, but the interface used to build them will require login.

FEATURES​

  • ‘Shop’ for content (posts) by browsing the website to sections where filters are available
  • Content that can be filtered will be primarily in resources, but can expand as content gets taxonomy applied in the back end (e.g. search results)
  • Use filters (Category and tags) to sort content live on the site
  • Add desired content to the ‘cart’ (builder UI) to use for a custom content page
  • Generate custom page on the fly, driven by an encoded URL that can be shared
  • Custom URL+parameters will generate dynamic content pages for anyone with the link
  • The page(s) don’t exist in the CMS, like a post. They are based on the URL parameters. The engine assembles it onLoad, using a standard layout template, from components selected in the builder, and encoded in the URL.
  • Ranking of content + posts, to be able to grab different types of content as well as the most popular a/o relevant
  • Integrate Pardot form URLs (created in advance and added into back-end for use in pick-list)

FUNCTIONAL SPECIFICATION DETAILS​

OVERVIEW​

  • Landing page content driven by taxonomies (categories and tags).
  • CPTs and content on the site will be updated to support tagging and categorizing in Edit mode.
  • The taxonomy will be used as filters in resources to allow visitors to sort and filter content and get their own mix based on topics they choose
  • Editable taxonomy UI like Resource Library
  • Ability to track campaign URLs to form submissions. URL params, hidden field, etc.

TAXONOMIES​

  • Categories will be defined by IPInfusion
  • Site publishers and admins with back-end access will be able to categorize and tag content
  • Content that has taxonomies applied will be connected to the engine’s UI, so that content shows up when the page builder UI is running

LEAD PAGE BUILDER UI​

mightydev.sirv.com

Click to view Builder UI sketch

  • See sketch concept at link above ↑
  • Builder will be a right-hand column/overlay that can be toggled on and off
  • Admin users logged into WordPress will automatically see the icon
  • Non-WordPress accounts will onboard through a hidden link
  • That link will trigger an on-boarding dialog box to enter credentials

mightydev.sirv.com

Click to view Onboarding sketch

  • See sketch concept at link above ↑
  • The builder will have a common password and users will enter their email
  • Users will be internal/known users (staff, vendors, and partners), it will not be available to the public
  • Once users are cookied, the builder icon will be present in the upper right corner to allow easy access to the builder
  • On-boarding process will explain cookie function, how it will just work from here on
  • Include a link to How To docs/PDF download cheat sheet for using the builder
  • The login and Page Builder UI will be custom function specific to this tool only. It will not be a login to WordPress Admin

UI ELEMENTS​

  • PANEL ONE: Main banner/Top Item
    • Prompt to choose one resource shown on the website
    • Item title and link show up on click of card, with icon for OK or Error
    • In case of validation error, prompt to correct (’Needs featured image’ will be most common)
    • Field(s) for custom headline and subheadline
    • Clear/delete choice links/icons
    • Validate that all are selected before enabling panel #2
  • PANEL TWO: Resources Row
    • Prompt to select multiple items shown on the website
    • Quantity TBD, but there will be a Min/Max of 2-4, or 3-6
    • Same list of items by title with links and OK/Error icons
    • Clear/delete choice links/icons
    • Validate that all are selected before enabling panel #3
  • PANEL THREE: CTA Selection
    • Radio buttons with choices for pre-selected CTAs, such as:
      • Software Downloads
      • Contact Us
      • Webinar
      • (others TBD these are suggestions)
    • CTAs will be configured in Admin backend with shortcodes to use on site and in builder
  • PANEL FOUR: FUNCTION BUTTONS
    • Preview (opens in overlay or new tab with X to close)
    • Copy URL (with icon)
    • Reset
    • LinkedIn Post Checker (optional/future)
    • My URLs list (optional/future)
  • EASY BUTTON CONCEPT (future): Method for user to skip the builder and get an auto-selected layout in one click, based on templates a/o rules
  • ADMIN UI (Back End)
    • TBD brainstorm ideas here
    • Admins can have more granular control over CTAs, for example, to link to or embed forms for specific campaigns
    • In effect, this becomes an EZ Builder for admins, as a simpler UI for quick-turn content, before going to the full Editor experience in the CMS
  • ADMIN of users (?) add/modify/delete users in advance, and hand out logins
  • ADMIN builds CTAs as shortcode-accessed widgets in WordPress for builder and for general website use

RANKING (future)​

  • Define and describe features and UI for ranking/curating posts

URLs​

  • Syntax and logic definition (TBD Dimas)
  • Public URLs will be similar to filters seen on Feature Matrix
  • Ability to build pages by typing syntax into URL directly, if you are technical
  • Short URL support (future?) E.g., ipinfusion.com/resource?id=abc123
    • If so, these will need logging in short and long form for reference and tracking
  • Log all created URLs
  • Flag the public ones with too few results for Lead Pages, to gauge if more content is needed there
  • Capture filter result counts by category

SEARCH INTEGRATION​

TBD/Future

LOGS​

NEED Details here

TAXONOMIES​

The dynamic page concept will be driven by a taxonomy and tagging feature. Expanding on what was done in Partners for regions, would grow to include products, use cases, and any other relevant categories are defined.

INITIAL CATEGORIES & VALUES​

TBD: Which taxonomies to start with, and which content types to apply them to

  1. REGION (pull from Partners, use for Customer Stories first)
    • TBD how this would integrate
  2. PRODUCT/SOLUTION
    • SP-CSP
    • SP-AGGR
    • DC
    • RON
  3. TAGS
    • SOLUTION
    • PARTNER
    • CUSTOMER STORY
    • OTHERS?
  4. HARDWARE (future)
  5. RESOURCE TYPE
  6. CUSTOMER STORIES (if possible in first version with region taxonomy, else future)
  7. FREE FORM TAGS (e.g. Mobile, 5G, etc.)

ADDITIONAL NOTES & TASKS FOR PROJECT​

RESOURCES UPDATES​

Eventually consolidate resources from many CPTs down to one, with taxonomies applied

Filters in resource public view can have Copy URL icon at bottom of column for easy sharing (maybe add to Feature Matrix and HCL, too)

mightydev.sirv.com

Click to view UI sketch for Copy URL button on Resources public view

  • See sketch concept at link above ↑