Fix static references for images #29

jamescooke · Feb 13, 2022 · 3a62ea3 · 3a62ea3
1 parent 6d02377
commit 3a62ea3
Show file tree

Hide file tree

Showing 6 changed files with 14 additions and 14 deletions.
diff --git a/content/1301-tumbleweed-mako-question.rst b/content/1301-tumbleweed-mako-question.rst
@@ -18,7 +18,7 @@ bad smell? Is there something bad I don't know about this tech? Even worse is
 when you look around those quiet forums (or tags in Stack Overflow) you find
 comments like this about the library you're being asked to use:
 
-.. image:: |filename|/images/mako.png
+.. image:: |static|/images/mako.png
     :alt: Screenshot of comment on StackOverflow. Comment reads: "Suggestion:
           Don't use Mako. It's horrible. [...]"
 

diff --git a/content/1303-django-1.5-migration.rst b/content/1303-django-1.5-migration.rst
@@ -29,7 +29,7 @@ wanted to update their templates to the new syntax.
 Here's the warning from the `URL tag documentation
 <https://docs.djangoproject.com/en/1.5/ref/templates/builtins/#std:templatetag-url>`_.
 
-.. image:: |filename|/images/url-warning.png
+.. image:: |static|/images/url-warning.png
     :alt: Screenshot of warning from Django documentation. Warning reads:
           "Don't forget to put quotes around the function path or pattern name!
 

diff --git a/content/1311-git-squash.rst b/content/1311-git-squash.rst
@@ -29,7 +29,7 @@ And I jumped straight in with...
 
 Then, as part of our following conversation, I drew a picture:
 
-.. image:: |filename|/images/git.jpg
+.. image:: |static|/images/git.jpg
     :alt: Git squashing, feature versus history
 
 ..

diff --git a/content/1610-factory-audit.rst b/content/1610-factory-audit.rst
@@ -26,7 +26,7 @@ reaches the database.
 This is the way that I've been looking at Django model instances - for a single
 model we can imagine sets of instances which might look like:
 
-.. image:: |filename|/images/venn.png
+.. image:: |static|/images/venn.png
     :alt: Venn diagram showing sets of Django model instances grouped by
         validity.
     :width: 500
@@ -442,11 +442,11 @@ Happy fabricating!
     
     Brandon Rhodes, Pycon UK 2016
 
-.. |red_circle| image:: |filename|/images/red_circle.png
+.. |red_circle| image:: |static|/images/red_circle.png
     :width: 25
 
-.. |yellow_heart| image:: |filename|/images/yellow_heart.png
+.. |yellow_heart| image:: |static|/images/yellow_heart.png
     :width: 25
 
-.. |green_heart| image:: |filename|/images/green_heart.png
+.. |green_heart| image:: |static|/images/green_heart.png
     :width: 25
diff --git a/content/2004-github-travis.rst b/content/2004-github-travis.rst
@@ -21,7 +21,7 @@ vulnerability found in the development dependencies of one of my FOSS projects.
 This was a bump to Mozilla's `bleach <https://github.com/mozilla/bleach>`_, a
 project that GitHub states is used by more than 61,000 other projects.
 
-.. image:: |filename| images/200402_pr.png
+.. image:: |static| images/200402_pr.png
     :alt: GitHub's Dependabot opened a PR to bump bleach in Flake8-AAA.
     :target: https://github.com/jamescooke/flake8-aaa/pull/138
 
@@ -39,7 +39,7 @@ Unreported build status
 However, when I checked on the Dependabot Pull Request, GitHub was still
 waiting for the status of its Travis build to be reported.
 
-.. image:: |filename|/images/200401_some_checks_havent_completed_yet.png
+.. image:: |static|/images/200401_some_checks_havent_completed_yet.png
     :alt: GitHub's merge dialogue box showing that expected tests have not
         completed.
 
@@ -53,7 +53,7 @@ the call from Travis to GitHub to report the build status on the commit failed
 for some reason.
 
 
-.. image:: |filename|/images/200402_green_build.png
+.. image:: |static|/images/200402_green_build.png
     :alt: Travis build of the Dependabot PR is green.
 
 
@@ -79,7 +79,7 @@ Next, while checking the `GitHub status page <https://www.githubstatus.com/>`_
 and `Travis status page <https://www.traviscistatus.com/>`_, I found this
 status update on the Travis site:
 
-.. image:: |filename| images/200402_travis_status.png
+.. image:: |static| images/200402_travis_status.png
     :alt: Travis status page shows GitHub commit status issue: GitHub status
         may not be posted on commits occasionally from builds using the legacy
         Services integration.

diff --git a/content/2004-travis-migration.rst b/content/2004-travis-migration.rst
@@ -37,7 +37,7 @@ is pretty comprehensive, but watch out for these gotchas:
 * Make sure you "Sign up for the beta" of migration in `your Travis dot org
   account <https://travis-ci.org/account/repositories>`_.
 
-  .. image:: |filename| images/200424_travis_sign_up.png
+  .. image:: |static| images/200424_travis_sign_up.png
       :alt: Travis "Sign up for beta" call to action
 
   Without this your existing repositories will not appear in your new Travis
@@ -46,7 +46,7 @@ is pretty comprehensive, but watch out for these gotchas:
 * If you have required checks in the branch protection rules of your GitHub
   project repository, these need to be switched over.
 
-  .. image:: |filename| images/200424_branch_status_checks.png
+  .. image:: |static| images/200424_branch_status_checks.png
       :alt: GitHub branch status checks required
 
   You will need to trigger a build on Travis dot com for these new checks to
@@ -66,7 +66,7 @@ you straight to Travis dot org.
 
 Here's how GitHub advertises this benefit:
 
-.. image:: |filename| images/200424_travis_checks_integration.png
+.. image:: |static| images/200424_travis_checks_integration.png
     :alt: Integrations built with Checks API - Travis CI - Get a complete
         picture of a project’s health directly from GitHub by viewing your
         build's stages, jobs, and results, including the config associated with