Software and online website content checklists

10 starter checklists for this group of clients. Each one names the pages, the requests and the help text.

API product

An API product site has to show a working request and response, explain how to get a key and state limits, prices and uptime in plain terms. Most delays come from docs owned by engineering, SLA figures and unclear rate limits.

8 pages, 42 requests

Browser extension

A browser extension site has to show what the extension does in ten seconds and say plainly what it can see in the browser. Most delays come from store listing details, permission explanations and screenshots that match the current version.

8 pages, 39 requests

Developer tools

A developer tool site has to get an engineer from the home page to a working install in minutes, with code that runs as written. The delays come from sample code nobody tested, benchmark claims and docs owned by another team.

7 pages, 37 requests

Membership community

A membership site has to sell a room that visitors cannot see inside, so it needs a clear promise, honest member numbers and plain rules for joining and leaving. Most delays come from pricing decisions, community rules and permission to show members.

8 pages, 40 requests

Mobile app

A mobile app site has to show the app on a phone, link to the right store and answer privacy and support questions before the stores ask. The usual delays are store listing assets, a privacy policy address and the real pricing.

7 pages, 41 requests

Newsletter

A newsletter site has to make the case for subscribing in one screen, show what an issue looks like and keep the archive findable. The slow parts are the archive export, sponsor details and consent wording on the signup form.

7 pages, 39 requests

Online course

An online course site has to say what a student can do at the end, show a sample lesson and make enrolment a single click. The slow items are the curriculum document, student results with permission and refund wording.

7 pages, 41 requests

Online marketplace

A marketplace site has two audiences with different questions, so it needs a separate story for buyers and for sellers, plain fee rules and visible trust signals. Most delays come from seller terms, payout details and category lists nobody has finished.

8 pages, 43 requests

Open source project

An open source project site has to take a stranger from curiosity to a working install in minutes, and show that the project is still maintained. Most delays come from licence details, contributor guidance and maintainers who answer slowly.

8 pages, 43 requests

SaaS landing page

A SaaS landing page has to say who the product is for, show it working and give a price or a clear next step. Real screenshots, customer permission to use names and a pricing page that is still changing cause most of the delay.

7 pages, 40 requests