All HTML guides

Every browser already reads documents. Extensions that offer to do it better ask for permission to see every page you open, including the private ones.

Authoring tools differ less in what they build than in what comes out and where it can go. Output format is the decision that survives the trial.

Suites are strong at building and opinionated about publishing. What to test in the trial, and the questions that only matter after year one.

A layout file is a recipe, not a meal. It points at images and fonts stored elsewhere, which is why sending it alone never works.

Tour software exports a folder that runs in any browser. Where that folder lives decides whether the tour keeps working after the subscription ends.

Publishing by archive works when the structure is right. Three mistakes account for nearly every failed upload, and all are visible before you send it.

Many people pay a subscription for four operations. What replaces it depends on whether you edit photographs, make graphics, or crop screenshots.

No sign-up means faster and it does not mean private. What to look for before uploading anything, and what should never go near one.

One changes a file and hands it back. The other puts it on the internet at their address. Choosing wrong is how documents end up branded by a stranger.

One source file, two outputs. The fixed document is for printing and the page is for reading, and most sources should produce both.

Plain text with a few punctuation conventions for structure. It opens in anything, survives every format change, and converts into all of them.

Open-source layout tools produce print-ready documents at no cost. The export settings are where a job succeeds or comes back from the printer.

A file on a server records nothing useful by default. What to measure, how to set it up, and why opens beat downloads as a number.

One publishes with a terminal command, the other with a browser. The right one is whichever the person maintaining the page already uses.

A practical artifact request, a complete fictional shift guide and a review path that separates the generated result from sharing and export.

Generated pages break on publishing for four predictable reasons. Asking for the right things up front removes all of them.

Generating a layout in a minute is real. What matters afterwards is whether you can take the page with you and what a correction costs.

Generated prose is competent and generic. Where it helps, where it flattens a story, and how to publish the finished piece at an address.

Most questions a bot answers come from information the site never displayed. A good page answers them faster and costs nothing to run.

Assisted coding gets you a working folder quickly. Publishing is a separate step, and it is where many of these projects stop.

Assisted editors make building fast and scope expensive. What to cut so the thing gets published, and what genuinely needs more than a page.

Generating a working page is solved. Getting it to an address, on a phone, with nothing exposed, is where most of these projects stop.

A domain is a rented name pointing wherever you say. Owning it is what lets you change hosts without breaking a single link.

Free names come bundled, borrowed or from registries that reclaim them. Each is fine for something temporary and wrong for anything printed.

Hosting means a machine serving your files at an address. Which kind you need depends on one question, and most sites need the simplest answer.

Technically straightforward and operationally constant. What self-hosting genuinely gives you, and the four things that make it a commitment.

The monthly figure is the smallest part. Renewal jumps, the domain, the certificate and the time to change one line are the actual bill.

The page is decided before anyone visits. That single property makes it faster, cheaper, safer and harder to break than the alternative.

Static describes how the page is served, not how often it changes. The word misleads people into thinking they need something they do not.

Most small sites do not need a generator. Start with the pages, add a build step only when repetition makes it worth the machinery.

A form needs somewhere to send the submission. An outside service does that in one line, and the spam handling is the part that matters.

Static sites start ahead on speed and rendering. What remains is one page per question, real titles, and an address you never change.

Analytics dashboards report dozens of figures. Four of them change decisions, and a small site needs no more than those.

Video files are too large to send and too slow to serve yourself. A hosting service plus your own page is the arrangement that works.

The exchange only works if what you give is worth more than the address. Most are not, and the format is usually wrong as well.

Most advice addresses machinery a static site does not have. What remains is a certificate, the domain account, and what you put in the page.

A template saves the layout and hands you somebody else’s decisions. Which ones are cheap to change and which ones you are stuck with.

On many small sites images are the largest part of the weight. Fixing them takes an hour and beats every other optimisation combined.

Five checks, about ten minutes, and they catch much of what gets reported back. Most of them are not about the code at all.

A formatter fixes indentation in seconds. It does not fix structure, and badly structured markup reads worse when it is neatly indented.

Browser editors remove the install, the terminal and the deployment. What they give up matters less than people assume for a small page.

Storage sharing is built for colleagues with accounts. Used on customers it produces permission screens, downloads and a link you cannot brand.

A sync folder keeps machines identical, which is a different problem from showing somebody a document. Using one for the other creates the friction.

Some storage services used to serve pages, and Dropbox and Google Drive both stopped. What replaced the practice, and why the replacement is better anyway.

A prototype in a design tool is judged on a laptop by somebody who was shown it. A prototype at an address is judged by a user, alone.

Export produces a folder with long identifiers in every filename and links that point inside the tool. What survives and what needs fixing.

A camera scans a building and produces a walkable model hosted by the vendor. The capability is real and the hosting arrangement is the commitment.

Cable is fastest and lossless. Messaging apps recompress. The format question catches people out after the files are already on the laptop.

Browser-based slides need no software, open on any device, and share as a link. What you give up and when that matters.

Interactive charts lose their hover on phones and their meaning without a caption. What to fix before sending the address to anyone.

An embed keeps the chart on the vendor’s service. An export gives you a folder. The difference decides whether the chart outlives the subscription.

Publish before the site is finished, at the real address, on the real domain. Everything discovered afterwards is discovered by visitors.

For a finished file, publishing is genuinely one step. What takes longer is the domain, and it is the only part worth doing carefully.

Holding client hosting means holding their uptime, their renewals and their emergencies. How to structure it so that stays deliberate.

A freelancer’s own site competes with billable hours and always loses. Build it so it needs nothing, and put the effort into the work pages.

Most small business sites are opening hours, services and a phone number. That is a static site, and the traditional hosting stack is overhead.

University space disappears at graduation, along with every link on every application. Own the domain now and the work follows you.

A daily puzzle needs no server: the answer is derived from the date, progress is kept in the browser, and sharing is a line of text.

Branching narrative tools export a single file that runs anywhere. The writing problem is structure, and it is harder than the software.

Interactive fiction moved to the browser because a story is one file. What that means if you want to play, and if you want to publish.