🖌️ Setting a Theme as Default#

1. Click any theme card — a drawer opens with a live preview.
2. Adjust the options:
   • Appearance: Light or Dark (a ★ marks the theme’s recommended mode).
   • Button style: Solid or Gradient.
   • Editor appearance: Light, Dark, or Match app (this one is saved per user).
3. The whole app previews your choices live as you toggle.
4. Click Set as default to apply it for the workspace. A confirmation appears.

✨ Creating a Custom Theme#

1. Click Create theme.
2. Fill in the dialog:
   • Name (required, up to 40 characters)
   • Base: Light or Dark
   • Primary colour — pick with the color picker or type a hex value (e.g., #6633D1)
   • Secondary colour (optional) — used for gradient buttons
3. Watch the live preview update, then click Add theme.

Your custom themes appear in the gallery with Edit (pencil) and Delete (trash) icons on hover.

🌐 Custom Domains

Config page: /documentation-portal/settings (menu: Custom Domains) Used in: a portal’s Product Settings → General Info tab

🌟 Overview#

A custom domain is a personalized web address that puts your portal under your own brand. Setting one up is a two-part process:

1. Add & verify the domain on the Custom Domains page — prove you own it (via DNS) and let InteractiveDox provision an SSL certificate.
2. Attach the verified domain to a specific portal from that portal’s Product Settings.

Once both are done, visitors reach that portal over HTTPS at your custom address.

➕ Step 1 — Add a Domain#

1. On the Custom Domains page, click Add New Domain.
2. In the drawer, enter the Domain Name (e.g., docs.example.com). It’s validated for a proper domain format.
3. (Optional) Paste an ACM Certificate ARN if you already have one in AWS. Leave it blank to have InteractiveDox request the certificate automatically.
4. Click Save. The domain is created in Draft status, and a confirmation appears.

🧩 Step 2 — Configure DNS#

Open the domain to see the DNS records you must add at your DNS provider (GoDaddy, Cloudflare, Route 53, etc.). Each record has a copy button.

Copy each value into a matching record at your DNS provider, then save. DNS changes can take a few minutes (sometimes longer) to propagate.

✅ Step 3 — Verify#

InteractiveDox checks your DNS automatically on a schedule. To check right away, click Verify now in the domain drawer (there’s a short cooldown between manual checks).

A status timeline shows progress:

1. Ownership verified — the TXT record was found.
2. Routing detected — the CNAME points to InteractiveDox.
3. Certificate requested — AWS ACM starts issuing your SSL cert.
4. Certificate issued & attached — HTTPS is ready.
5. Domain active — ready to bind to a portal.

🔁 Domain Statuses#

🔗 Step 4 — Attach the Domain to a Portal#

A verified domain only goes live once you connect it to a portal:

1. Open the portal’s Product Settings → General Info tab.
2. Tick “Enable Custom domain for this portal product?”.
3. Pick your domain from the domain selector. Only Approved or Active domains appear, and any domain already claimed by another portal is hidden.
4. Save. InteractiveDox binds the domain to this portal; once bound, the domain becomes Active and your portal is served at that address.

🗑️ Editing & Removing a Domain#

• Edit: open a domain to change its name (only while in Draft) or update its certificate ARN.
• Delete: remove a domain from the Custom Domains page and confirm. This frees the address and detaches it from any portal that was using it.

🧭 Quick Recap#

1. Add the domain → 2. Add the DNS records at your provider → 3. Verify (auto or Verify now) → 4. Attach it to a portal in Product Settings. When the status reads Active, your docs are live on your own domain. 🎉