Use relative urls for images and links to other posts.

posts/2015-02-20-Rust-1.0-alpha2.md

@@ -8,7 +8,7 @@ description: "Rust 1.0.0.alpha.2 has been released."
 Today, we are happy to announce the release of Rust 1.0.0.alpha.2! Rust is a
 systems programming language pursuing the trifecta: safe, fast, and concurrent.
 
-In accordance with our [status report](/2015/02/13/Final-1.0-timeline.html)
+In accordance with our [status report](../../../2015/02/13/Final-1.0-timeline.html)
 last week, this is a second alpha release, rather than a first beta release.
 The beta release will be six weeks from today, with the final coming six weeks
 after that.
@@ -17,7 +17,7 @@ We’ve managed to land almost all of the features previously expected for this
 cycle. **The big headline here is that all major API revisions are finished**:
 path and IO reform have landed. At this point, all modules shipping for 1.0 are
 in what we expect to be their final form, modulo minor tweaks during the alpha2
-cycle. See the [previous post](/2015/02/13/Final-1.0-timeline.html) for more
+cycle. See the [previous post](../../../2015/02/13/Final-1.0-timeline.html) for more
 details.
 
 This coming release cycle is crucial to Rust, as this will be the last cycle

posts/2016-04-19-MIR.md

@@ -606,14 +606,14 @@ interested in contributing, look for
 [nagisa]: https://github.com/nagisa/
 [eddyb]: https://github.com/eddyb/
 
-[cfg-img]: /images/2016-04-MIR/cfg.svg
-[drop-unwind]: /images/2016-04-MIR/drop-unwind.svg
-[drop]: /images/2016-04-MIR/drop.svg
-[flow]: /images/2016-04-MIR/flow.svg
-[loop-break]: /images/2016-04-MIR/loop-break.svg
-[nzd-flags]: /images/2016-04-MIR/nzd-flags.svg
-[nzd]: /images/2016-04-MIR/nzd.svg
-[send_if2-flags]: /images/2016-04-MIR/send_if2-flags.svg
-[send_if2-opt]: /images/2016-04-MIR/send_if2-opt.svg
-[send_if2]: /images/2016-04-MIR/send_if2.svg
+[cfg-img]: ../../../images/2016-04-MIR/cfg.svg
+[drop-unwind]: ../../../images/2016-04-MIR/drop-unwind.svg
+[drop]: ../../../images/2016-04-MIR/drop.svg
+[flow]: ../../../images/2016-04-MIR/flow.svg
+[loop-break]: ../../../images/2016-04-MIR/loop-break.svg
+[nzd-flags]: ../../../images/2016-04-MIR/nzd-flags.svg
+[nzd]: ../../../images/2016-04-MIR/nzd.svg
+[send_if2-flags]: ../../../images/2016-04-MIR/send_if2-flags.svg
+[send_if2-opt]: ../../../images/2016-04-MIR/send_if2-opt.svg
+[send_if2]: ../../../images/2016-04-MIR/send_if2.svg
 [alt]: https://github.com/rust-lang/rfcs/blob/master/text/1211-mir.md#alternatives

posts/2016-05-16-rust-at-one-year.md

@@ -20,7 +20,7 @@ having fun doing it.
 
 And yesterday, Rust turned one year old.
 
-<img src="/images/2016-05-16-rust-at-one-year/cupcakes.jpg" height="300px" width="300px">
+<img src="../../../images/2016-05-16-rust-at-one-year/cupcakes.jpg" height="300px" width="300px">
 
 ### Rust in numbers
 

posts/2016-06-30-State-of-Rust-Survey-2016.md

@@ -159,17 +159,17 @@ And we couldn't agree more.  One of the best things about working in Rust is tha
 We'd love to hear your comments and invite you to jump in and participate in the upcoming discussions on ways we can tackle the challenges brought up in this survey.
 
 
