Fix MD posts (#107)

* Add some blog post updates * Update record * More records updated * More files and add border blockquote to mdx * More changes * Remove comments * Closing tags * More posts * Remaining records * Rename script and add prebuild script
sourcegraph · Apr 11, 2022 · 0c38afb · 0c38afb
1 parent e00be60
commit 0c38afb
Show file tree

Hide file tree

Showing 234 changed files with 2,020 additions and 2,922 deletions.
diff --git a/content/blogposts/2016/announcing-checkup-simple-self-hosted-health-checks.md b/content/blogposts/2016/announcing-checkup-simple-self-hosted-health-checks.md
@@ -35,7 +35,8 @@ We talked to [Matt Holt](https://twitter.com/mholt6), creator of the [Caddy web
 
 Health checks should be as easy to create and maintain as unit tests. We wanted an interface that lets you easily say, “Here are a bunch of URLs I want to test. Here’s the expected behavior for each.” It seemed to us that the best interface for declaring these was not a GUI that forced you to point and click, but a config file. Here’s an example **checkup.json**:
 
-<pre name="4277" id="4277" class="graf graf--pre graf-after--p">{
+```
+{
      "checkers": [{
          "type": "http",
          "endpoint_name": "Website",
@@ -48,30 +49,37 @@ Health checks should be as easy to create and maintain as unit tests. We wanted
          "secret_access_key": "&lt;yours&gt;",
          "bucket": "&lt;yours&gt;"
      }
-}</pre>
+}
+```
 
 You simply specify a list of endpoints in JSON and provide Checkup access to an S3 bucket. (Checkup can automatically provision this for you if you’re not familiar with the AWS control panel.)
 
 Then all you need to do to check the health of your endpoints is run
 
-<pre name="264c" id="264c" class="graf graf--pre graf-after--p">**$ checkup**
+```
+**$ checkup**
 == Website - https://sourcegraph.com
   Threshold: 0
         Max: 136.296933ms
         Min: 37.716659ms
      Median: 51.626374ms
        Mean: 65.212206ms
         All: [{54.489828ms } {45.93124ms } {51.626374ms } {136.296933ms } {37.716659ms }]
- Assessment: healthy</pre>
+ Assessment: healthy
+ ```
 
 You can have Checkup upload this data to your S3 bucket with
 
-<pre name="941a" id="941a" class="graf graf--pre graf-after--p">$ checkup --store</pre>
+```
+$ checkup --store
+```
 
 or have it run every 10 minutes with
 
-<pre name="758e" id="758e" class="graf graf--pre graf-after--p">$ checkup every 10m
-^C</pre>
+```
+$ checkup every 10m
+^C
+```
 
 And with Checkup and Caddy, you get a nice, simple status page like the one above that works out of the box and pulls data live from your S3 bucket.
 

diff --git a/content/blogposts/2016/appdash-an-open-source-perf-tracing-suite.md b/content/blogposts/2016/appdash-an-open-source-perf-tracing-suite.md
@@ -29,11 +29,11 @@ This post will walk you through an example app that uses Appdash and cover exact
 
 If you don’t already have Go, [install that first](https://golang.org/doc/install). Then install Appdash by running:
 
-<pre name="27e2" id="27e2" class="graf graf--pre graf-after--p">go get -u sourcegraph.com/sourcegraph/appdash/...</pre>
+<pre name="27e2" id="27e2" className="graf graf--pre graf-after--p">go get -u sourcegraph.com/sourcegraph/appdash/...</pre>
 
 This will also install the example web app in the Appdash repository that demonstrates the basic features of Appdash. Let’s run that first:
 
-<pre name="c9e1" id="c9e1" class="graf graf--pre graf-after--p">$ go get -u sourcegraph.com/sourcegraph/appdash/...
+<pre name="c9e1" id="c9e1" className="graf graf--pre graf-after--p">$ go get -u sourcegraph.com/sourcegraph/appdash/...
 $ webapp
 2015/04/27 20:40:56 Appdash web UI running on HTTP :8700
 [negroni] listening on :8699</pre>

diff --git a/...e-review-code-on-github-like-in-an-ide-with-the-sourcegraph-chrome-extension.md b/...e-review-code-on-github-like-in-an-ide-with-the-sourcegraph-chrome-extension.md
@@ -18,7 +18,7 @@ _Update (June 22, 2016): Added support for pull requests and diffs._
 
 [**Install Chrome extension for GitHub.**] (https://docs.sourcegraph.com/integration/browser_extension) And don’t let your team review any code until they get it, too!_For Go, Java, TypeScript, and JavaScript only; more languages_ [_coming soon_](https://sourcegraph.com/beta)_!_
 
-<iframe width="640" height="480" src="https://www.youtube-nocookie.com/embed/hIs4QtuM1Ig" frameborder="0" allowfullscreen></iframe>
+<iframe width="640" height="480" src="https://www.youtube-nocookie.com/embed/hIs4QtuM1Ig"frameBorder="0"allowFullScreen></iframe>
 
 The [Sourcegraph Chrome extension](https://docs.sourcegraph.com/integration/browser_extension) keeps you in flow while coding, with:
 
@@ -31,11 +31,11 @@ The [Sourcegraph Chrome extension](https://docs.sourcegraph.com/integration/brow
 
 It’s totally free. See what other devs are saying about it:
 
-<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Learning a new code base using <a href="https://twitter.com/sourcegraph">@sourcegraph</a> is extra dope! <a href="https://t.co/MKbac0RB0B">https://t.co/MKbac0RB0B</a> <a href="https://t.co/6YWeYyyYZo">pic.twitter.com/6YWeYyyYZo</a></p>&mdash; Kelsey Hightower (@kelseyhightower) <a href="https://twitter.com/kelseyhightower/status/791084672797122561">October 26, 2016</a></blockquote>
+<blockquote className="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Learning a new code base using <a href="https://twitter.com/sourcegraph">@sourcegraph</a> is extra dope! <a href="https://t.co/MKbac0RB0B">https://t.co/MKbac0RB0B</a> <a href="https://t.co/6YWeYyyYZo">pic.twitter.com/6YWeYyyYZo</a></p>&mdash; Kelsey Hightower (@kelseyhightower) <a href="https://twitter.com/kelseyhightower/status/791084672797122561">October 26, 2016</a></blockquote>
 
-<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Used <a href="https://twitter.com/sourcegraph">@sourcegraph</a> jump-to-definition across 3 projects, 2 langs, finally landing deep in Golang src. Took &lt; 10 min to pin down the issue. 💪🏼</p>&mdash; Gabe Monroy (@gabrtv) <a href="https://twitter.com/gabrtv/status/738861622882508801">June 3, 2016</a></blockquote>
+<blockquote className="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Used <a href="https://twitter.com/sourcegraph">@sourcegraph</a> jump-to-definition across 3 projects, 2 langs, finally landing deep in Golang src. Took &lt; 10 min to pin down the issue. 💪🏼</p>&mdash; Gabe Monroy (@gabrtv) <a href="https://twitter.com/gabrtv/status/738861622882508801">June 3, 2016</a></blockquote>
 
-<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">&quot;Do you use source graph?&quot; My multi-times a day question for when I talk to people about <a href="https://twitter.com/github">@github</a> projects. <a href="https://twitter.com/hashtag/devBetter?src=hash">#devBetter</a> <a href="https://twitter.com/sourcegraph">@sourcegraph</a></p>&mdash; chase adams (@chaseadamsio) <a href="https://twitter.com/chaseadamsio/status/774284535655653376">September 9, 2016</a></blockquote>
+<blockquote className="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">&quot;Do you use source graph?&quot; My multi-times a day question for when I talk to people about <a href="https://twitter.com/github">@github</a> projects. <a href="https://twitter.com/hashtag/devBetter?src=hash">#devBetter</a> <a href="https://twitter.com/sourcegraph">@sourcegraph</a></p>&mdash; chase adams (@chaseadamsio) <a href="https://twitter.com/chaseadamsio/status/774284535655653376">September 9, 2016</a></blockquote>
 
 * * *