Skip to content

Commit 23c48de

Browse files
committed
Fix yaml and image references
1 parent 74b5cfd commit 23c48de

3 files changed

Lines changed: 7 additions & 8 deletions

File tree

.ruby-version

Lines changed: 0 additions & 1 deletion
This file was deleted.

_data/authors.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,6 @@ ben_mansheim:
5959
gary_niemen:
6060
name: Gary Niemen
6161
picture: https://docslikecode.com/images/gary-niemen.png
62-
github: //github.com/garyniemen
63-
twitter:
64-
bio: "Product Manager for TechDocs, a docs-like-code solution at Spotify"
62+
github: //github.com/garyniemen
63+
twitter:
64+
bio: "Product Manager for TechDocs, a docs-like-code solution at Spotify"

_posts/articles/2020-11-06-ten-tips-maintaining-long-term-docs-like-code.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ categories: articles
77
author: gary_niemen
88
tags: [cicd, backstage, spotify, github, git, portal, internal, documentation, developer, docs]
99
image:
10-
path: /images/soundboard-han.ailes.jpg
10+
path: /images/spotify/soundboard-han.ailes.jpg
1111
caption: "[Flickr han.ailes](https://flic.kr/p/oVPTVm)"
1212
comments: false
1313
share: true
@@ -19,17 +19,17 @@ I remember about two years ago sitting here watching a Write the Docs video. Wel
1919

2020
I remember seeing this adoption curve and saying to myself: We need to do this. I want that curve.
2121

22-
![image](/images/adoption1.png)
22+
![image](/images/spotify/adoption1.png)
2323

2424
And just a few months later, we had built and released TechDocs, Spotify’s docs-like-code solution for internal technical documentation. And a few months after that, we had the curve that I had longed for. Nice gradient, eh?
2525

26-
![image](/images/adoption2.png)
26+
![image](/images/spotify/adoption2.png)
2727

2828
We were fortunate in that there were several synchronous moments that helped us, but overall, we moved fast because we were able to make use of preexisting infrastructure, such as [Backstage](https://backstage.io/) (our homegrown and now open sourced developer portal) and Tingle, Spotify’s CI/CD tool. We also made use of the open source static site generator, [MkDocs](https://www.mkdocs.org/).
2929

3030
In just two short years, writing docs in Markdown in our enterprise version of GitHub has become standard practice. We have over 3,000 doc sites from across the organisation, all showing up and searchable in Backstage. And most of the feedback we get from engineers is positive with the odd request for a small tweak or improvement.
3131

32-
![image](/images/techdocs.png)
32+
![image](/images/spotify/techdocs.png)
3333

3434
Time to put our feet up, right?
3535

0 commit comments

Comments
 (0)