..  include:: /Includes.rst.txt

..  _introduction:

============
Introduction
============

..  _what-it-does:

What it does
============

A :file:`robots.txt` taken along from staging hides the entire site. Nothing
breaks, the pages look right, and the mistake surfaces weeks later when someone
asks why the site is not in Google. The sitemap line in :file:`robots.txt` is
the only place in a TYPO3 configuration where the domain is spelled out, so it
is the only one that does not travel along when the site moves. A 404 handler
pointing at a hidden page turns every unknown address into a server error.

This extension adds one backend module that looks for those, and for about two
dozen more. It reads the site configuration, the page tree and
:php:`$GLOBALS['TYPO3_CONF_VARS']`, and it sends real HTTP requests to the
site's own live address — because half of these mistakes are invisible from the
inside.

Every finding names the value that was found, not a rule that was violated:
the wrong base URL, the pages still flagged as :sql:`no_index`, the sender
address still pointing at :file:`example.com`.

..  figure:: /Images/report.png
    :alt: The Go-Live Check module, showing the verdict with counts by severity and the first findings
    :class: with-shadow

    One report per site. The header counts by severity, and the verdict says in
    three words whether this site can go live.

..  _what-it-is-not:

What it is not
==============

..  rst-class:: dl-parameters

Not a scanner
    It checks the site it is installed in, over its own configured base URL.
    It cannot be pointed at a foreign domain.

Not a rule engine
    The list of checks is fixed in code, and so are the word lists behind a few
    of them (placeholder text, template titles, common passwords). There is no
    configuration to tune, and no thresholds to set. Extensions can
    :ref:`add their own checks <extending>`.

Not a cron job
    The report is built when the module is opened, in the request of the
    backend user who opened it. Nothing runs in the background, nothing is
    stored except the ticks of the manual checklist, and nothing is sent by
    e-mail.

Not a guarantee
    A green report means the things this extension knows how to look at are in
    order. The twelve manual points exist precisely because the important
    remainder — a tested backup restore, imported redirects, consent before
    tracking — cannot be established by a machine.

..  _why-it-skips:

Why it skips instead of passing
===============================

A check that cannot reach its answer reports as *not verifiable*, never as
passed. No loopback connection to the live URL, an extension that is not
installed, a relative base URL that makes a domain comparison meaningless —
all of these end in a grey result with the reason.

A false green is worse than no statement at all, because it replaces the very
check it pretends to be.