Ways to compare

Link vs attachment for a document: an attachment is a copy, a link is the document, and six consequences follow. Plus the two cases where a file still.

Screenshot vs live page: a picture removes selectable text, copyable numbers, the date, the screen reader, the phone layout and anything interactive..

Two ways to host static HTML free, and the difference is what you work on after: a file host makes the file the unit of work, a document makes the content.

Looking for a CodePen alternative usually means the reader wants the finished page rather than the editor. What each format puts first, and how to choose.

PDF vs HTML file is a choice between two opposite promises: a layout that never changes, or an address that shows the current version. Where each wins.

When to send a link instead of an attachment: what an email body renders, why the attachment is the worst of the three routes, and what to write.

Most people want one specific thing fixed. Five categories of Notion alternative, what each is good at, and a ten minute test that beats a feature chart.

Seat cost, permissions, search and what outsiders see. The four things that decide a team workspace, plus a migration order that does not strand links.

What self hosting a workspace involves: backups, upgrades, certificates, storage. When it is worth it, when a hybrid split is better, and how to test.

Open source and self hosted are not the same thing. What the licence gives you, the categories worth evaluating, and how to check a project is still alive.

No AI can mean three different things. What to check in the settings and in the terms, and which categories of tool genuinely stay quiet.

Two ways to get AI into a workspace: features inside the tool, or drafting in a chat and pasting the result. What each is good at, and where each fails.

One person does not need permissions, guest roles or admin panels. What to keep, what to drop, and the four categories that fit solo work.

OneNote, Loop, SharePoint and Teams cover most of a workspace if you already pay for them. Where each fits, and the one gap they leave for outbound pages.

Google Workspace already covers most of what teams use Notion for, except one thing: a page that renders HTML at a stable address. Where each side fits.

Teams leave Confluence for four different reasons, and each one points at a different replacement. Sort by job first, then compare tools.

Free wiki options split into three kinds, and only one of them stays free as the team grows. How to tell them apart before you migrate anything.

Self hosting a wiki is a real answer when data residency requires it. The comparison that matters is operational load per page read, not the feature list.

SharePoint, OneNote, Loop and Teams cover most wiki jobs on a licence you already pay for. Where each one fits, and the one gap none of them closes.

Documentation fails for reasons a wiki cannot fix: staleness and findability. Compare replacements by how cheap a correction is, not by feature count.

Three routes for putting HTML on a Confluence page, why pasted markup turns into plain text, and when linking to a rendered page beats embedding it.

PDF fixes the layout and freezes the content. HTML adapts and stays current. A row by row comparison and the cases where each one is the right answer.

Both formats can be accessible and only one is by default. What tagging actually costs, where PDFs fail on phones, and a checklist for each format.

Static means the server sends the same file to everyone. Dynamic means it builds a response per request. How to tell which your page needs, with examples.

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.

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.

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

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

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.

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

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

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.

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

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.

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 a file you own and can change anywhere. A builder produces a design inside a product. That difference decides the next two years.

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

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

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.

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.

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.

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.

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

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.

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.

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

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.

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

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