Abridge blog posts in index view.

content/blog/2015-04-24-prometheus-monitring-spreads-through-the-internet.md

@@ -16,6 +16,8 @@ catch up on anything you missed.
 In the future, we will use this blog to publish more articles and announcements
 to help you get the most out of Prometheus.
 
+<!-- more -->
+
 ## Using Prometheus
 
 Posts on how to use Prometheus comprise the majority of online content. Here

content/blog/2015-06-01-advanced-service-discovery.md

@@ -22,6 +22,7 @@ In this blog post, we will take a closer look at the built-in service discovery
 some practical examples. As an additional resource, see
 [Prometheus's configuration documentation](/docs/operating/configuration).
 
+<!-- more -->
 
 ## Prometheus and targets
 

content/blog/2015-06-18-practical-anomaly-detection.md

@@ -19,6 +19,8 @@ detect and handle with custom-built rules. The Prometheus [query
 language](../../../../../docs/querying/basics/) gives you the tools to discover
 these anomalies while avoiding false positives.
 
+<!-- more -->
+
 ## Building a query
 
 A common problem within a service is when a small number of servers are not

content/blog/2015-06-24-monitoring-dreamhack.md

@@ -30,6 +30,8 @@ or *dhtech*. This post is going to focus on the work of dhtech and how we used
 Prometheus during DreamHack Summer 2015 to try to kick our monitoring up another
 notch.
 
+<!-- more -->
+
 ## The equipment
 Turns out that to build a highly performant network for 10,000+
 computers, you need at least the same number of network ports. In our case these

content/blog/2015-08-17-service-discovery-with-etcd.md

@@ -24,6 +24,8 @@ In this post we will implement a small utility program that connects a custom
 service discovery approach based on [etcd](https://coreos.com/etcd/), the
 highly consistent distributed key-value store, to Prometheus.
 
+<!-- more -->
+
 ## Targets in etcd and Prometheus
 
 Our fictional service discovery system stores services and their

content/blog/2016-01-26-one-year-of-open-prometheus-development.md

@@ -22,6 +22,8 @@ Docker and Boexever in 2014. Over the years, Prometheus was growing more and
 more mature and although it was already solving people's monitoring problems,
 it was still unknown to the wider public.
 
+<!-- more -->
+
 ## Going public
 
 Everything changed for us a year ago, in January of 2015. After more than two

content/blog/2016-03-03-custom-alertmanager-templates.md

@@ -30,7 +30,7 @@ route:
   receiver: 'slack-notifications'
   # All alerts in a notification have the same value for these labels.
   group_by: [alertname, datacenter, app]
-  
+
 receivers:
 - name: 'slack-notifications'
   slack_configs:
@@ -45,7 +45,9 @@ It shows us that there is one firing alert, followed by the label values of
 the alert grouping (alertname, datacenter, app) and further label values the
 alerts have in common (critical).
 
-## Customize 
+<!-- more -->
+
+## Customize
 
 If you have alerts, you should also have documentation on how to handle them –
 a runbook. A good approach to that is having a wiki that has a section for
@@ -66,11 +68,11 @@ by the Go programming language.
 ```yaml
 global:
   slack_api_url: '<slack_webhook_url>'
-  
+
 route:
 - receiver: 'slack-notifications'
   group_by: [alertname, datacenter, app]
-  
+
 receivers:
 - name: 'slack-notifications'
   slack_configs:
@@ -105,7 +107,7 @@ field and we provide a path to our custom template file:
 ```yaml
 global:
   slack_api_url: '<slack_webhook_url>'
-  
+
 route:
 - receiver: 'slack-notifications'
   group_by: [alertname, datacenter, app]

content/blog/2016-03-23-interview-with-life360.md

@@ -33,6 +33,7 @@ services written in Go, Python, PHP, as well as plans to introduce Java to our
 stack. We use Consul for service discovery, and of course our Prometheus setup
 is integrated with it.
 
+<!-- more -->
 
 ## What was your pre-Prometheus monitoring experience?
 

content/css/docs.css

@@ -368,7 +368,3 @@ aside {
 article {
   margin: 10px 0 60px 0;
 }
-
-.read-more > a {
-  color: #888;
-}

lib/default.rb

@@ -18,7 +18,7 @@ module BlogHelper
     content = post.compiled_content
     if content =~ /\s<!-- more -->\s/
       content = content.partition('<!-- more -->').first +
-      "<div class='read-more'><a href='#{post.path}'>Continue reading &rsaquo;</a></div>"
+      "<div class='read-more'><a class='btn btn-primary' href='#{post.path}'>Continue reading &raquo;</a></div>"
     end
     return content
   end