A practical HTML presentation workflow

From three articles to a shareable slide deck with Codex

The author approved the story. Codex handled production.

Source material Codex build Human review
Akhilesh Keshap · Sample deck for HackerNoon

01

Three articles supplied the source material

The presentation still needed one argument, a clear sequence, and a format readers could open in a browser.

Article 1Your AI Agent Should Not Be Talking to All MCP Tools

Tool visibility and domain abstraction

Article 2Designing Reasoning Boundaries in Agentic Systems

Software, model reasoning, and human approval

Article 3How Do You Evaluate an Agent That Calls Tools That Call Other Tools?

Layered evaluation and execution traces

The job was synthesis

Compress the series without turning the deck into three article summaries placed back to back.

02

A four-step workflow kept the work simple

Each step produced a clear handoff to the next one.

  1. 1

    Provide sources

    Share the articles, documents, screenshots, and links that contain the evidence.

  2. 2

    Approve the storyline

    Agree on the audience, main takeaway, and one sentence for each slide.

  3. 3

    Build and refine

    Let Codex write the HTML, CSS, navigation, and slide layouts.

  4. 4

    Review and publish

    Check meaning and rendering, then publish the static files.

The author makes the editorial decision before Codex starts production.

03

The approved storyline connected the articles

Codex found the shared structure. The author approved it before the deck was built.

Source argument

Limit what the main model can see

The first article established the tool visibility boundary.

Source argument

Assign each decision to the right mechanism

The second article separated software, model reasoning, and human approval.

Source argument

Evaluate each boundary

The third article traced failures across the complete execution.

Approved deck argument

Reliable agents need boundaries around tool visibility, reasoning, and evaluation.

04

The build contract gave Codex clear boundaries

A short brief removed the need to describe every slide from scratch.

Audience
Technical readers interested in agentic systems

Main point
Reliable agents need three boundaries

Approved sequence
Tool visibility, reasoning, evaluation

Format
16:9 HTML deck with no build step

Behavior
Arrow keys, fullscreen, swipe, slide URLs

Guardrail
Do not invent evidence or strengthen claims

The author fixed

The audience, argument, evidence, level of certainty, and public sharing scope.

Codex could decide

Layouts, typography, spacing, reusable styles, and browser behavior.

05

Codex combined project context with reusable skills

Context supplied the facts. Skills guided how the work was done.

Context available to Codex

Conversation
The approved storyline, feedback, and revision requests
Source material
Article links, the pasted draft, and supporting text
Workspace
The existing HTML, CSS, JavaScript, and README files
Browser review
The live slide, rendered screenshots, and navigation state

Skills used during the build

  • PresentationsStoryline, layout, source accuracy, and validation
  • Frontend DesignVisual identity, typography, and responsive HTML
  • Ogilvy Writing AuditClarity, brevity, quotation checks, and the closing action

Skills guide the method. They do not replace the facts in the supplied sources. Codex can use only the context shared in the conversation or available in the permitted workspace.

06

Codex produced a working presentation website

The result used four static files and required no slide-authoring application.

index.htmlSlide content and structure
styles.css16:9 canvas, typography, and colors
script.jsNavigation, fullscreen, and swipe
README.mdLocal preview and publishing instructions

What the deck included

  • Left and right arrow navigation
  • Fullscreen presentation mode
  • Direct links to individual slides
  • Responsive scaling of the fixed canvas
  • Clickable links back to every source article

The deck source stayed readable, reviewable, and ready for Git.

07

One request reshaped the whole deck

A coding workflow made a narrative change easier to apply consistently.

Revision request

Make Codex the main topic and use the articles as the example.

Cover

The title changed from agent architecture to the deck-building result.

Sequence

The workflow moved ahead of the technical case study.

Examples

Architecture slides became evidence of what Codex produced.

Conclusion

The final message now separates production from editorial responsibility.

The same instruction could update repeated terminology, colors, links, or navigation across every slide.

08

Meaning and rendering needed separate reviews

A good screenshot cannot prove that the argument is correct.

Meaning review

  • Read only the slide headlines in order
  • Check every claim against its source
  • Preserve uncertainty and scope
  • Remove detail that does not serve the reader

Editorial question: Does the deck ask the audience to believe the right thing?

Rendering review

  • Inspect every slide at presentation size
  • Test overflow and element bounds
  • Use the navigation controls from beginning to end
  • Check the deployed version before sharing it

Practical result: Browser review caught a content and footer collision before handoff.

09

GitHub Pages turns the files into a shareable URL

Static HTML keeps publishing simple and makes the source easy to inspect.

  1. 1

    Create a repository for the deck

  2. 2

    Commit the HTML, CSS, JavaScript, and local assets

  3. 3

    Enable GitHub Pages from the publishing branch

  4. 4

    Test the public URL and each linked slide

Easy to share

Readers open one browser link.

Easy to review

Git can show each wording and design change.

Easy to reuse

The next deck can keep the same navigation and visual tokens.

Only publish material cleared for public sharing. Use approved internal hosting for private work.

10

Source articles used in the example

Each link opens the original HackerNoon article.

  1. Part 1Your AI Agent Should Not Be Talking to All MCP Tools

    Tool visibility and domain abstraction

  2. Part 2Designing Reasoning Boundaries in Agentic Systems

    Reasoning boundaries and execution layers

  3. Part 3How Do You Evaluate an Agent That Calls Tools That Call Other Tools?

    Evaluation seams and execution traces

The deck paraphrases these articles and uses them to demonstrate the Codex workflow.

The practical division of work

Codex handles production. The author owns the argument.

Codex handles

HTML structure, shared styles, navigation, layout changes, and browser checks.

The author decides

What the audience should believe, which evidence supports it, and what remains uncertain.

Start with one representative slide. Approve its message and design, then let Codex expand the deck.