FarosCMS 0.1.53

• A part that says what needs attention, most serious first, each line with where to deal with it: a new version, storage nearly full, a system check that is not fine, no backup yet or one that is old or overdue, mail that could not be sent this week, a site that asks search engines to stay away, pages with no search description or the same title, links in content that still use an old address, addresses that were asked for and not found, drafts left alone for over 30 days, entries missing a language, no way of counting visits (or tracking code that is chosen but empty), and a site address that is not set. A site with nothing to say shows one calm line. Only six lines show; the rest open under Show N more. Each person sees only what they may deal with: an editor is told about drafts and languages, not about backups, mail or the system
• When the site's own analytics are on, a widget as wide as the page shows the last 90 days: visitors, page views, pages per visit, bounce rate and visit time with their change against the 90 days before, the chart, the pages most seen and where the visitors come from, how many are on the site now, and a link to the reports. With nothing counted yet it says how to see the first visit. It is the same chart as the reports (shared parts in partials/analytics-parts.twig)
• A tidier top: a greeting with a shortcut for each of the first types (+ New Page, + New Post…), and the figures as small tiles that open the screen they are about (content, form submissions of the last 7 days, storage with its bar, backups, system status)
• Drafts to finish: the newest drafts, how long each has been left (old ones are marked), with the number in all. Recent content has a row of the types with their counts. The recent activity, emails and system checks are compact rows; the storage bar is a tile of its own, where the users tile was
• 1 checks to review is now 1 check to review
• Tests: a new unit test for the list of things to watch and the counts that feed it (tests/unit/dashboard.php), more checks in the dashboard unit test, and an HTTP test of the page for the super admin and for an editor, the drafts, the lines, and the widget with and without visits (tests/http/dashboard_test.py). The full suite and CI were not run