All HTML guides

A Plotly figure exports to a single HTML file that keeps its zoom and tooltips. Where to put it so a colleague can open it without a Python environment.

A chart at an address keeps its tooltips and its data. What interactivity is worth on a phone, and when a labelled static image wins.

Uploaded HTML inside a course often will not run scripts. Hosting the page separately and linking it keeps interactive material working.

One address per session, readable on a phone, corrected in place. What to do about students who lost the link and materials that change mid-term.

Call sheets change hourly and crew read them on a phone at five in the morning. One address per production day beats a chain of attachments.

An HTML5 banner behaves differently in a page than in a design tool. How to preview every size at once and catch the failures before upload.

Weight limits, animation caps, the click tag and the final frame. What ad networks require, and how to keep a banner inside all of it.

Investors forward decks. An address survives the forward, updates when the numbers change, and tells you the deck reached the partner meeting.

A guidelines PDF nobody opens versus an address with copyable colour values and downloadable logos. What agencies and suppliers actually need.

A fictional online workshop page with a compact event brief, timed agenda and honest registration handoff awaiting confirmation.

What belongs above the fold, why a second call to action costs conversions, and how to test a variant without touching the main page.

Every extra field costs signups. What to promise, how often to say you will send it, and what has to happen in the sixty seconds after they submit.

A deck built to be talked over is unreadable alone. How to publish a version that stands by itself, at an address you can correct afterwards.

Decks bounce off mail servers and open badly on phones. An address carries the same slides, opens in a tap, and stays current after you send it.

The page runs on your machine and nowhere else. What to check before publishing it, and the three things that commonly break once it leaves the chat.

An artifact lives inside a conversation. Putting it at your own address means it opens without an account, keeps working, and belongs to you.

Whatever produced the page, the same four things break when it leaves the tool. A checklist, then an address anyone can open.

Sending the file produces a wall of code and a confused reply. An address produces a working page. What to say alongside it.

Building by prompting is fast. Getting the result in front of someone is where most of it stops. What a single page can carry and what needs more.

What happens to formatting in each viewer, which ones need an account, and what to do when the document has to be read on a phone.

Leading zeros vanish, dates change, and long numbers turn into scientific notation. Why it happens on open and how to avoid it entirely.

Import settings that prevent silent conversion, what the locale does to dates, and when a published table beats a shared spreadsheet.

A table on a page reads on a phone, keeps its leading zeros and cannot be mangled by the reader. How to build one that stays readable at width.

What each free option does to fonts, animations and speaker notes, when uploading is a bad idea, and what the sender should have sent instead.

Layered design files are enormous and need software most people do not have. What the free options show, what they lose, and what to ask for instead.

Every operating system already extracts archives. When an online tool is genuinely needed, what it costs you, and how to avoid sending one next time.

What actually protects a document, what only looks like it does, and the one control that matters most: being able to take access away.

The stated limit is not the real one. Why encoding inflates attachments, what corporate servers do quietly, and the three routes that work.

A minute of phone video exceeds every mail limit. What to compress, what to link, and why the recipient should be watching rather than downloading.

An expiring link ends access and does not un-send anything. When it is the right tool, when it quietly breaks things, and what to use instead.

Transfer services move files. Pages show documents. Which one your situation needs, and the questions that decide it in about ten seconds.

Expiry, hotlink blocking and address changes all happen quietly. The three checks before relying on one, and when to keep images with the page.

Clients cannot judge copy without knowing what it had to do. How to present pieces with the constraint and the result, at an address you can send.

Art directors look at the first three pieces on a phone. What to show, what to cut, and how to keep large images from making the page unusable.

Platforms change their feeds and their rules. A portfolio at an address you control keeps working, loads faster and belongs to you.

Coursework and personal projects can carry a portfolio if the brief and the reasoning are visible. What reviewers look for when experience is absent.

Most one-file hosts do the same thing. The differences that matter are expiry, whether you can edit after publishing, and what happens to your address.

Pages is free and excellent if you already work in repositories. For one file and no version control, the setup is most of the effort.

Deployment platforms are built around a pipeline. If your page has no build, most of what you are configuring is machinery you never needed.

The file view shows code and the raw link downloads it. Neither renders the page. What actually publishes it and what to watch for.

A course is pages, video and a way to ask questions. What a platform adds, when it is worth it, and how to run the first cohort without one.

An LMS is enrolment, tracking and records. It is not a content tool, and treating it as one is why so much course material is unreadable.

Some studios still ask for a PDF. What it is genuinely good at, why it fails on a phone, and how to keep both versions without maintaining two.

A downloaded file reports nothing. A document at an address reports opens, and page-level reading data is noisier than it is usually presented as.

Links and form fields usually work. Video, buttons and scripted behaviour usually do not. What each reader supports and when a page is the better answer.

Built-in tools handle pages and annotations. Changing text is harder than it looks, and uploading a contract to a free editor deserves a second thought.

Printing to PDF captures whatever is on screen, including the parts nobody wants. What print styles fix and what to do when you do not control the page.

Print styles decide what appears on paper. The twenty lines that hide the furniture, keep tables whole and make links useful once printed.

EPUB reflows to the reader's screen and font size. A PDF does not. Which one a book needs, and what it means that EPUB is HTML in a container.

The exported profile is a dump of every field in profile order. What it is genuinely useful for, and what to send instead when it matters.

Posts do not accept documents. What each surface allows, why a link with a preview outperforms an attachment, and what to post instead.

Printing to a document loses the headers that prove when it was sent. What to include when the copy might matter, and what it does not prove.

Filters, tooltips and drill-through do not survive an export. What to do about the missing context, and when a page serves the reader better.

An infinite canvas exported to fixed pages loses the spatial reasoning that made it useful. What to export, what to rewrite, and what to link.

Document platforms surround your file with their branding, their reader and their prompts. What you give up, and when hosting it yourself is simpler.

Fonts are the reason a converted document looks different. What to embed, which converter to use, and when the recipient needed a page instead.

Documents are already compressed, so archiving saves almost nothing. What actually reduces the size, and when an archive is still the right move.

Converting extracts the text and rebuilds the layout approximately. Good for getting words out, poor for anything where the layout mattered.

A PDF menu behind a QR code is the most common mistake in hospitality. What to do instead, and how a price change stops meaning a reprint.

One chapter per address, readable on a phone, with the reading position kept. What platforms give you and what they take in return.