-[do-you-use-rust]: /images/2016-06-Survey/do_you_use_rust.png
-[time-using-rust]: /images/2016-06-Survey/time_using_rust.png
-[versions-of-rust]: /images/2016-06-Survey/versions_of_rust.png
-[after_1_0_broke_code]: /images/2016-06-Survey/after_1_0_broke_code.png
-[easy_to_fix]: /images/2016-06-Survey/easy_to_fix.png
-[like_cargo]: /images/2016-06-Survey/like_cargo.png
-[rust_at_work]: /images/2016-06-Survey/rust_at_work.png
-[part_time]: /images/2016-06-Survey/part_time.png
-[full_time]: /images/2016-06-Survey/full_time.png
-[rust_at_work_future]: /images/2016-06-Survey/rust_at_work_future.png
-[demo_areas]: /images/2016-06-Survey/demo_areas.png
-[meetup_locations]: /images/2016-06-Survey/meetup_locations.png
-[what_languages]: /images/2016-06-Survey/what_language.png
-[underrepresented]: /images/2016-06-Survey/underrepresented.png
+[do-you-use-rust]: ../../../images/2016-06-Survey/do_you_use_rust.png
+[time-using-rust]: ../../../images/2016-06-Survey/time_using_rust.png
+[versions-of-rust]: ../../../images/2016-06-Survey/versions_of_rust.png
+[after_1_0_broke_code]: ../../../images/2016-06-Survey/after_1_0_broke_code.png
+[easy_to_fix]: ../../../images/2016-06-Survey/easy_to_fix.png
+[like_cargo]: ../../../images/2016-06-Survey/like_cargo.png
+[rust_at_work]: ../../../images/2016-06-Survey/rust_at_work.png
+[part_time]: ../../../images/2016-06-Survey/part_time.png
+[full_time]: ../../../images/2016-06-Survey/full_time.png
+[rust_at_work_future]: ../../../images/2016-06-Survey/rust_at_work_future.png
+[demo_areas]: ../../../images/2016-06-Survey/demo_areas.png
+[meetup_locations]: ../../../images/2016-06-Survey/meetup_locations.png
+[what_languages]: ../../../images/2016-06-Survey/what_language.png
+[underrepresented]: ../../../images/2016-06-Survey/underrepresented.png

posts/2016-08-10-Shape-of-errors-to-come.md

@@ -31,7 +31,7 @@ The problem though is that it takes a few seconds to look at the message, orient
 the critical pieces. This time loss adds up. What if, instead, we cleared away everything that slows
 down how you read the error message?
 
-<img src="/images/2016-08-09-Errors/new_errors.png" width="500" />
+<img src="../../../images/2016-08-09-Errors/new_errors.png" width="500" />
 
 This is the new error format. It's designed around the fundamental observation that
 errors should **focus on the code you wrote**. By doing so, you can much more easily see the context
@@ -182,10 +182,10 @@ improve the learning curve bit by bit, and we're looking forward to seeing how f
 
 
 
-[old_errors]: /images/2016-08-09-Errors/old_errors.png
-[new_errors]: /images/2016-08-09-Errors/new_errors.png
-[new_errors2]: /images/2016-08-09-Errors/new_errors2.png
-[new_errors3]: /images/2016-08-09-Errors/new_errors3.png
-[new_errors4]: /images/2016-08-09-Errors/new_errors4.png
+[old_errors]: ../../../images/2016-08-09-Errors/old_errors.png
+[new_errors]: ../../../images/2016-08-09-Errors/new_errors.png
+[new_errors2]: ../../../images/2016-08-09-Errors/new_errors2.png
+[new_errors3]: ../../../images/2016-08-09-Errors/new_errors3.png
+[new_errors4]: ../../../images/2016-08-09-Errors/new_errors4.png
 [Dybuk]: https://github.com/ticki/dybuk
 [Elm]: https://elm-lang.org/blog/compiler-errors-for-humans

posts/2016-09-08-incremental.md

