docs: fix broken links #110

alies-dev · alies-dev · commit f22c8bbd9d24 · 2026-05-27T12:33:42.000+02:00
diff --git a/development/library/back-end/conventions--laravel.md b/development/library/back-end/conventions--laravel.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [Laravel conventions](../../../library/backend/conventions--laravel).
+New URL is [Laravel conventions](../../../library/backend/conventions--laravel.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/development/library/back-end/conventions--sql.md b/development/library/back-end/conventions--sql.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [SQL conventions](../../../library/backend/conventions--sql).
+New URL is [SQL conventions](../../../library/backend/conventions--sql.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/development/library/front-end/conventions--css.md b/development/library/front-end/conventions--css.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [CSS conventions](../../../library/frontend/conventions--css).
+New URL is [CSS conventions](../../../library/frontend/conventions--css.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/development/library/front-end/conventions--js.md b/development/library/front-end/conventions--js.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [JS conventions](../../../library/frontend/conventions--js).
+New URL is [JS conventions](../../../library/frontend/conventions--js.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/development/library/front-end/conventions--jsdoc.md b/development/library/front-end/conventions--jsdoc.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [JSDoc conventions](../../../library/frontend/conventions--js).
+New URL is [JSDoc conventions](../../../library/frontend/conventions--jsdoc.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/development/library/front-end/conventions--vue.md b/development/library/front-end/conventions--vue.md
@@ -1,4 +1,4 @@
 The document is moved.
-New URL is [Vue conventions](../../../library/frontend/conventions--vuejs).
+New URL is [Vue conventions](../../../library/frontend/conventions--vuejs.md).
 
 Please report/fix a broken link on the external source — we’ll remove these stub/redirect pages soon.
diff --git a/guides/OKR/00-why-okrs.md b/guides/OKR/00-why-okrs.md
@@ -2,7 +2,7 @@
 
 ## WHAT are Objectives And Key Results (OKRs)?
 
-The OKR method is a popular strategy for setting and achieving goals within organizations. Like most organizations, we use [Cascading OKRs](./02-cascading-okrs), that allows us to align our vision, mission, values and strategy with day-to-day objectives, work and key results.
+The OKR method is a popular strategy for setting and achieving goals within organizations. Like most organizations, we use [Cascading OKRs](./02-cascading-okrs.md), that allows us to align our vision, mission, values and strategy with day-to-day objectives, work and key results.
 
 ![Diagram of OKR alignment](../../images/5-alignment.svg)
 
@@ -31,5 +31,5 @@ Note that in these examples the KPI's and tasks are combined. For example, in Ex
 
 ![](../../images/19-okr-pillars.svg)
 
-If you are still wondering, here are some more [benefits of OKRs](./00-benefits-of-okrs).
-Otherwise, if you are ready to start using OKRs at the IxDF, let's start with [our OKR cadence](./01-okr-cadence).
+If you are still wondering, here are some more [benefits of OKRs](./00-benefits-of-okrs.md).
+Otherwise, if you are ready to start using OKRs at the IxDF, let's start with [our OKR cadence](./01-okr-cadence.md).
diff --git a/guides/OKR/02-cascading-okrs.md b/guides/OKR/02-cascading-okrs.md
@@ -16,4 +16,4 @@ Here is what the process looks like over the course of a normal quarter.
 
 ![](../../images/26-okr-quarter-reference.svg)
 
-Now that you have seen how our OKRs work at the organizational level, it’s time to start [creating your OKR's](./03-create-your-okrs).
+Now that you have seen how our OKRs work at the organizational level, it’s time to start [creating your OKR's](./03-create-your-okrs.md).
diff --git a/guides/OKR/03-create-your-okrs.md b/guides/OKR/03-create-your-okrs.md
@@ -1,6 +1,6 @@
 # Create Your OKRs
 
-Once you know [about OKRs](./00-why-okrs), about the IxDF's [OKR cadence](./01-okr-cadence) and our [cascading OKR's](./02-cascading-okrs), you are ready to begin creating your own OKR's.
+Once you know [about OKRs](./00-why-okrs.md), about the IxDF's [OKR cadence](./01-okr-cadence.md) and our [cascading OKR's](./02-cascading-okrs.md), you are ready to begin creating your own OKR's.
 
 ## Familiarize yourself with the OKR Planning Spreadsheet
 
@@ -106,4 +106,4 @@ The Quarterly OKR Planning Meeting
 -   Each Team Member meets 1:1 with the Team Lead to verify and refined their Personal OKRs.
 
 With your OKR's created, it is time to execute on them for the next six weeks, but to do so effectively,
-you will need to [stay aligned as a team](./04-stay-aligned-as-a-team).
+you will need to [stay aligned as a team](./04-stay-aligned-as-a-team.md).
diff --git a/guides/OKR/04-stay-aligned-as-a-team.md b/guides/OKR/04-stay-aligned-as-a-team.md
@@ -8,7 +8,7 @@ Each Sprint begins with a planning meeting.
 
 ![](../../images/35-sprint-planning-prep.svg)
 
-_Note: We use Agile/Scrum in all our teams. It’s really just a fancy word for something simple so don’t be scared about the terminology or think you need to read books about it. There is some background information on how the Dev Team uses Scrum [here](https://handbook.interaction-design.org/development/guides/scrum/)._
+_Note: We use Agile/Scrum in all our teams. It’s really just a fancy word for something simple so don’t be scared about the terminology or think you need to read books about it. There is some background information on how the Dev Team uses Scrum [here](../../outdated/scrum/README.md)._
 
 Prepare yourself before a Sprint Planning Meeting
 
@@ -79,4 +79,4 @@ This Team-wide meeting could be the day after the 1:1 Meetings or on the same da
 
 If you already have a recurring Team-wide meeting, then hold this “Team-wide OKR Check-in Meeting” at the same time. There’s no reason for having too many meetings.
 
-At the end of the quarter, it is time to [assess your OKRs](./05-assess-your-okrs).
+At the end of the quarter, it is time to [assess your OKRs](./05-assess-your-okrs.md).
diff --git a/guides/OKR/README.md b/guides/OKR/README.md
@@ -9,8 +9,8 @@ at the lowest possible cost for millions of people, you are only going to succee
 To achieve this at the IxDF, we hire unicorn team members, maintain a high-performance culture,
 and use frameworks like scrum, agile and OKRs (Objectives and Key Results).
 
-If you are not already familiar, you can learn more [about OKRs](./00-why-okrs),
-or about the [benefits of OKRs](./00-benefits-of-okrs).
+If you are not already familiar, you can learn more [about OKRs](./00-why-okrs.md),
+or about the [benefits of OKRs](./00-benefits-of-okrs.md).
 
 If you are already familiar and want to start using OKRs as an IxDF staff,
-please start with [our OKR cadence](./01-okr-cadence).
+please start with [our OKR cadence](./01-okr-cadence.md).
diff --git a/guides/onboarding/README.md b/guides/onboarding/README.md
@@ -29,15 +29,15 @@ We don't expect you to spend too much time and feel pressured, however you can:
 1.  To start, head over to [🔒 IxDF Handbook Course](https://www.interaction-design.org/courses/ixdf-handbook)
     and go through Lesson 1 and Lesson 2 where the onboarding is explained.
 1.  Set up and know your [collaboration tools](../collaboration-tools.md).
-1.  Know our [expectations from you and your work](../roles/senior-developer).
+1.  Know our [expectations from you and your work](../roles/senior-developer.md).
 1.  Get closer to coding: Setup your [🔒 working environment](https://github.com/InteractionDesignFoundation/IxDF-web/blob/main/docs/environment/first-run/README.md)
     (private repository link) — It’s time-consuming (2-3 hours), so don't wait.
     While your tools are being downloaded/installed, you can continue with the list.
 1.  Never stop learning 📖. Go through our library and create a plan to acquire
     every bit of knowledge there. Once you have a plan, please discuss it with
     your mentor. (Are you full-stack? Then please open both links☀):
-    -   Literature/subscriptions [for back-end developers](../../library/backend/literature)
-    -   Literature/subscriptions [for front-end developers](../../library/frontend/literature)
+    -   Literature/subscriptions [for back-end developers](../../library/backend/literature.md)
+    -   Literature/subscriptions [for front-end developers](../../library/frontend/literature.md)
 1.  If you have any issues accessing the platform, company culture course
     or our collaboration tools, please ping the Member Experience team (`@member-experience-team`)
     via Slack (#onboarding-buddy-chat), so they can assist you. By this point,
diff --git a/index.md b/index.md
@@ -67,11 +67,12 @@ hero:
 </section>
 
 <section class="container">
-<h2 class="h2">Quick links: Coding conventions</h2>
-            <ul class="ul list-disc">
-                <li><a href="/library/backend/conventions--php.html">PHP</a> and <a href="/library/backend/conventions--laravel.html">Laravel</a></li>
-                <li><a href="/library/backend/conventions--sql.html">SQL</a></li>
-                <li><a href="/library/frontend/conventions--js.html">JS</a> and <a href="/library/frontend/conventions--jsdoc.html">JSDoc</a></li>
-                <li><a href="/library/frontend/conventions--css.html">CSS</a></li>
-            </ul>
+
+## Quick links: Coding conventions
+
+- [PHP](/library/backend/conventions--php.md) and [Laravel](/library/backend/conventions--laravel.md)
+- [SQL](/library/backend/conventions--sql.md)
+- [JS](/library/frontend/conventions--js.md) and [JSDoc](/library/frontend/conventions--jsdoc.md)
+- [CSS](/library/frontend/conventions--css.md)
+
 </section>
diff --git a/library/backend/clean-code-php.md b/library/backend/clean-code-php.md
@@ -930,7 +930,7 @@ Singleton is an [anti-pattern](https://en.wikipedia.org/wiki/Singleton_pattern).
 1.  They inherently cause code to be tightly [coupled](https://en.wikipedia.org/wiki/Coupling_%28computer_programming%29). This makes faking them out under **test rather difficult** in many cases.
 1.  They carry state around for the lifetime of the application. Another hit to testing since **you can end up with a situation where tests need to be ordered** which is a big no for unit tests. Why? Because each unit test should be independent from the other.
 
-There is also very good thoughts by [Misko Hevery](http://misko.hevery.com/about/) about the [root of problem](http://misko.hevery.com/2008/08/25/root-cause-of-singletons/).
+There is also very good thoughts by [Misko Hevery](https://web.archive.org/web/2019/http://misko.hevery.com/about/) about the [root of problem](https://web.archive.org/web/2019/http://misko.hevery.com/2008/08/25/root-cause-of-singletons/).
 
 **Bad:**
 
@@ -1445,7 +1445,7 @@ oriented API that aims to improve the readability of the source code by using
 [Method chaining](https://en.wikipedia.org/wiki/Method_chaining).
 
 While there can be some contexts, frequently builder objects, where this
-pattern reduces the verbosity of the code (for example the [PHPUnit Mock Builder](https://phpunit.de/manual/current/en/test-doubles.html)
+pattern reduces the verbosity of the code (for example the [PHPUnit Mock Builder](https://docs.phpunit.de/en/12.0/test-doubles.html)
 or the [Doctrine Query Builder](https://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/query-builder.html)),
 more often it comes at some costs:
 
diff --git a/library/backend/conventions--laravel.md b/library/backend/conventions--laravel.md
@@ -513,7 +513,7 @@ Route::name('home')->get('/', HomeController::class);
 
 1. [Policy class](https://laravel.com/docs/master/authorization#creating-policies) methods MUST use camelCase. Example: `@can('editPost', $post)` ([Laravel does it under the hood](https://github.com/illuminate/auth/blob/09d82d3a2966e6673495456f340855186a1962f5/Access/Gate.php#L718))
 1. Try to name abilities using default CRUD words. One exception: replace `show` with `view`. A server shows a resource, a user views it.
-1. Some other packages may use Policies (example: [Nova](https://nova.laravel.com/docs/resources/authorization.html)). Build your method naming strategy accordingly.
+1. Some other packages may use Policies (example: [Nova](https://nova.laravel.com/docs/v5/resources/authorization)). Build your method naming strategy accordingly.
 
 ## Validation
 
diff --git a/library/backend/conventions--php.md b/library/backend/conventions--php.md
@@ -32,7 +32,7 @@ IxDF uses automated tools to check our code on CI:
 -   [Psalm](https://psalm.dev/docs/) (`errorLevel="1"`)
 -   [PHPStan](https://phpstan.org/user-guide/getting-started) (`level: 8`)
 -   [Rector](https://github.com/rectorphp/rector)
--   [Deptrac](https://qossmic.github.io/deptrac/) (multiple configurations for modules and entire application)
+-   [Deptrac](https://github.com/opensoftwareconsulting/deptrac) (multiple configurations for modules and entire application)
 -   [composer-dependency-analyser](https://github.com/shipmonk-rnd/composer-dependency-analyser) (checks for unused and shadow dependencies)
 -   and more...
 
@@ -137,7 +137,7 @@ protected function initialize(string $notificationFQCN): Notification
 
 ### Final by default
 
-Use `final` for classes and `private` for methods [by default](<(https://ocramius.github.io/blog/when-to-declare-classes-final/)>).
+Use `final` for classes and `private` for methods [by default](https://ocramius.github.io/blog/when-to-declare-classes-final/).
 This encourages composition, dependency injection, and interface use over inheritance.
 Consider the long-term maintainability, especially for public APIs.
 
@@ -372,7 +372,7 @@ There is a great guide [Testing tips by Kamil Ruczyński](https://github.com/sar
 
 ## Security
 
-See [Security](./conventions--laravel#security) section from Laravel conventions.
+See [Security](./conventions--laravel.md#security) section from Laravel conventions.
 
 ## Dependency Management
 
diff --git a/library/backend/literature.md b/library/backend/literature.md
@@ -58,7 +58,7 @@ YouTube:
 Blogs:
 
 1.  Freek’s (from Spatie) blog on Laravel & PHP: [freek.dev](https://freek.dev)
-1.  Brent’s Roose blog on Laravel & PHP: [stitcher.io](https://stitcher.io/blog)
+1.  Brent’s Roose blog on Laravel & PHP: [stitcher.io](https://stitcher.io/)
 1.  Tim MacDonald blog: [timacdonald.me](https://timacdonald.me/)
 
 ## References
diff --git a/library/frontend/clean-code-js.md b/library/frontend/clean-code-js.md
@@ -672,7 +672,7 @@ Two caveats to mention to this approach:
 
 2. Cloning big objects can be very expensive in terms of performance. Luckily,
   this isn't a big issue in practice because there are
-  [great libraries](https://facebook.github.io/immutable-js/) that allow
+  [great libraries](https://immutable-js.com/) that allow
   this kind of programming approach to be fast and not as memory intensive as
   it would be for you to manually clone objects and arrays.
 
@@ -2289,7 +2289,6 @@ This is also available in other languages:
   - [alivebao/clean-code-js](https://github.com/alivebao/clean-code-js)
   - [beginor/clean-code-javascript](https://github.com/beginor/clean-code-javascript)
 - ![tw](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Taiwan.png) **Traditional Chinese**: [AllJointTW/clean-code-javascript](https://github.com/AllJointTW/clean-code-javascript)
-- ![fr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/France.png) **French**: [GavBaros/clean-code-javascript-fr](https://github.com/GavBaros/clean-code-javascript-fr)
 - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [marcbruederlin/clean-code-javascript](https://github.com/marcbruederlin/clean-code-javascript)
 - ![id](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Indonesia.png) **Indonesia**: [andirkh/clean-code-javascript/](https://github.com/andirkh/clean-code-javascript/)
 - ![it](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Italy.png) **Italian**: [frappacchio/clean-code-javascript/](https://github.com/frappacchio/clean-code-javascript/)
diff --git a/library/frontend/conventions--css.md b/library/frontend/conventions--css.md
@@ -19,7 +19,7 @@ We use [ITCSS](http://www.creativebloq.com/web-design/manage-large-css-projects-
 
 -   [ITCSS architecture](https://www.xfive.co/blog/itcss-scalable-maintainable-css-architecture/)
 -   [ITCSS: Harry Roberts - Managing CSS Projects with ITCSS (video)](https://youtu.be/1OKZOV-iLj4?t=404)
--   [BEM quick-start](https://en.bem.info/methodology/quick-start)
+-   [BEM quick-start](https://getbem.com/introduction/)
 -   [Battling BEM CSS: 10 Common Problems And How To Avoid Them](https://www.smashingmagazine.com/2016/06/battling-bem-extended-edition-common-problems-and-how-to-avoid-them/)
 
 Additionally, we prefer to use camelCase, as follows:
diff --git a/library/frontend/conventions--js.md b/library/frontend/conventions--js.md
@@ -17,7 +17,7 @@ You can check all our custom rules at the [.eslintrc.js](https://github.com/Inte
 
 ## Docblocks
 
-[Use JSDoc](conventions--js) together with type definitions files.
+[Use JSDoc](./conventions--jsdoc.md) together with type definitions files.
 It will help both your IDE and developers to check types.
 This provides main benefits from TypeScript, but without translation cost and improved readability.
 
diff --git a/library/frontend/conventions--jsdoc.md b/library/frontend/conventions--jsdoc.md
@@ -17,7 +17,7 @@ This document is created to avoid confusion and increase consistency.
 
 ## JSDoc vs. PHPDoc
 
-Comparing with [PHPDoc](./../backend/conventions--php#docblocks), there are some differences:
+Comparing with [PHPDoc](../backend/conventions--php.md#docblocks), there are some differences:
 
 1.  JSDoc uses`@returns` instead of `@return`;
 2.  Curly brackets are used as wrappers for variable types, e.g., `{Object}`, `{Array<string>}`.
diff --git a/library/frontend/literature.md b/library/frontend/literature.md
@@ -39,12 +39,12 @@ Every frontend developer should have some backend knowledge to have basic workin
 1.  [Laravel Blade](https://laravel.com/docs/master/blade) - PHP template engine. Frontend developers should understand how to
     use `@extend`, `@include`, `@component`, `@section`, `@push`, `@foreach` and `@if` directives. They should also understand when they should use `{{ $variable }}` and `{!! $variable !!}` (display escaped/unescaped data).
 1.  How to get an instance of the authenticated Member at the view layer and how to determine whether the visitor is a guest or not (see
-    [🔒 Authenticated Member instance](https://github.com/InteractionDesignFoundation/IxDF-web/docs/library/backend/hints/authenticated-member-instance.md)).
+    [🔒 Authenticated Member instance](https://github.com/InteractionDesignFoundation/IxDF-web/blob/main/docs/library/backend/hints/authenticated-member-instance.md)).
 1.  How to
-    [🔒 create a new route and a new test view for it](https://github.com/InteractionDesignFoundation/IxDF-web/docs/code/backend/hints/create-test-route.md) for testing purposes.
+    [🔒 create a new route and a new test view for it](https://github.com/InteractionDesignFoundation/IxDF-web/blob/main/docs/code/backend/hints/create-test-route.md) for testing purposes.
     Sometimes it’s a faster way to implement a new feature.
 
-For more back-end hints, please see [🔒 backend hints dir](https://github.com/InteractionDesignFoundation/IxDF-web/docs/code/backend/hints).
+For more back-end hints, please see [🔒 backend hints dir](https://github.com/InteractionDesignFoundation/IxDF-web/tree/main/docs/code/backend/hints).
 
 ## Frontend
 

Original file line number	Diff line number	Diff line change
`@@ -16,4 +16,4 @@ Here is what the process looks like over the course of a normal quarter.`
`16`	`16`
`17`	`17`	`![](../../images/26-okr-quarter-reference.svg)`
`18`	`18`
`19`		`-Now that you have seen how our OKRs work at the organizational level, it’s time to start [creating your OKR's](./03-create-your-okrs).`
	`19`	`+Now that you have seen how our OKRs work at the organizational level, it’s time to start [creating your OKR's](./03-create-your-okrs.md).`