From abcd49da9f3c8f96eca8143985d84963143f7b7d Mon Sep 17 00:00:00 2001 From: Matthias Mair Date: Tue, 31 Jan 2023 07:47:46 +0100 Subject: [PATCH] fix links --- _posts/2023-01-30-plugin-list.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/_posts/2023-01-30-plugin-list.md b/_posts/2023-01-30-plugin-list.md index 35ae250d..9716fe5e 100644 --- a/_posts/2023-01-30-plugin-list.md +++ b/_posts/2023-01-30-plugin-list.md @@ -7,7 +7,7 @@ Recently a new feature was launched: A central plugin list. ## TLDR -The Plugin List is managed by the [InvenTree org](https://github.com/inventree) and is [open for submissions](https://github.com/inventree/inventree-website#adding-a-plugin-to-the-list). It is a simple list [on the website](../plugins.html) for a start. Being on the list is not an endorsement or guarantee of service by the core team. +The Plugin List is managed by the [InvenTree org](https://github.com/inventree) and is [open for submissions](https://github.com/inventree/inventree-website#adding-a-plugin-to-the-list). It is a simple list [on the website]({% link plugins.html %}) for a start. Being on the list is not an endorsement or guarantee of service by the core team. ## Why plugins and a plugin list? @@ -24,17 +24,17 @@ The plugin list is a way to share the cool, public plugins you made with the com ## How it works -As mentioned [before](../_news/2022-04-23-news-are-starting.md), we use Jekyll for this website. This means that the list consists of static pages that are generated from YAML/Markdown files. The output is hosted by GitHub pages (for free ;-)) and can be previewed on PRs thanks to the Netlify app integration. +As mentioned [before]({% link _news/2022-04-23-news-are-starting.md %}), we use Jekyll for this website. This means that the list consists of static pages that are generated from YAML/Markdown files. The output is hosted by GitHub pages (for free ;-)) and can be previewed on PRs thanks to the Netlify app integration. A file contains a number of standardised fields in the header and markup text for the plugin page that uses Markdown (just like GitHub README pages). That information is used to generate: -- the individual plugin pages (eg. [this one](../_repo/inventree-brother-plugin.md)) +- the individual plugin pages (eg. [this one]({% link _repo/inventree-brother-plugin.md %})) - plugin cards on the main page (showing the newest entries) -- a list of [all plugins](../plugins.html) -- overview pages for [tags](../tags.html) and [categories](../categories.html) +- a list of [all plugins]({% link plugins.html %}) +- overview pages for [tags]({% link tags.html %}) and [categories]({% link categories.html %}) Adding a new entry is as simple as forking, creating a new file in the plugins folder and opening a PR. More on that is below. -There are also entries and pages for authors/publishers. Currently, we only support one author per plugin, but that might change in the future. The author entry is used to generate a page for the author (eg. [this one](../_publishers/schrodingersgat.md)). That page also contains all blog posts written by the author and a few links. +There are also entries and pages for authors/publishers. Currently, we only support one author per plugin, but that might change in the future. The author entry is used to generate a page for the author (eg. [this one]({% link _publishers/schrodingersgat.md %})). That page also contains all blog posts written by the author and a few links. ### Disclaimer