Close your site behind a page worth landing on, and collect the addresses of everyone waiting for it to open.
The complete list — what each part does and what it is there for.
Two modes, and the difference is not decoration. Coming soon answers normally, so the address can be shared and indexed while you build. Maintenance answers 503 with a Retry-After, so a crawler comes back instead of replacing your site with a holding page in its index.
Quiet ones — Plain, Card, Split, Notice — and ones with something going on: Aurora's drifting lights, Glass over your photograph, a Spotlight that follows the pointer, Blueprint paper, a blinking Terminal, a Marquee band. Pick one and override any of its four colours. No page builder, no template files, and every bit of motion stops for a reader who has asked for less.
Counts to the opening time you set, in your site's own time zone. It is drawn with the right numbers already in it, so it reads correctly before any script runs, and it measures the visitor's clock against your server so a phone that is an hour fast still counts down to the right moment.
A sign-up form built into the page, with the list kept on your own site. When you open, the plugin emails everybody who asked — in small batches, plain text, with a one-click unsubscribe, and nobody written to twice.
Every address is recorded on your site first and passed to Mailchimp afterwards, so an outage, an expired key or a deleted audience never costs a visitor their place on the list.
One address that lets somebody see the finished site without signing in and without a password. Their browser remembers for a week, so you send it once. Make a new link and everyone holding the old one is out immediately.
Shut the shop while the blog carries on, or leave one contact page open while everything else waits. The same tick lists, searchable fields and address patterns every Traslatability plugin uses to decide where it applies.
A discreet box at the foot of the page for a group who share one password. Stored the way WordPress stores yours, five wrong guesses and that visitor waits a quarter of an hour, and changing it signs out everyone using the old one.
Choose which roles see the site as normal while everyone else sees the page. Anyone who can change the setting always gets through, so unticking your own role cannot lock you out of your own front end.
Set a moment to close and a moment to open. Both are compared on every request as well as scheduled, so the site opens on the minute even on a host whose cron has not run for a fortnight.
Views, people and sign-ups, one row per day. No addresses stored, no user agents, no third-party script, and nothing that could identify a single visitor — so there is nothing to add to your privacy notice.
The stylesheet and the script are inside the page, the type is already on the reader's machine and the network marks are drawn rather than loaded. The page most likely to be opened on a bad connection makes no outside request at all.
Activate it on one site or across a whole multisite network. Each site keeps its own settings, its own list and its own counts, and a site added to the network later is set up on its own.
Every string in the plugin, the admin screens and the licence page is translated into Spanish and French, and the page itself is built from your words in whatever language you write them.
Every screen in the plugin arrives without a page load, and every save happens where you are standing. WordPress fetches the whole of wp-admin's CSS and JavaScript again to change one panel; this fetches the panel. The screen you are on is still there while the next one is on its way, and the one you are heading for is usually already in hand — a pointer takes a moment to reach a menu item, and that moment is spent fetching.
A save answers in the corner of the screen, bordered in the colour of what it is telling you and saying what was saved rather than just "Saved". Four seconds, and hovering holds it open. No reload, and no scrolling back to find a notice above the header three hundred pixels from the button you just pressed.
A WordPress admin request spends about a second in its own bootstrap before a plugin gets a word in, and fetching when your pointer arrives only buys back a fraction of it. So the plugin's other screens are fetched quietly while you read the first one — one at a time, only while the browser is idle, and never on a metered connection. By the time you click a tab the answer has been in memory for seconds.
One licence, every feature. Updates and support included.