Microsite Framework

Key Benefits

• Upload your static files (HTML, CSS, JS, images, etc.) to your assigned FTP folder
• Your site will be instantly available at its own subdomain
• No complex deployment pipelines or CI/CD setup required
• Perfect for microsites, landing pages, and campaign websites

products.json Structure

The products.json file should contain an array of product objects. Each product object defines access permissions using the following structure:

[
  {
    "serviceArea": "WMC",
    "productCode": "US"
  },
  {
    "serviceArea": "Global",
    "productCode": "EU"
  }
]

Properties:

• serviceArea - Defines the service area or department (e.g., "WMC", "Global", "Research")
• productCode - Specifies the product or region code (e.g., "US", "EU", "APAC")

How It Works

The presence of products.json enables automatic authentication integration. Users who have access to any product listed in the file will gain access to the entire microsite.

This authentication model allows you to:

• Grant full site access to users with any matching service area and product code combination
• Define which user groups should have access by listing their associated products
• Integrate with existing authentication systems using standardized product codes
• Restrict the entire microsite to users from specific regions or departments

Note: This is an all-or-nothing access model - there is no page-level or content-level restrictions within the microsite.