Skip to content

Commit 3baedf5

Browse files
committed
Fix some alt image tags
1 parent 940b4a7 commit 3baedf5

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

_posts/articles/2017-04-15-balsamiq-case-study-part-3.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ The last challenge is one that I had wanted to do for the first release of our n
2626

2727
Let's look at the [Dropbox help site home page](https://www.dropbox.com/help) as an example:
2828

29-
![](https://media.balsamiq.com/images/docslikecode/dropbox-help.png)
29+
![Dropbox help example](https://media.balsamiq.com/images/docslikecode/dropbox-help.png)
3030

3131
I love the illustrations and layout. Very appealing and inviting. But as soon as you go a level deeper you get this:
3232

33-
![](https://media.balsamiq.com/images/docslikecode/dropbox-help-toc.png)
33+
![Dropbox Table of Contents](https://media.balsamiq.com/images/docslikecode/dropbox-help-toc.png)
3434

3535
A big ol' list of links. A wall of text. It's a very different feel from the page you came from.
3636

@@ -40,13 +40,13 @@ They're limited because they don't know how many articles there will be in each
4040

4141
And this is exactly what we do on our documentation site within each product category currently:
4242

43-
![]({{ site.url }}/images/balsamiq/desktop-toc-old.png)
43+
![Previous Balsamiq Table of Contents]({{ site.url }}/images/balsamiq/desktop-toc-old.png)
4444

4545
But I really love the look of hard-coded landing pages like the Dropbox site. The illustrations, the grid layout, the way it directs you to the information that's most important. I wanted to see if we could make our second-level pages look more like that.
4646

4747
To cut to the chase, here's what the upcoming version of our docs site will look like:
4848

49-
![]({{ site.url }}/images/balsamiq/desktop-toc.png)
49+
![New Balsamiq Table of Contents]({{ site.url }}/images/balsamiq/desktop-toc.png)
5050

5151
It feels more like a documentation site landing page, right? It has a featured articles section with the articles that are most relevant to new users, and the rest of the articles are split evenly in three columns. Yet none of it is hard-coded, even the featured "Getting Started" articles.
5252

@@ -99,7 +99,7 @@ The variable called `$featuredRows` helps determine where the count should start
9999

100100
And now to that "Getting Started" section at the top...
101101

102-
![]({{ site.url }}/images/balsamiq/desktop-toc-getting-started.png)
102+
![Getting Started Section]({{ site.url }}/images/balsamiq/desktop-toc-getting-started.png)
103103

104104
I wanted different images for each of the featured articles, but I just didn't like the idea of hard-coding any links or resources, in case we decided to change things later (and also because I'm stubborn). So, the top part of the code identifies the first three articles (ordered by weight), lists their names, links them up, and then grabs an image for each of them using the following code:
105105

0 commit comments

Comments
 (0)