1.2 Deep Dive

State/Version: 20230829p1

1.2.1.1 Creation workflow - Deep Dive

Sequencediagram

sequenceDiagram participant A as Laptop@local participant B as blog-source@github participant C as blog-rendered@github A->>A: 1. Create content locally A->>B: 2. Push code to blog-source@github Note over A, B: Commit action (push)
will trigger "Github Actions" B->>C: 3. Push static html from blog-source@github to blog-rendered@github
(Github pages) via a "Github Actions"

1.2.2 Github setup

Alias	Real world	brief description
blog-source@github	gerundium/gerundium.github.io-source	This repository contains the full monty. Use it to create / render new content for your blog.
blog-rendered@github	gerundium/gerundium.github.io	This repository is linked as git submodule inside blog-source@github. It contains the rendered / static html files

# --
# Folder tree
# --
./blog-source@github
├── archetypes
├── content
├── data
├── layouts
├── public  # blog-rendered@github (Git submodule)
|   ├── authors
|   ├── basics
|   ├── categories
|   ├── css
|   ├── fonts
|   ├── images
|   ├── js
|   ├── logo
|   ├── mermaid
|   ├── posts
|   ├── series
|   ├── tags
|   └── webfonts
├── resources
├── static
└── themes

1.2.3 Step-by-step deployment

Apply changes to blog-source@github/content
Build static html
```
# Execute command on the laptop
hugo
```

Commit changes in public submodule and push commit to blog-rendered@github

 # Git commit and push
 git add -A
 git commit -m "add: <specify cxhange>"
 git push

Wait a minute while build and deployment piplines run. Check if changes were deployed to github pages. gerundium.github.io