All HTML guides

Share a spreadsheet as a link instead of an .xlsx attachment. Figures stay readable on a phone, formulas stay private, and nobody breaks your workbook.

Share a notebook as a link that renders outputs without anyone installing Python. What survives the export, what does not, and when to send the .ipynb.

Share a project with someone who does not use GitHub. What a repository link looks like to a non-developer, and what to send instead.

Share notes with someone outside your organisation. Why OneNote links fail for external recipients, and what to send instead.

Send a calendar invite as a link that works across Google, Outlook and Apple. What an .ics file does, why invites fail externally, and what to put on the page.

Put an event at one address people can share, bookmark and check on the day. What belongs on it, and what to do when details change.

Share your availability as a link instead of listing times in an email. Time zones stated once, no back and forth, and no booking tool required.

Put a job advert at one address you can share anywhere. What candidates check first, the salary question, and how to keep it current when the role changes.

Make a QR code point at a page you control, so printed codes never need replacing. Sizing, contrast, and what breaks a code in the real world.

Put the WiFi details at one address guests can open, with a QR code that joins the network in one tap. Changing the password stops meaning new signs.

Share screenshots as a link so they stay sharp and readable. What messaging apps do to an image, and when to share the page itself instead.

Share an album with people outside your photo service. Why album invitations fail across platforms, and what to send so everyone can just look.

Share a browser game as a link that runs on a phone in one tap. Touch controls, keeping it in one file, and what a page cannot do.

Share a survey as a link people complete on a phone. Question order, showing the length, and where the responses have to go.

Share an address as a link that opens in whatever map app the recipient uses, with the arrival details a map cannot tell them.

Publish a dataset at one address with the documentation beside it. What a CSV needs, why the column notes matter, and how to version it.

Give each order its own address so the customer checks the status without emailing you. What belongs on it, and how to keep it current.

Send a reminder as a link so the details travel with it. What a page can and cannot do, and why an .ics download beats a notification you cannot send.

Share a short recording as a link. Why GIF files are so large, when a video is better, and how to keep a demo under a megabyte.

Your email will not send because the attachment is too large. Why the limit exists, why compressing rarely helps, and the fix that works every time.

The attachment limits for Gmail, Outlook and corporate mail, why the real ceiling is lower than the stated one, and why the recipient decides.

Share something so the recipient opens it without signing in. Why drive links ask for access, what a page does differently, and what you give up.

The four ways to share a file online, what each one asks of the recipient, and how to choose. Most of the time the file is not what you are sending.

You zipped it and the size barely moved. Why that happens, which files genuinely compress, and what to do when zipping is not the answer.

An upload that fails silently or stalls at the end. The six causes in the order worth checking, and how to tell which one you have.

Reach someone without using email. What works when you have a phone number, a chat, or nothing but a person standing in front of you.

Attachment, cloud folder, or a link. What each costs the person receiving it, the size limits that bounce mail, and when a link is the only option.

Turn a PDF into an address anyone can open in one tap. No download, no size limit, and you can correct the document after you have sent it.

Give a PDF a web address so it can be linked, texted, printed on a card or turned into a QR code. What makes an address last, and what breaks one.

Storage keeps a file. Hosting puts it at an address a reader can open. Which one you need, what each costs, and the questions that decide it.

Linking to a document is easy. Making it open on screen rather than landing in a downloads folder takes two decisions. Both are covered here.

Built-in ways to lock a document on Mac and Windows, what a document password actually prevents, and why a private address is often the better answer.

The three ways to put a document inside a page, which of them fail on a phone, and the fallback that keeps every reader able to open it.

A code that points at an address can be updated. A code that carries the document cannot. The difference decides whether you reprint every card.

A document is shaped for paper and a page is shaped for a screen. What to keep, what to drop, and when converting is not worth the effort.

What changes when a brochure stops being a document and becomes an address. Page flips, prices that go stale, and knowing whether it was opened.

An issue at an address instead of a file to download. Where page-flip tools cost you readers, how to handle back issues, and what to measure.

Mail clients mangle layouts and images arrive blocked. A web version at a permanent address fixes both and gives the issue a life after the inbox.

Why each article needs its own permanent address, what breaks when addresses change, and the details that decide whether a shared link gets opened.

An annual report that opens in a tap, with the numbers in real tables and the summary reachable before page forty. What to keep as a document.

A catalogue at an address, with stock codes that are findable and prices you can correct after sending. Where flipbook catalogues lose orders.

Prices and departure dates change. A brochure at an address can be corrected after it is sent, and a page opened before leaving often stays readable offline.

Wifi, check-out, the temperamental shower. A house manual at one address, reachable by QR code on the fridge, answers it before the guest messages you.

One address carrying photographs, floor plan and viewing times, sent by message and printed on the board. Updating the price stops meaning a reprint.

Floor plans are studied, not glanced at. How to put one at an address where it opens full screen, keeps its dimensions legible and prints to scale.

An itinerary at an address updates when the schedule changes and opens on a phone at a station. What belongs at the top and what belongs nowhere.

Manuals are searched, not read. How to structure one around the questions people arrive with, and why a printed booklet stops being the main version.

An FAQ built from the questions you actually receive, at an address you can link to one answer at a time. Where accordions help and where they hide things.

Panoramas are heavy and most viewers arrive on mobile data. How to publish a tour that opens quickly, and when photographs would serve better.

Free image hosts expire, rewrite addresses and add watermarks. What breaks, what to check before relying on one, and when to embed images instead.

A candidate profile at one private address, sent to a hiring manager in a tap. Withdrawable when the process ends, and you can see it was opened.

One address that opens on a recruiter's phone, updates after you have sent it, and tells you whether it was read. When the PDF is still required.

An attachment tells you nothing after you send it. What an address can tell you, what it cannot, and how to use the information without being creepy.

A separate address per channel tells you where readers came from without any analytics setup. What tagged links do, and the ones that quietly break.

What a data room needs, what the expensive ones add, and where a set of private addresses is enough. Access that can be withdrawn when the deal moves on.

Where the link goes, what it should say, and why a portfolio address printed in a PDF has to be short enough to type by hand.

A program at one address, readable on a phone mid-set, updatable when the plan changes. Where a PDF plan loses clients and what to charge for.

Where to put a training plan so it opens in one tap, works on gym wifi, and can be adjusted mid-program without resending anything.

A design link that asks the viewer to sign in can lose them. How to publish the exported design at an address anyone can open.

Sharing a Power BI report outside the organisation: what each route needs, what Publish to web exposes, and options for clients and board members.