By use case

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.

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

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.

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.

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.

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.

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.

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.

A narrow screen rewraps long lines and destroys the shape of a poem. What preserves it, what to do about indentation, and where to put each poem.

Stores handle payment and discovery and keep the customer. A web sample at your own address is how readers find you rather than a category.

Publishing is free. Editing, a cover and reaching readers are not. What is genuinely free, what to pay for first, and what to skip.

A comic page is composed for a page. On a phone it needs a different reading order, and pretending otherwise is why panels become unreadable.

A story is read in one sitting and shared in one link. What makes that link get opened, and why submission rules decide where it can live.

Clients lose attachments and ask for things twice. A page per client holds the current state, and nobody has to create an account to see it.

An event, a campaign, a holding page. What should genuinely be temporary, and why the address should outlive the content every time.

Project tools assume everyone has an account. A status page per project gives the client what they need without adding them to anything.

A workbook carries hidden sheets, formulas and your source data. Publishing the numbers as a table sends what you meant and nothing else.

A code pointing at a drive document fails in two ways at once: it asks for access and it downloads on a phone. What to point it at instead.

Scanned surveys are answered standing up in under a minute. Length, the sign-in wall and the code placement decide the response rate.

A form posting to a service, a page saying what arrives, and consent you can evidence. What the law requires and what most signup forms get wrong.

A password on a deck stops casual opening. It does not stop forwarding, it breaks on some devices, and the password usually travels with the file.

A flipbook catalogue cannot be searched, which is the one thing a trade buyer needs. What to publish instead, and how prices stay current.

Uploading the print file produces a catalogue nobody can search. What to extract, what to keep as a download, and the order to do it in.

Customers check a menu before deciding where to eat. Allergens, prices and sold-out items all change, and the paper version cannot.

A quote attached as a file is a guess about timing and a version problem waiting to happen. What an address changes about following up.

Proposals are read by people you never met. What survives the forward, what to put first, and why the reading data changes the next version.

Invoices get forwarded to a finance team who never met you. What has to be on it, what accounts systems need, and what knowing it was opened changes.

Sending everything asks the client to do the matching. Sending the two relevant pieces with a line each is what turns an enquiry into a conversation.

A price list emailed as a file is quoted back at you long after the prices changed. One address, dated, is the fix and it takes minutes.

Monthly reports get skimmed for one number. One address updated each month, with the conclusion first, replaces a chain of attachments.

Most of a team never opens the tool. A page with the five numbers that matter reaches them, and screenshots in chat go stale immediately.

Asking what people think produces preferences. Asking specific questions about a live page produces answers you can act on.

Design tool links ask the client to sign in. A prototype at a plain address opens on their phone, and the feedback you get back changes accordingly.

One address on the invitation, checked months later in a car park. Times, parking and dress code change, and printed cards cannot.

A layered comic file is enormous and needs the software that made it. What to export for editors, for readers, and for print.

Screenshots of course screens look the same to everyone. The analysis behind them is what a hiring manager is actually assessing.

Studios look for topology and texture work as much as the final render. What to show alongside each piece, and how to keep the page fast.

Terms change and disputes are about the version in force at the time. Dated versions at permanent addresses solve that; a replaced page does not.

Entries written for the person affected, newest first, at one address. Why version numbers alone tell users nothing they can act on.