All HTML guides

Job boards expire and reformat. One address you control is what goes in the post, and it is what candidates forward to friends.

One address per case study, findable by the problem rather than by the client name. What to get approved, and what to do when you cannot name them.

Logos, a boilerplate paragraph, photographs at print resolution and a named contact. What journalists actually take, and what wastes their time.

Audience numbers, formats and prices at one address, updated in place. Why a PDF media kit is quoting last quarter within a month.

One takes a file you already have. The other builds a page from scratch. Picking the wrong one means either rebuilding or fighting an editor.

Both serve static files free with custom domains. The differences: builds and previews, private repositories on the free tier, and published usage limits.

Shooting, stitching and publishing a walkthrough. Where to start each viewpoint, how many to shoot, and what makes a tour abandoned halfway.

Stores, aggregators and selling direct. What each takes in commission and in customer relationship, and why exclusivity is the real decision.

Storage is for finding things again. Naming, folder depth and what to do about the versions problem, before it becomes forty files called final.

The format stores positioned glyphs rather than flowing text. What that means for a one-word change, and the three routes that actually work.

A page-turn animation borrows the feel of paper. What it costs in load time, phone reading and search visibility, and when a page serves readers better.

Workbooks, handouts and reference pages. Which of those needs to be printable, which needs to be searchable, and why they are different artefacts.

Authoring tools produce packages that only run inside a platform. What that locks up, when it is worth it, and what a page does instead.

Self-hosting is free until somebody has to maintain it. What each route costs in money and in attention, and what decides it.

Prompting produces the page in minutes. The part that stalls is everything between a file on your machine and an address somebody can open.

Prompting produces a file you own and can change anywhere. A builder produces a design inside a product. That difference decides the next two years.

Parsing and keyword checks are genuinely useful. Judgement about which experience matters for a role is not something a score can supply.

Browser development environments run your project while the session is warm. What that means for sharing it, and when to take the file out.

Every one of them produces a page in minutes. Speed, whether you can export, and what the free tier removes are what separate them.

Plain text with commas between values. Simple enough to have no types, which is why leading zeros vanish and dates change country.

Automatic conversion reproduces the appearance with absolute positioning that breaks at every other width. What the real work is.

Rejected uploads come from four things: encoding, delimiters, date formats and a header row that does not match. All four are checkable first.

Published guidelines from large organisations are worth studying for structure, not for length. What a small business should copy and what to ignore.

A separate address per place you publish answers the question. Tagged links cannot be printed, and shorteners take your links with them when they close.

The same five decisions apply to design, writing, engineering and teaching. Ordering, the floor, the brief, per-piece addresses and what to cut.

The newer format is a zip of XML and is smaller, safer and better supported. The older one persists in organisations that never changed a template.

The older format stops at 65,536 rows and frequently truncates without saying so. That alone decides which one to use for anything with real data in it.

Right-click, compress. Two minutes later the archive is the same size, because most of what people archive is already compressed.

Text survives, formatting shifts, and tracked changes are where it goes wrong. What to check before sending it back to whoever wrote it.

Once something fetches your file, the address and its shape are a contract. What to version, what to cache, and what never to change.

Genre readers buy on cover, category and the first page. What that means for where you publish and what the book page has to carry.

Editors need the file, reviewers need to watch. Those are different problems, and sending raw footage to a reviewer wastes hours of their connection.

Vector artwork files usually contain a PDF version inside them. That is why some tools open them and others show nothing.

The phrase covers three different kinds of product. Which one somebody means changes the price a great deal.

Per-learner pricing rewards small cohorts and punishes growth. What to check before signing, and the export question nobody asks at the start.

All of them produce code quickly. The differences that matter are whether you get a file, what it depends on, and how far it is from being published.

Serving web pages from Google Drive ended in August 2016, and the guides recommending it are still online. What to do instead.

One is a reading subscription, the other a publishing viewer. Both put your document inside their product, and that is the decision.

The tool exports a folder of tiles and a page. What has to stay together, why the tile count is large, and the path mistake that breaks it.

Identity is the visual system, brand is what people think. What a small business needs to produce, and where it has to live to stay consistent.

A brand book explains the thinking. Guidelines give suppliers the files. Publishing them as one document means neither job gets done.

Operations, finance, project management and analysis produce no images. What to show instead, and how to do it without disclosing anything.

Much document friction comes from three habits. Naming, one current version, and publishing anything somebody outside reads.

Attaching a document to a team message creates a copy per person. One address means everybody reads the same thing, including whoever joins later.

Portals cap uploads at five or ten megabytes. Scans are large because they are photographs, and re-exporting fixes it in one step.

Permanence, privacy, whether it displays, whether it can be corrected, and whether you learn it was opened. Every document link answers all five.

A layout file only opens in the program that made it. Exporting produces a readable document, and an address makes it readable on a phone.

Every drag-and-drop host publishes a page in a minute. They differ on what happens on day thirty, when the page needs a correction.

Converters turn a fixed page into absolutely positioned markup that breaks on a phone. When conversion is the right answer and when publishing is.

A picture of a page is not a page. What automated conversion gets right, what it gets wrong, and what a design has to specify before it can be built.

Site builders can upload documents as downloads or embed them in frames that may not display on phones. What works on every device and what only works on a desktop.

A working file holds layers nobody else can open. Which export format suits which job, and why the flattened copy is not a replacement.

Right-click and compress. The archive is the easy part; what breaks is hidden files, mail filters rejecting it, and phones that cannot open it.

Serialised crime works because each chapter ends on a question. What a reading page needs, how to structure chapters, and where the address goes.

Horror depends on control of pace and of what the reader sees next. A reading page either protects that or destroys it with one loading spinner.

One expects a finished page, the other expects a repository and a build. Comparing their feature lists answers the wrong question entirely.

Repository pages are free and static. Deployment platforms add builds, previews and functions. For a single finished page, most of that is unused.

A code printed on paper cannot be changed. What it points at can be, which decides whether the code still works in two years.

It closes the gap between something printed and something you can change. Where that is worth doing, and where a code is decoration.

Workbooks belong in a fixed format because they get printed. Everything else in a course reads better as a page, and most of it is not printed.