A microsite is an HTML website that is uploaded to Experience League directly instead of through the standard authoring pipeline. Microsites are useful for displaying HTML sample files or providing tools or services not available through markdown authoring.


Creating a microsite

  1. Create an AdobeDocs git repo that begins with microsite- (no .en suffix).

    For microsites, the repo name is NOT used in the URL.

  2. Add the HTML files and supporting CSS/JS reference files to the repo.

    Microsite git repo

  3. Log a JIRA ticket (project = UGP; component = Authoring) with a title such as “Add microsite for <x>,” and assign it to Bob Bringhurst.

    Bob will work with you to determine the microsite URL. See image below for examples.

  4. (Admin task) Specify settings in the Microsites YAML file.

    Microsite config image

    Current top-level keys used in the URL include tools, landing, and developer. If new top-level keys are required, clone this ticket.

  5. Test the microsite after it gets pushed.

    Any microsite edits are picked up once a day (midnight PT). Contact Bob if you want to push changes more quickly than that.

Adding SEO metadata to your microsite content

If you want to add description or other metadata to your microsites, use a format similar to the following sample.

<!doctype html>
    <title>Adobe Target Sample Size Calculator</title>
    <meta name="description" content="The Adobe Target Sample Size Calculator helps you determine the sample size needed for a successful A/B test.">

Note that metadata such as solution, role, level, and feature is not used in Experience League at this time.

Adding Analytics tags to your microsite content

Not yet available. HTML is simple pass-through, with no out-of-the-box connection to EXL. Writers need to add their own analytics tagging.

On this page