Add web interface for blog posts (#2)

* front: header, author block

* Main page

* WIP Category, Post pages

* MPV1

* Lint

content/drafts/2023/08/2023-08-21-colorize-svg.mdx → content/posts/2023/08/2023-08-21-colorize-svg.mdx

@@ -4,11 +4,9 @@ description: This post describes how to change SVG color with CSS
 slug: change-svg-color
 category: css
 datePublished: 2023-08-21T00:00:00.000Z
-tags: [css, scss, svg]
+tags: [beginner, css, scss, svg]
 ---
 
-# How to change color of SVG with CSS
-
 I saw a lot of cases in my career when CSS beginners exported same SVG icon files twice just to put it in the layout with different color.
 
 Let's look on example:

content/drafts/2023/08/2023-08-21-git-flow.mdx → content/posts/2023/08/2023-08-21-git-flow.mdx

@@ -2,13 +2,11 @@
 title: Git branching policy for team with scheduled releases (GitFlow)
 description: In this post I'd like to share with you how to organize branches in a team with scheduled releases and what flow worked perfectly fine for our team setup.
 slug: git-branching-policy
-category: tech-project-management
+category: pm
 datePublished: 2023-08-21T00:00:00.000Z
-tags: [git, development, gitflow, team]
+tags: [intermediate, git, development, gitflow, team]
 ---
 
-# Git branching policy for team with scheduled releases (GitFlow)
-
 In this post I'd like to share with you how to organize branches in a team with scheduled releases and what flow worked perfectly fine for our team setup.
 
 Spoiler - GitFlow.
@@ -49,7 +47,7 @@ GitFlow has 3 types of short-living branches - `feature`, `release`, `hotfix`:
 - `release/vX.X.X` – branch reflecting set of new features preparing for production (release candidate),
 - `hotfix/hotfix_name` – temporary branch for urgent code changes in the middle of the Sprint.
 
-### FLow description
+### Flow description
 
 The flow will be described below in reflection to Sprint activities.
 

content/drafts/2023/08/2023-08-27-js-number-separator.mdx → content/posts/2023/08/2023-08-27-js-number-separator.mdx

@@ -2,13 +2,11 @@
 title: Improve readability of numbers in your JavaScript code
 description: Few advices on how to improve readability of numbers in your JavaScript code
 slug: js-numbers-readability
-category: javascript
+category: js
 datePublished: 2023-08-27T00:00:00.000Z
-tags: [javascript, numbers, readability]
+tags: [beginner, javascript, numbers, readability]
 ---
 
-# Improve readability of numbers in your JavaScript code
-
 Quite a common situation to have big numbers in JavaScript code e.g. during working with timestamps, intervals, timeouts, milliseconds:
 
 ```js

content/drafts/2023/08/2023-08-28-minimal-nestjs-bootstrap.mdx → content/posts/2023/08/2023-08-28-minimal-nestjs-bootstrap.mdx

@@ -4,11 +4,9 @@ description: Things to do after running $ nest new command
 slug: minimal-nestjs-setup-for-api-project
 category: backend
 datePublished: 2023-08-28T00:00:00.000Z
-tags: [nestjs, nodejs, backend, api, docker]
+tags: [intermediate, nestjs, nodejs, backend, api, docker]
 ---
 
-# Minimal Nest.js setup for API project
-
 When starting new enterprise-level Nest.js-based project it is fat not enough to run `$ nest new` command to cover minimal infra requirements.
 Usually initial framework setup misses next things for such project:
 

content/drafts/2023/08/2023-08-29-ci-for-js-project.mdx → content/posts/2023/08/2023-08-29-ci-for-js-project.mdx

@@ -4,11 +4,9 @@ description: In this post we will look at detailed instructions how to setup con
 slug: ci-for-js-project
 category: devops
 datePublished: 2023-08-29T00:00:00.000Z
-tags: [devops, ci, javascript, github, github-actions]
+tags: [intermediate, devops, ci, javascript, github, github-actions]
 ---
 
-# Setting up continuous integration pipeline for JavaScript project
-
 In this post we will look at detailed instructions how to setup continuous integration (CI) for JavaScript project hosted on GitHub and GitHub Actions.
 
 It is important to run static analysis and unit tests on every new portion of code changes as often and as early as possible.

content/drafts/2023/08/2023-08-30-structured-data-markup.mdx → content/posts/2023/08/2023-08-30-structured-data-markup.mdx

@@ -4,11 +4,9 @@ description: It is important to optimize your site pages for search engines to i
 slug: structured-data-features-for-every-site
 category: misc
 datePublished: 2023-08-30T00:00:00.000Z
-tags: [seo, structured-data, google-search]
+tags: [beginner, seo, structured-data, google-search]
 ---
 
-# SEO: Must have structured data features for every site
-
 It is important to optimize your site pages for search engines to increase organic search traffic. One of mandatory SEO task on every site - is adding structured data markup to your pages.
 
 In this post we will review what is structured data and what its features should be added to every your site.