@@ -471,17 +471,17 @@ or ask around in the [#rustc channel on IRC][rustc-irc].
 [incr-comp-rfc]: https://github.com/rust-lang/rfcs/blob/master/text/1298-incremental-compilation.md
 [compiling]: https://xkcd.com/303/
 [up-to-or-more]: https://xkcd.com/870/
-[algebra-initial]: /images/2016-08-Incremental/algebra-initial.svg
-[algebra-update]: /images/2016-08-Incremental/algebra-update.svg
-[algebra-dep-graph]: /images/2016-08-Incremental/algebra-dep-graph.svg
-[algebra-dep-graph-dag]: /images/2016-08-Incremental/algebra-dep-graph-dag.svg
-[compiler-phases]: /images/2016-08-Incremental/compiler-phases.svg
-[compiler-dep-graph]: /images/2016-08-Incremental/compiler-dep-graph.svg
-[compiler-cache-purge]: /images/2016-08-Incremental/compiler-cache-purge.svg
-[compiler-phases-cost]: /images/2016-08-Incremental/compiler-phases-cost.svg
+[algebra-initial]: ../../../images/2016-08-Incremental/algebra-initial.svg
+[algebra-update]: ../../../images/2016-08-Incremental/algebra-update.svg
+[algebra-dep-graph]: ../../../images/2016-08-Incremental/algebra-dep-graph.svg
+[algebra-dep-graph-dag]: ../../../images/2016-08-Incremental/algebra-dep-graph-dag.svg
+[compiler-phases]: ../../../images/2016-08-Incremental/compiler-phases.svg
+[compiler-dep-graph]: ../../../images/2016-08-Incremental/compiler-dep-graph.svg
+[compiler-cache-purge]: ../../../images/2016-08-Incremental/compiler-cache-purge.svg
+[compiler-phases-cost]: ../../../images/2016-08-Incremental/compiler-phases-cost.svg
 [cargo-incremental]: https://github.com/nikomatsakis/cargo-incremental
-[performance-full-re-use]: /images/2016-08-Incremental/perf-full-re-use.svg
-[performance-changes]: /images/2016-08-Incremental/perf-changes.svg
+[performance-full-re-use]: ../../../images/2016-08-Incremental/perf-full-re-use.svg
+[performance-changes]: ../../../images/2016-08-Incremental/perf-changes.svg
 [regex]: https://github.com/rust-lang-nursery/regex
 [futures]: https://github.com/alexcrichton/futures-rs
 [syntex]: https://github.com/serde-rs/syntex/tree/master/syntex_syntax

posts/2016-09-29-Rust-1.12.md

@@ -29,7 +29,7 @@ a result of the effort of many hours of [volunteer effort] to design, test, and
 update every one of `rustc`s errors to the new format. We're excited to see
 what you think of them:
 
-![A new borrow-check error](/images/2016-09-Rust-1.12/borrowck-error.png)
+![A new borrow-check error](../../../images/2016-09-Rust-1.12/borrowck-error.png)
 
 The largest internal change in this release is moving to a new compiler backend
 based on the new Rust [MIR]. While this feature does not result in anything
@@ -52,15 +52,15 @@ For example, in 1.11 if a implementation of a trait didn't match the trait
 declaration, you would see an error like the one below:
 
 ![An old mismatched trait
-error](/images/2016-09-Rust-1.12/old-mismatched-trait-error.png)
+error](../../../images/2016-09-Rust-1.12/old-mismatched-trait-error.png)
 
 In the new error format we represent the error by instead showing the points in
 the code that matter the most. Here is the relevant line in the trait
 declaration, and the relevant line in the implementation, using labels to
 describe why they don't match:
 
 ![A new mismatched trait
-error](/images/2016-09-Rust-1.12/mismatched-trait-error.png)
+error](../../../images/2016-09-Rust-1.12/mismatched-trait-error.png)
 
 Initially, this error design was built to aid in understanding borrow-checking
 errors, but we found, as with the error above, the format can be broadly

posts/2016-11-10-Rust-1.13.md

@@ -178,7 +178,7 @@ appear to be some big reductions, which are quantified on the corresponding
 
 <br/>
 
-![Performance graph](/images/2016-11-Rust-1.13/graph.png)
+![Performance graph](../../../images/2016-11-Rust-1.13/graph.png)
 
 <br/>
 

posts/2017-05-15-rust-at-two-years.md

@@ -15,7 +15,7 @@ It's been two years since Rust 1.0 was released. Happy second birthday, Rust!
 
 *Rustaceans at RustFest Berlin, September 2016. Picture by Fiona Castiñeira*
 
-[group-pic]: /images/2017-05-Second-Birthday/rustfest-berlin.jpeg
+[group-pic]: ../../../images/2017-05-Second-Birthday/rustfest-berlin.jpeg
 
 Over these two years, we have demonstrated stability without stagnation,
 maintaining backwards compatibility with version 1.0 while also making many
@@ -240,7 +240,7 @@ Try out incremental compilation on nightly Rust with
 
 [incrcomp]: https://internals.rust-lang.org/t/incremental-compilation-beta/4721
 [roadmap-4]: https://github.com/rust-lang/rust-roadmap/issues/4
-[incrcomp-svg]: /images/2017-05-Second-Birthday/incremental-compilation.svg
+[incrcomp-svg]: ../../../images/2017-05-Second-Birthday/incremental-compilation.svg
 
 We've also made some progress on the time it takes to do a full compilation. On
 average, compile times have improved by 5-10% in the last year, but some

posts/2017-06-27-Increasing-Rusts-Reach.md

@@ -4,7 +4,7 @@ title: "Increasing Rust’s Reach"
 author: Carol Nichols
 ---
 
