diff --git a/CHANGELOG.md b/CHANGELOG.md index 884dc4ee..73726349 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,11 @@ # Changelog All notable changes to this project will be documented in this file. +## Unreleased + +### Improvements +- Content updates in the "Welcome" page. + ## 1.1.0 - 2018-08-20 ### Improvements diff --git a/static/css/welcome.css b/static/css/welcome.css index 72b6b2ab..180ff5cd 100644 --- a/static/css/welcome.css +++ b/static/css/welcome.css @@ -93,6 +93,10 @@ font-size: 12px; } +.use-cases li { + line-height: 200%; +} + .page-welcome .tab-content { border: 1px solid #ddd; border-top: 0; diff --git a/templates/front/welcome.html b/templates/front/welcome.html index 5c5b34d3..186d7104 100644 --- a/templates/front/welcome.html +++ b/templates/front/welcome.html @@ -318,6 +318,7 @@
{% site_name %} monitoring is a great fit for cron jobs and cron-like systems + (systemd timers, Jenkins build jobs, Windows Scheduled Tasks, wp-cron, uwsgi cron-like + interface, Heroku Scheduler, ...). A failed cron job often has no immediate visible + consequences, and can go unnoticed for a long time.
+ +Specific examples:
+{% site_name %} monitoring can be used for lightweight server monitoring: + ensuring a particular system service, or the server as a whole is alive and healthy. + Write a shell script that checks for a specific condition, and pings {% site_name %} + if successful. Run the shell script regularly.
+ +Specific examples:
+