Fix file extensions as nothing they can only be found with the full path now

 - middleman is gone

Author: galund

Diff for: career-path/index.html.md

@@ -19,38 +19,38 @@ These competencies do not generally distinguish between developers, web operatio
 
 ### Working practices
 
-- [Building software as a team](working-practices/building-software-as-a-team.html)
-- [Knowing when to ask for help](working-practices/knowing-when-to-ask-for-help.html)
-- [Planning and estimating](working-practices/planning-and-estimating.html)
-- [Prioritising your time](working-practices/prioritising-your-time.html)
-- [Working independently](working-practices/working-independently.html)
-- [Working as a multi-disciplinary team](working-practices/working-as-a-multi-disciplinary-team.html)
-- [Owning your development plan](working-practices/owning-your-development-plan.html)
+- [Building software as a team](working-practices/building-software-as-a-team.html.md)
+- [Knowing when to ask for help](working-practices/knowing-when-to-ask-for-help.html.md)
+- [Planning and estimating](working-practices/planning-and-estimating.html.md)
+- [Prioritising your time](working-practices/prioritising-your-time.html.md)
+- [Working independently](working-practices/working-independently.html.md)
+- [Working as a multi-disciplinary team](working-practices/working-as-a-multi-disciplinary-team.html.md)
+- [Owning your development plan](working-practices/owning-your-development-plan.html.md)
 
 
 ### Technical skills
 
-- [Version control](technical-skills/version-control.html)
-- [Using a sytematic approach to solve problems](technical-skills/systematic-approach-solving-problems.html)
-- [Technical debt tradeoffs](technical-skills/technical-debt-tradeoffs.html)
-- [Diagnosing and debugging issues](technical-skills/diagnosing-and-debugging-issues.html)
-- [Using appropriate testing to ensure software quality](technical-skills/using-appropriate-testing-to-ensure-software-quality.html)
-- [Designing technical features](technical-skills/designing-technical-features.html)
-- [Designing and testing for accessibility](technical-skills/designing-and-testing-for-accessibility.html)
-- [Building secure services](technical-skills/building-secure-services.html)
-- [Assessing performance](technical-skills/assessing-performance.html)
-- [Designing for reliability](technical-skills/designing-for-reliability.html)
-- [Selecting technology](technical-skills/selecting-technology.html)
+- [Version control](technical-skills/version-control.html.md)
+- [Using a sytematic approach to solve problems](technical-skills/systematic-approach-solving-problems.html.md)
+- [Technical debt tradeoffs](technical-skills/technical-debt-tradeoffs.html.md)
+- [Diagnosing and debugging issues](technical-skills/diagnosing-and-debugging-issues.html.md)
+- [Using appropriate testing to ensure software quality](technical-skills/using-appropriate-testing-to-ensure-software-quality.html.md)
+- [Designing technical features](technical-skills/designing-technical-features.html.md)
+- [Designing and testing for accessibility](technical-skills/designing-and-testing-for-accessibility.html.md)
+- [Building secure services](technical-skills/building-secure-services.html.md)
+- [Assessing performance](technical-skills/assessing-performance.html.md)
+- [Designing for reliability](technical-skills/designing-for-reliability.html.md)
+- [Selecting technology](technical-skills/selecting-technology.html.md)
 
 
 ### Leading and communicating
-- [Leading on stories](leading-and-communicating/leading-on-stories.html)
-- [Wider context](leading-and-communicating/wider-context-of-work.html)
-- [Writing and speaking](leading-and-communicating/writing-and-speaking.html)
-- [Sharing knowledge with others](leading-and-communicating/sharing-knowledge-with-others.html)
-- [Awareness of wider community](leading-and-communicating/awareness-of-wider-community.html)
+- [Leading on stories](leading-and-communicating/leading-on-stories.html.md)
+- [Wider context](leading-and-communicating/wider-context-of-work.html.md)
+- [Writing and speaking](leading-and-communicating/writing-and-speaking.html.md)
+- [Sharing knowledge with others](leading-and-communicating/sharing-knowledge-with-others.html.md)
+- [Awareness of wider community](leading-and-communicating/awareness-of-wider-community.html.md)
 - Comunicating assumptions and getting clarification up front to minimise rework
