Markdown Updates (#166)

* update broken footer links

* terms WIP

* terms markdown markup

* update links to relative and new URIs

* more link edits

* md updates WIP

* update from sourcegraph/about#5359

* updates from sourcegraph/about#5355

* updates from sourcegraph/about#5355

content/blogposts/2018/how-to-support-your-employee-through-pregnancy-maternity-leave-and-the.md

@@ -1,5 +1,7 @@
 ---
-title: 'How To Support Your Employee Through Pregnancy, Maternity Leave and the Transition Back To Work'
+title: 'How to support your employee through pregnancy, maternity leave, and the transition back to work'
+externalTitle: 'Welcome back from maternity leave: How to support a returning employee'
+externalDescription: 'Working parents need time off to care for their children and a positive welcome back from maternity leave. Learn how to support them here.'
 author: 'Vanesa Ortiz'
 publishDate: 2018-08-28T09:00-06:00
 tags: [
@@ -10,19 +12,20 @@ heroImage: https://images.ctfassets.net/le3mxztn6yoo/luDj9P2olaGusw64m4koA/c3b44
 published: true
 ---
 
-Today was my first day back to work at [Sourcegraph](https://sourcegraph.com) after my 3 1/2 months* long maternity leave. I consider myself lucky to be working at a company that is family friendly and has made my journey to parenthood much easier than expected. I decided to share some of the points I believe Sourcegraph and others do right and I encourage companies to follow.
+Today was my first day back to work at [Sourcegraph](https://sourcegraph.com) after my 3 1/2 months* long maternity leave. I consider myself lucky to be working at a company that is family friendly, has made my journey to parenthood much easier than expected, and has made for a warm welcome back from maternity leave. I decided to share some of the points I believe Sourcegraph and others do right and I encourage companies to follow.
 
+## 13 tips for an effective welcome back from maternity leave
 1. Have a parental leave policy ready and help your employee file the correct forms at the [Employment Development Department](https://www.edd.ca.gov/). I was hired pregnant and despite having the first pregnancy in the company, Sourcegraph had its parental policy in place and I was supported throughout the entire process of filing for State Disability Insurance (SDI) and Paid Family Leave (PFL) claims. This turned out to be a blessing, as the application process was quite cumbersome and confusing.
 
-2. Be supportive of your pregnant employees: Creating a baby is hard! The more the pregnancy progresses, the bigger toll it will take on your employee. Have a supportive environment in which your employee feels safe sharing their needs and struggles. Offer to adapt their workload/focus accordingly.
+2. Be supportive of your pregnant employees: Creating a baby is hard! The more the pregnancy progresses, the bigger toll it will take on your employee. Have a supportive environment in which your employee feels safe sharing their needs and struggles, especially after you welcome them back from maternity leave. Offer to adapt their workload/focus accordingly.
 
 3. Get necessary props: There are numerous props that can make pregnancy way more comfortable for your employee and help them maintain productivity. E.g.: A standing desk with foot pad helps against back pain. An ergonomic mouse will prevent carpal tunnel (a common issue during pregnancy), etc.
 
 4. Offer prenatal benefits: Prenatal yoga/aquatics class are often only offered around noon/early afternoon. Let your employee go to them and have benefits to pay for these classes. It’s a win-win: Your employee will have a healthier pregnancy, experience less issues, stay productive and motivated.
 
 5. Your employee has the right to take up to 4 weeks pregnancy related disability leave before the due date in California. Make sure they feel safe enough to take this leave without worrying about their job/position/career development. The last pregnancy month is the hardest.
 
-6. Respect your employee’s wish to work until they feel ready to take their leave. I was able and wanting to work up to 3 days before giving birth due to an “easy” pregnancy with no complications. I’m glad I got to work so long, though I know other moms-to-be need the time off due to more difficult pregnancies. It was great that my team was supportive of my decision, didn't make me feel uncomfortable or was judgmental about my choice. Every pregnancy is different.
+6. Respect your employee’s wish to work until they feel ready to take their leave. I was able and wanting to work up to 3 days before giving birth due to an “easy” pregnancy with no complications. I’m glad I got to work so long, though I know other moms-to-be need the time off due to more difficult pregnancies. It was great that my team was supportive of my decision, didn't make me feel uncomfortable or was judgmental about my choice. Every pregnancy is different and every welcome back from maternity leave should be, too.
 
 7. After birth: A no-brainer, but FYI: Your employee just created a little miracle (or maybe even more than one)! Rejoice and welcome the new life with a thoughtful gift that will help the new parents: baby clothes/props are great and also something nice for the new mama like a beautiful flower bouquet**!
 
@@ -34,7 +37,7 @@ Today was my first day back to work at [Sourcegraph](https://sourcegraph.com) af
 
 10. Prepare the lactation room: Ask your employee what they need to make pumping at work as efficient and comfortable as possible, e.g.: a hospital grade pump or/and a hands free willow pump, a freezer to store the milk longer, a baby bottle cooler, a comfy chair etc.
 
-11. Once the employee goes back to work, plan together how the first weeks will look like to help their transition back to the original workflow. Temporary part time work or 4 days work week can help adding back the full time work to the new full time parent situation.
+11. Once you welcome the employee back from maternity leave and they go back to work, plan together how the first weeks will look like to help their transition back to the original workflow. Temporary part time work or 4 days work week can help adding back the full time work to the new full time parent situation.
 
 12. Encourage them to block time in their calendar for pumping sessions. Not pumping enough at work can lead to painful mastitis, engorgement and a significant drop of their breast milk production, so things you don’t want your employee to be worrying about while working.
 
@@ -51,3 +54,10 @@ _\*\*Ask the new parents beforehand if they are ok with fresh flowers, as some p
 ---
 
 _PS: We are [hiring](https://boards.greenhouse.io/sourcegraph91)!_
+
+---
+
+### More posts like this
+- [Let's talk about release anxiety](blog/release-anxiety)
+- [How we built our software engineering career framework](/blog/software-engineer-career-ladder)
+- [Async, remote, and flexible: How 7 engineers rethought their work calendars](/blog/remote-work-calendar)

content/blogposts/2021/continuous_delivery.md

@@ -131,7 +131,7 @@ One mental model through which you can look at this is one that both [GitLab](ht
 
 Releases should be a true snapshot of your current work. Shift from “Will X be merged?” to “Is X merged?” As Jez Humble, SRE at Google, [tweeted](https://twitter.com/jezhumble/status/1448318922713821186?s=21), continuous delivery is not about “taking whatever crap you have in version control & shipping it into prod as fast as possible so you can test in prod” but is about “making it SAFE to ship your code into prod quickly.”
 
-<blockquote className="twitter-tweet tw-align-center"><p lang="en" dir="ltr">It’s come to my attention that many people think continuous delivery/deployment is about taking whatever crap you have in version control &amp; shipping it into prod as fast as possible so you can test in prod<br></br>NO<br></br>CD is about making it SAFE to ship your code into prod quickly by:</p>&mdash; Jez Humble (@jezhumble) <a href="https://twitter.com/jezhumble/status/1448318922713821186?ref_src=twsrc%5Etfw">October 13, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charSet="utf-8"></script>
+<blockquote className="twitter-tweet tw-align-center"><p lang="en" dir="ltr">It’s come to my attention that many people think continuous delivery/deployment is about taking whatever crap you have in version control &amp; shipping it into prod as fast as possible so you can test in prod<br />NO<br />CD is about making it SAFE to ship your code into prod quickly by:</p>&mdash; Jez Humble (@jezhumble) <a href="https://twitter.com/jezhumble/status/1448318922713821186?ref_src=twsrc%5Etfw">October 13, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charSet="utf-8"></script>
 
 Your ultimate metric of success won’t be a poll of emotions among your teammates but will be how often your customers upgrade. An uneventful release for you is one that’s uneventful for your customers, too. If your customers are regularly upgrading and consistently keeping up with new releases, then you can trust you’ve reached a point where your releases are uneventful.
 

content/blogposts/2021/how-to-not-break-a-search-engine-or-what-i-learned-about-unglamorous-engineering.md

@@ -8,12 +8,12 @@ authorUrl: https://twitter.com/rvtond
 publishDate: 2021-06-25T10:00-07:00
 tags: [blog, code, search, software, engineering, testing]
 slug: how-not-to-break-a-search-engine-unglamorous-engineering
-heroImage: https://sourcegraphstatic.com/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg
-socialImage: https://sourcegraphstatic.com/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg
+heroImage: https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-new.png
+socialImage: https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-new.png
 published: true
 ---
 
-![Unglamorous engineering](https://sourcegraphstatic.com/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg)
+![Unglamorous engineering](https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-new.png)
 
 > _"In 2020 I flipped the switch to use a completely rewritten parser for
 > Sourcegraph search queries. It serves tens of thousands of users and processes
@@ -26,7 +26,7 @@ Sourcegraph—the bit that users type into the search bar. This component
 processes every single input that goes into the search bar when users search
 for code:
 
-<img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/search-bar.png" style={{width: '660px'}} alt="Code search input bar"/>
+<img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/search-bar.png" style={{width: '660px'}} alt="Code search input bar" />
 
 When the switch activated the new parser in September 2020, you'd never know
 that anything had changed. This is an account of the invisible, rigorous
@@ -87,7 +87,7 @@ defense for testing correctness. I reused some of our existing parser tests
 lot of additional tests for new parts of the syntax. You bet there's test
 coverage.
 
-<img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/parser-coverage.png" style={{width: '300px'}} alt="Parser file unit test coverage"/>
+<img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/parser-coverage.png" style={{width: '300px'}} alt="Parser file unit test coverage" />
 
 ### Part 2: Integration testing
 
@@ -100,16 +100,11 @@ representation. I'd abstracted out a common interface for our backend to access
 the new data structure under the feature-flagged code path to test on.
 
 <figure style={{width: '800px', maxWidth: '100%', margin: 'auto'}}>
-  <img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/integration.png" alt="Integration testing diagram" style={{boxShadow:'none'}} />
-  <i><small>Integration testing abstracts a common interface for our backend
-  to access query values.
-  We test that the backend produces the same search results for
-  simple queries (ones that don't have, e.g., </small></i>
-  <code>or</code>
-  <i>-operators), irrespective of whether those values originate from the existing parser's output or the new one.</i>
+  <img src="https://storage.googleapis.com/sourcegraph-assets/about.sourcegraph.com/blog/2021/integration.png" alt="Integration testing diagram" style={{boxShadow: 'none'}} />
+  <small><i>Integration testing abstracts a common interface for our backend to access query values. We test that the backend produces the same search results for simple queries (ones that don't have, e.g., <code>or</code> -operators), irrespective of whether those values originate from the existing parser's output or the new one.</i></small>
 </figure>
 
-<br/>
+<br />
 
 When I got to this part, we didn't have a good way to run integration tests. We
 had browser-based end-to-end testing that was onerous to set up, time-consuming
@@ -206,7 +201,7 @@ There's unglamorous engineering in the software all around us. For all its lack
 of recognition, I wish we grasped its value a bit better. I'm reminded of a
 tweet by a former colleague who researched donations for open source projects:
 
-<blockquote className="twitter-tweet tw-align-center" data-conversation="none"><p lang="en" dir="ltr">I can tell you from some informal interviews we did outside that paper, that people spend the money on gruntwork — the stuff that’s fun they’re more likely to do anyway, money or not.</p>&mdash; Bogdan Vasilescu (@b_vasilescu) <a href="https://twitter.com/b_vasilescu/status/1279199236094132227?ref_src=twsrc%5Etfw">July 3, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charSet="utf-8"></script>
+<blockquote className="twitter-tweet tw-align-center" data-conversation="none"><p lang="en" dir="ltr">I can tell you from some informal interviews we did outside that paper, that people spend the money on gruntwork — the stuff that’s fun they’re more likely to do anyway, money or not.</p>&mdash; Bogdan Vasilescu (@b_vasilescu) <a href="https://twitter.com/b_vasilescu/status/1279199236094132227?ref_src=twsrc%5Etfw">July 3, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 
 This suggests that gruntwork, if not glamorous, is certainly valuable (and
 perhaps, even disproportionately so). At the same time, I wouldn't necessarily
@@ -260,7 +255,7 @@ other engineers at Sourcegraph doing momentous but unglamorous things that most
 of the organization is blissfully unaware of. And the Twitterverse suggests
 there's more of it happening in software all around us:
 
-<blockquote className="twitter-tweet tw-align-center"><p lang="en" dir="ltr">A huge problem in software companies is that large new features get praise, promotions, accolades... while migrating off a legacy system, increasing performance 2,4,10X, or reducing error rates, pages, or alerts by X% is often only recognized by peers and not leadership.</p>&mdash; Dan Mayer (@danmayer) <a href="https://twitter.com/danmayer/status/1395564252308541440?ref_src=twsrc%5Etfw">May 21, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charSet="utf-8"></script>
+<blockquote className="twitter-tweet tw-align-center"><p lang="en" dir="ltr">A huge problem in software companies is that large new features get praise, promotions, accolades... while migrating off a legacy system, increasing performance 2,4,10X, or reducing error rates, pages, or alerts by X% is often only recognized by peers and not leadership.</p>&mdash; Dan Mayer (@danmayer) <a href="https://twitter.com/danmayer/status/1395564252308541440?ref_src=twsrc%5Etfw">May 21, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 
 I empathize with the engineers who don't have an audience for their unglamorous
 work, who want to say, "I did A Thing, there's nothing to see, but more people

content/blogposts/2021/integration-testing.md

@@ -7,12 +7,15 @@ author: Joe Chen
 publishDate: 2022-01-13T18:00+02:00
 tags: [blog]
 slug: integration-testing
-heroImage: https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg
-socialImage: https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg
+heroImage: https://storage.googleapis.com/sourcegraph-assets/blog/backend-integration-testing/backend-integration-testing.png
+socialImage: https://storage.googleapis.com/sourcegraph-assets/blog/backend-integration-testing/backend-integration-testing.png
 published: true
 ---
 
-![Unglamorous engineering graphic](https://storage.googleapis.com/sourcegraph-assets/blog/how-not-to-break-a-search-engine-unglamorous-engineering.jpg)
+<video loop autoplay muted playsinline>
+  <source src="https://storage.googleapis.com/sourcegraph-assets/blog/backend-integration-testing/backend-integration-testing.webm" type="video/webm" />
+  <source src="https://storage.googleapis.com/sourcegraph-assets/blog/backend-integration-testing/backend-integration-testing.mp4" type="video/mp4" />
+</video>
 
 My name is Joe Chen and I was on the Core Application team at Sourcegraph (before it split into Repo Management and Cloud SaaS––I'm on the latter at the time of writing). Our responsibility was to build and maintain the infrastructure of the Sourcegraph application for other teams. Some of our previous work includes licensing enforcement, background permissions syncing, and explicit permissions APIs.