All HTML guides

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.

Every collaboration tool assumes the other person signs in. What to do when they are a client, a supplier or somebody who will not create another login.

Per-user permissions, watermarking and an audit trail. Which transactions need that proof, and which are served by private addresses.

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.

The one link you get is the most valuable address you have. What you give up by renting it, and how little it takes to own one instead.

Builders are fast until you want the page somewhere else. What a one page site actually needs, and what an export is worth when you leave.

Drive is storage with sharing attached. For a recipient outside your organisation that shows up as permission screens and downloads.

Sync tools are built for files you work on. A client wants to read something, and the download-and-preview path is friction they did not sign up for.

An archive of pages becomes a site when the folder structure and the paths agree. What has to be at the root, and the path mistake that breaks everything.

Converting a design image to a working page means rebuilding it as text. What the automatic tools produce, and why the text has to be real.

A file on your machine is already a page. What it is missing is an address, and the four things that have to be true before it works for anyone else.

Uploading is the easy part. What decides whether the result works is the file name, the paths, and what the service does to the address afterwards.

Hosting is replaceable and the address is not. What a domain costs, what it protects, and the two records that point it at a page.

Free tiers differ in expiry, bandwidth and whether you can use your own domain. Which limit bites depends on what you are publishing.

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

Calculators, converters and internal tools do not need a server. Where the line is, and what to do about the three things that cross it.

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.

Fonts substitute, files bounce and phones download. Which route suits an editor, a reader and a system, and why those need different answers.

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.

What each free route shows, what it loses, and whether uploading a commercial deck to a viewer is a trade worth making.

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.

Neither wins generally. Four questions decide it every time, and three of them have nothing to do with how the document looks.

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.

The file works on your machine and arrives as code for everyone else. What to check before sending, and what to write alongside the link.

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.

A build produces a folder of static files. What has to be configured for routing to work, and the base path mistake that breaks every asset.

Serving the same content at three addresses splits your links and confuses search. Pick one, redirect the rest, and keep the extras anyway.

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.

Serving the file is easy. Whether another site can read it depends on one header, and whether it is safe depends on what is in it.

A shared stylesheet is a dependency for every page that loads it. Caching, paths inside it, and why editing one changes several sites at once.

A script at an address runs with full access to every page loading it. Caching, content type, and what you take on by sharing one.

A vector image can contain scripts, which is why some hosts refuse to serve one inline. What to strip, and when to inline it instead.

Self-hosting a typeface removes a third-party request and introduces two new problems: licensing and the moment before it loads.

A page with no icon gets a blank square in every tab and bookmark. Three files cover every place one is used, and caching hides your changes.

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

A status page on the same infrastructure as the product goes down with it. Where to put it, what to write during an incident, and how fast.

Release notes buried in a support portal go unread. One address per release, anchored, is what sales and support actually use.

Notes pasted into a chat channel are gone in a week. One address per meeting, with decisions separated from discussion, survives.

One address per topic, written so somebody with no access yet can follow it. What the first week actually needs and what can wait.