-- [Pair programming](leading-and-communicating/pair-programming.html)
+- [Pair programming](leading-and-communicating/pair-programming.html.md)
 
 ### Adding a competency to this page
 ```

Diff for: career-path/leading-and-communicating/leading-on-stories.html.md

@@ -18,7 +18,7 @@ You should take responsibility for:
 
 ### Junior level
 
-At junior level, you will be given support to work on user stories. You will normally work in a pair with a more experienced developer. You may be asked to take the lead on well defined stories - [see an example](/resources/delivery/user-story-template.html).
+At junior level, you will be given support to work on user stories. You will normally work in a pair with a more experienced developer. You may be asked to take the lead on well defined stories - [see an example](/resources/delivery/user-story-template.html.md).
 
 A well defined story will:
 
@@ -43,7 +43,7 @@ This could involve:
 - working with the tech lead and the rest of the team to agree scope and identify risks to delivery early on
 - creating well defined stories for other developers to pick up or suggesting an approach to take
 - helping to resolve blockers
-- making sure code gets [code reviewed](/resources/other/code-reviews.html) quickly
+- making sure code gets [code reviewed](/resources/other/code-reviews.html.md) quickly
 - doing a timeboxed investigation (spike) into a problem area
 
 ## As a tech lead (any level)

Diff for: career-path/leading-and-communicating/sharing-knowledge-with-others.html.md

@@ -16,7 +16,7 @@ Much of what we’re doing is only possible because of open source code and the
 ## Your role as developer/webops
 You can share knowledge internally by
 
-- [Reviewing other developers' code](/resources/other/code-reviews.html)
+- [Reviewing other developers' code](/resources/other/code-reviews.html.md)
 - Documenting software you work with
 - Demonstrating work at Show and Tell events and within your team
 - Speaking at a monthly Technospective
@@ -39,7 +39,7 @@ You can also volunteer for the monthly Technospective to give a longer talk on a
 
 ### Mid level
 
-[Working together with other developers](/career-path/leading-and-communicating/pair-programming.html) is a really good way to share knowledge, since you get to see other developer's workflow, environment and editor/IDE config, and general approaches to problem solving.
+[Working together with other developers](/career-path/leading-and-communicating/pair-programming.html.md) is a really good way to share knowledge, since you get to see other developer's workflow, environment and editor/IDE config, and general approaches to problem solving.
 
 You should also regularly review other developers' pull requests. It's a good idea to check other work-in-progress before picking up new stories, so that code review doesn't become a bottleneck for the team. See the [How to review code](https://gds-way.cloudapps.digital/manuals/code-review-guidelines.html) on the GDS way website for guidance about how to do code reviews well.
 

Diff for: career-path/technical-skills/designing-for-reliability.html.md

@@ -11,15 +11,15 @@ title: Designing for reliability
 
 Writing code is a core part of software development, but our responsibility extends beyond that.
 
-As a developer you are responsible for the whole release process, from [code review](/resources/other/code-reviews.html) to
+As a developer you are responsible for the whole release process, from [code review](/resources/other/code-reviews.html.md) to
 deployment on a production system. You should also ensure that the products you are
 working on are easy to support and operate.
 
 ### Junior level
 
 Working with a more experienced developer, you should be able to produce code of a sufficient quality standard to ship to production.
 
-You should [use automated testing](/career-path/technical-skills/using-appropriate-testing-to-ensure-software-quality.html) to ensure your code works.
+You should [use automated testing](/career-path/technical-skills/using-appropriate-testing-to-ensure-software-quality.html.md) to ensure your code works.
 
 ### Mid level
 
@@ -44,4 +44,4 @@ At senior level, you should
 
 
 ## External resources
-- [Resources: Reliability engineering](/resources/systems/reliability-engineering.html)
+- [Resources: Reliability engineering](/resources/systems/reliability-engineering.html.md)

Diff for: career-path/technical-skills/version-control.html.md

@@ -20,7 +20,7 @@ Source code should be [open to the public and published under an open source lic
 
 ## What you should be able to do
 
-- Understand and follow your team’s branching and [code review](/resources/other/code-reviews.html) process
+- Understand and follow your team’s branching and [code review](/resources/other/code-reviews.html.md) process
 - Understand the benefits of having a clear commit history
 - Write clear commit messages for your changes
 

Diff for: career-path/working-practices/building-software-as-a-team.html.md

@@ -42,16 +42,16 @@ You should:
 
 Depending on the technology you're working with you may find the following resource lists helpful:
 
-- [Python](/resources/languages/python.html)
-- [Ruby](/resources/languages/ruby.html)
-- [Rails](/resources/frameworks/rails.html)
-- [Java](/resources/languages/java.html)
-- [Node.js](/resources/frameworks/nodejs.html)
+- [Python](/resources/languages/python.html.md)
+- [Ruby](/resources/languages/ruby.html.md)
+- [Rails](/resources/frameworks/rails.html.md)
+- [Java](/resources/languages/java.html.md)
+- [Node.js](/resources/frameworks/nodejs.html.md)
 
 ### Techniques
 
 - [Pair
-  programming](/career-path/leading-and-communicating/pair-programming.html)
-- [Giving and receiving feedback](/resources/other/giving-and-receiving-feedback.html)
-- [Structuring code](/resources/delivery/structuring-code.html)
-- [Documenting work](/resources/other/documentation.html)
+  programming](/career-path/leading-and-communicating/pair-programming.html.md)
+- [Giving and receiving feedback](/resources/other/giving-and-receiving-feedback.html.md)
+- [Structuring code](/resources/delivery/structuring-code.html.md)
+- [Documenting work](/resources/other/documentation.html.md)

Diff for: career-path/working-practices/knowing-when-to-ask-for-help.html.md

@@ -26,7 +26,7 @@ When asking questions, be sure to provide context about what you are trying to d
 
 ### Junior level
 
-You'll usually be given [well defined tasks](/career-path/leading-and-communicating/leading-on-stories.html#junior-level) to work on, with support from a more experienced developer. Discuss the work with your colleague and try to understand what's involved.
+You'll usually be given [well defined tasks](/career-path/leading-and-communicating/leading-on-stories.html.md#junior-level) to work on, with support from a more experienced developer. Discuss the work with your colleague and try to understand what's involved.
 
 The person you're working with will give you guidance and you can ask questions as you go along. There's no such thing as a stupid question, so don't be afraid to ask!
 

Diff for: contributing/index.html.md

@@ -11,7 +11,7 @@ Here are a few ways you can help:
 1. [Review open pull requests](https://github.com/alphagov/gds-tech-learning-pathway/pulls). You don't have to be an expert on the topic to make suggestions.
 2. Improve the copy so it's [easier to understand](https://www.gov.uk/guidance/content-design/writing-for-gov-uk).
 3. Write a resource list for a topic you're interested in
-4. Write a competency statement following the [template](template.html). Speak to someone before starting this as we have a list of competencies and what we think should go in them.
+4. Write a competency statement following the [template](template.html.md). Speak to someone before starting this as we have a list of competencies and what we think should go in them.
 4. Triage [issues](https://github.com/alphagov/gds-tech-learning-pathway/issues) and work out how they can be incorporated into the existing structure. This might be just adding a link to a resource list.
 5. Raise an issue for something that is currently missing from the learning pathway.
 

Diff for: resources/frameworks/rails.html.md

@@ -58,7 +58,7 @@ any arguments.
 
 ### Rails Test Frameworks
 
-See [Ruby test frameworks](/resources/languages/ruby.html)
+See [Ruby test frameworks](/resources/languages/ruby.html.md)
 
 ### Code style
 

Diff for: resources/languages/ruby.html.md

@@ -20,7 +20,7 @@ somewhat slow performing language [compared to others][ruby-go-comparison] -
 however Rubyists argue that [Ruby is fast enough][ruby-fast-enough].
 
 Ruby came to popularity with the rise in popularity of the
-[Ruby on Rails](/resources/frameworks/rails.html) web framework. Other popular Ruby projects are
+[Ruby on Rails](/resources/frameworks/rails.html.md) web framework. Other popular Ruby projects are
 [Sinatra](http://www.sinatrarb.com/), [Jekyll](https://jekyllrb.com/),
 [Puppet](https://puppet.com/), [Capistrano](http://capistranorb.com/) and
 [SASS](http://sass-lang.com/).

Diff for: ways-of-learning/index.html.md

@@ -48,7 +48,7 @@ Many skills are best developed through working on a project as part of a team.
 This can include:
 
 - building and supporting software
-- participating in [code reviews](/resources/other/code-reviews.html)
+- participating in [code reviews](/resources/other/code-reviews.html.md)
 - attending incident reviews
 - participating in show & tells
 - writing and speaking about your work externally