Azure Devops: Recap Creating this Blog Site
March 27, 2025 23:33
David Jones MVP
web
jekyll
devops
blobstorage
blog
27 Mar 2025 23:33:25
David Jones MVP
web jekyll devops blobstorage blog
web jekyll devops blobstorage blog
A recap of the way this blog site is generated, built and deployed. The next two blog posts refer to this.
This site is a highly customised Jekyll siye. It has been running for a number of years with regular updates and new blog posts. There has been significant coding of its functionality including:
- Meta-information wrt blog posts. Each post has one category. Also, posts have one or more tags which can be used for searching the site`
- The main index page is in reverse chronological order and each post entry has the meta-information that can be clicked on

- When a post’s category or one of tags is clicked, all posts of that category or tag are presented for slection.
- When the site is built, an index file with links is geneerated for each category and for each tag found in posts.
- New tags can be adhocly added when authoring pages, but categories are define on
- There is a yaml file
_data/sections.yml
that is used for grouping posts. This is a fixed list but is similar to categories. There is a sidebar of these sections that can be expanded to reval all posts in a section. - The site uses a number of off-the-shelf plugins.
- The site is authored in VS Code and can built and run locally there.
- Content is reposited to Azure DevOps where it automatically built then released - Copied to Azure Blob Storage. Thre it become a Static Web Site in a https context.
- As a footnote, the author receives an emial notification when the content is received by DevOps repository, when teh site is built/fails, and if built it is released.
Topic | Subtopic | |
< Prev: | Blockly | Switch Block |
This Category Links | ||
Category: | Web Sites Index: | Web Sites |
Next: > | Azure Devops | Jekyll Deployment Issue - A workaround. |
< Prev: | Azure Pipelines | Jekyll Site Build failure - Part 2 |