-**EDIT: We've heard that Google Forms is not easily accessible in all countries; if that applies to you, please find the [application's questions in this text file](/images/2017-06-Increasing-Rusts-Reach/application.txt) and send the answers via email to carol.nichols@gmail.com.**
+**EDIT: We've heard that Google Forms is not easily accessible in all countries; if that applies to you, please find the [application's questions in this text file](../../../images/2017-06-Increasing-Rusts-Reach/application.txt) and send the answers via email to carol.nichols@gmail.com.**
 
 One of [Rust's 2017 goals](https://blog.rust-lang.org/2017/02/06/roadmap.html) is to make it easier
 to become productive in Rust by reducing its learning curve. We believe Rust has potential as an
@@ -84,15 +84,15 @@ Who should apply for this project:
 - Interest in improving usability of developer-facing documentation and tools
 - Interest in learning in detail about Rust syntax and semantics
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/nrc.jpg" alt="Nick Cameron" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/nrc.jpg" alt="Nick Cameron" class="right-thumbnail">
 
 *About Nick Cameron: I'm a Rust core team member and lead the dev-tools team. I work on a bunch of
 tools including Rustdoc, Rustfmt, the Rust Language Server, and the Rust compiler. I want to make
 Rust developer tools awesome, and user experience is a key part of that. I want Rust to change the
 world (or at least the programming world), and we can't do that without making the Rust language
 and community more accessible to more people.*
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/steveklabnik.jpeg" alt="Steve Klabnik" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/steveklabnik.jpeg" alt="Steve Klabnik" class="right-thumbnail">
 
 *About Steve Klabnik: I used to work on Ruby on Rails before Rust, and one of the reasons why I love
 Rust is that as a project, we're committed to helping people learn Rust as their first low-level
@@ -127,7 +127,7 @@ Who should apply for this project:
 - Interest in improving the new Rust developer experience
 - Interest in learning how to improve and create lints
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/manish.png" alt="Manish Goregaokar" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/manish.png" alt="Manish Goregaokar" class="right-thumbnail">
 
 *About Manish Goregaokar: I'm a research engineer at Mozilla working on Servo. I care a lot about
 improving workflows and tooling, especially around the newcomer experience.*
@@ -154,7 +154,7 @@ Who should apply for this project:
 - Interest in improving approachability of Rust
 - Interest in investigating the motivations behind visitors to the main website and/or crates.io
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/aturon.jpg" alt="Aaron Turon" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/aturon.jpg" alt="Aaron Turon" class="right-thumbnail">
 
 *About Aaron Turon: I'm a Rust core team member, manage the Mozilla Rust team, and currently lead
 the library, infrastructure, and Cargo teams. On the technical side, I'm most driven by language
@@ -181,7 +181,7 @@ Who should apply for this project:
 - Background or interest in creating visual teaching tools like diagrams or drawings a plus
 - Interest in learning Rust concepts and teaching what you learn to others
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/nmatsakis.jpeg" alt="Niko Matsakis" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/nmatsakis.jpeg" alt="Niko Matsakis" class="right-thumbnail">
 
 *About Niko Matsakis: I'm a member of the Rust core team as well as the Rust language and compiler
 teams. I focus mainly on the design and implementation of the language itself. I want to do what I
@@ -205,7 +205,7 @@ Who should apply for this project:
 - Experience using a web framework written in some other language
 - Interest in learning how to write web applications in Rust and teaching what you learn to others
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/sgrif.jpeg" alt="Sean Griffin" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/sgrif.jpeg" alt="Sean Griffin" class="right-thumbnail">
 
 *About Sean Griffin: In addition to my Rust work, I am one of the maintainers of Ruby on Rails. One
 of the great things about Rails (and web development) is that it has really helped to lower the
@@ -235,7 +235,7 @@ Who should apply for this project:
 - Background in writing, teaching, or documentation
 - Interest in, and opinions about, improving tools for creating and displaying code documentation
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/pnkfelix.jpeg" alt="Felix Klock" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/pnkfelix.jpeg" alt="Felix Klock" class="right-thumbnail">
 
 *About Felix Klock: I'm the main developer of tango (as well as a member of the Rust compiler and
 language teams). I actively use tango for authoring my presentation slides about Rust. I
@@ -267,7 +267,7 @@ Who should apply for this project:
 - Interest in learning how to translate an application to Rust
 - Interest in researching and documenting features that libraries have or don’t have
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/burntsushi.jpeg" alt="Andrew Gallant" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/burntsushi.jpeg" alt="Andrew Gallant" class="right-thumbnail">
 
 *About Andrew Gallant: I'm a member of the Rust library team that works with Rust in my free time. I
 am very interested in information retrieval, fast text search and generally improving Rust's
@@ -293,7 +293,7 @@ Who should apply for this project:
 - Interest in learning how to write or translate a CLI program to Rust
 - Interest in researching and documenting features that libraries have or don’t have
 
-<img src="/images/2017-06-Increasing-Rusts-Reach/kamalmarhubi.jpeg" alt="Kamal Marhubi" class="right-thumbnail">
+<img src="../../../images/2017-06-Increasing-Rusts-Reach/kamalmarhubi.jpeg" alt="Kamal Marhubi" class="right-thumbnail">
 
 *About Kamal Marhubi: I've been writing Rust for about a year and a half. I help maintain nix, a
 library that gives a Rusty interface to unix systems APIs. I've also contributed to rustfmt, rustup,