Personalize further
What ADT Studio exports is yours to keep — shape it further by hand, with AI coding tools, or not at all.
Some personalization already happens inside ADT Studio, before you ever export — fonts and text sizing are set on the Storyboard stage, book-wide. Beyond that, everything exported — the Web Export, an EPUB, a SCORM package, or the project files themselves — belongs entirely to you or your organization from that point on. None of it is locked into a proprietary format: it's plain HTML, standards-based e-book and course packages, or the project folder itself, all of it readable and editable by any tool that understands those formats.
That means the export isn't a finished, sealed product — it's a solid starting point you're free to keep shaping, in-app or afterward.
In-app: fonts and typography
On the Storyboard stage, Font Settings let you attach font files or pick from Google Fonts, then either assign each font's role yourself (heading, body, caption, decorative, monospace) or select Analyze with AI to have it assign roles automatically from the page images. Fonts are embedded in the final bundle so they keep working offline; make sure you have the right to embed any font you upload. A Reset fonts action restores the default at any time.
Text sizes are a separate, book-wide scale: one size (mobile and desktop) per role — chapter title, section heading, subheading, body, caption — starting from the book's own detected sizes. Adjust any role yourself, or apply an Accessible sizes preset to scale the book up.
After export: two ways to keep customizing
- By hand. If you or your team already work with code, the exported files are just files — open them in any code editor (VS Code, or whichever you already use) and change what you need: visual styling, small fixes, extra interactivity, anything.
- With an AI coding assistant. Tools like Claude Code, GitHub Copilot / OpenAI Codex, or Gemini can make targeted edits from a plain-language description of what you want — useful if coding isn't your team's main skill, or you'd simply rather describe a change than write it. You (or someone you bring in) open the exported files and work with the assistant directly; this happens entirely outside ADT Studio.
Which one fits depends mostly on how comfortable your team is with code. A team with developers may prefer to work directly in the files; a less technical stakeholder may lean on an AI assistant to translate a request into a change; others may simply hand the files to a developer or vendor. No path is assumed or required — the export works the same regardless of what happens to it next.
This is entirely optional
Beyond the in-app font and typography settings, further personalization is entirely up to you — nothing about validating, distributing, or maintaining an ADT depends on it.