Wip: adding monthly chorus for dependency updates

d/m/components.ftd

@@ -0,0 +1 @@
+-- import: fastn.com/d/m/dependency-model

d/m/dependency-data.ftd

@@ -0,0 +1,69 @@
+-- import: fastn.com/d/m/dependency-model as dm
+-- import: fastn.com/u
+
+
+
+-- dm.dependency-data list dependencies:
+
+-- dm.dependency-data: $marked
+
+-- end: dependencies
+
+
+
+
+
+
+
+-- dm.dependency-data marked: Marked.js
+current-version: 9.1.4
+available-version: 9.1.5
+github-url: https://github.com/markedjs/marked/
+doc-url: https://marked.js.org/
+reference-url: https://cdnjs.com/libraries/marked
+updates: $marked-updates
+
+
+
+
+
+
+
+
+-- dm.update list marked-updates:
+
+-- dm.update: $u.arpita
+updated-on: 31-10-2023
+version: 9.1.4
+version-release-date: 31-10-2023
+pr-link: https://github.com/fastn-stack/fastn/pull/1440
+version-link: https://github.com/markedjs/marked/releases/tag/v9.1.4
+
+Using latest version marked 9.1.4, instead of 5.1.1.
+
+**Known Problems:**
+The problem with this version is that the heading gets converted into
+appropriate heading tag but it doesn't contain the id attribute. Consider the
+code below
+
+`# Heading 1`
+
+The above code gets converted into the following html
+`<h1>Heading 1</h1>`
+
+Instead of
+`<h1 id="heading-1">Heading 1</h1>`
+
+Checkout the [github issue](https://github.com/markedjs/marked/issues/3067)
+raised in the marked.
+
+**Solution:**
+
+Since we never encourage `fastn` users to ever use markdown headings but to use
+heading components provided by typography or doc site packages. This takes care
+of the problem above.
+
+So we can go ahead with this PR.
+
+
+-- end: marked-updates

d/m/dependency-model.ftd

@@ -0,0 +1,24 @@
+-- import: fastn.com/u
+
+
+-- record dependency-data:
+caption name:
+string current-version:
+string available-version:
+optional string github-url:
+optional string doc-url:
+optional string reference-url:
+optional string other-url:
+update list updates:
+
+
+
+
+-- record update:
+caption u.user-data updater:
+string updated-on:
+string version:
+string version-release-date:
+string pr-link:
+optional string version-link:
+optional body about:

d/m.ftd → d/m/index.ftd

@@ -3,7 +3,7 @@
 -- ds.h1: Version Policy
 
 Since we are a binary crate, and our library crates are only largely meant to be
-used by our binary crate, we are targetting the latest Rust version. Whenever a
+used by our binary crate, we are targeting the latest Rust version. Whenever a
 new version is released we always switch to it.
 
 -- ds.h1: Release Management
@@ -16,6 +16,13 @@ To create a release do the following:
 
 -- ds.h1: Monthly Cleanups
 
-1. Run `cargo update`.
+Monthly dependency updates are a must! We've set up a dedicated page to ensure
+we stay on track with this practice.
+
+Currently we have following dependencies and tracks:
+
+1. Marked.js: Parse markdown to HTML
+2. Prism.js: Code highlighter
+3. `cargo update`: Updates all rust dependencies
 
 -- end: ds.page

u/arpita-jaiswal.ftd

@@ -1,5 +1,18 @@
 -- import: fastn-community.github.io/spectrum-ds/common
 -- import: fastn.com/featured as ft-ui
+-- import: fastn.com/u/model
+
+
+-- model.user-data arpita: Arpita Jaiswal
+avatar: $fastn-assets.files.images.u.arpita.jpg
+profile: Lead Engineer
+github-url: https://github.com/Arpita-Jaiswal
+linkedin: https://www.linkedin.com/in/arpita-jaiswal-661a8b144/
+discord: https://discord.gg/arpita_j
+
+I believe that we are trying to cater the need of world with `fastn` technology.
+
+
 
 -- ds.user-info: Arpita Jaiswal
 avatar: $fastn-assets.files.images.u.arpita.jpg

u/index.ftd

@@ -1,6 +1,7 @@
 -- import: fastn-community.github.io/spectrum-ds/common
 -- import: fastn.com/featured as ft-ui
+-- import: fastn.com/u/arpita-jaiswal
+export: arpita
 
-
-
-
+-- import: fastn.com/u/model
+export: user-data

u/model.ftd

@@ -0,0 +1,8 @@
+-- record user-data:
+caption name:
+optional ftd.image-src avatar:
+optional string profile:
+optional body description:
+optional string github-url:
+optional string linkedin:
+optional string discord: