Hi all!

When you decide to share your perfect solution with community by posting it in LDI blog please follow this guide:

  1. Clone source code
git clone https://github.com/lean-delivery/lean-delivery.github.io-src.git
  1. Create a new branch
git checkout -b <branch_name>
  1. Create a new page in content/articles folder with the next count number of existing pages in the name with "rst" type, for example "1_contribution_guide.rst"
  2. Commit changes
git commit
  1. Push it to github
git push
  1. It will be ran a CD pipeline with rst syntax checker, and if it will be passed successfully, will be placed a comment with links of preview site and CD pipeline status to the current commit.

You could see a build status here https://gitlab.com/lean-delivery/lean-delivery-github-io-src/-/jobs/

If you want to publish your changes in lean-delivery.com just create a merge request from your branch to master.

You can see the logic of CD in gitlab-ci.yml

Deployment preview steps in any "dev" branches are:

  1. Run RST Validation of ".rst" files.
  2. Remove files (if exists) in s3 subfolder named as a current branch.
  3. Build a static site with "pelican" https://blog.getpelican.com/
  4. Change the default app URL in pelicanconf.py.
  5. Create (if not exists) subfolder in s3 bucket with the name of the current branch.
  6. Copy output files after the build to this subfolder.
  7. Create a comment with a link to preview page https://preview.lean-delivery.com/<branch_name> in the current commit.

Deployment from the master branch:

  1. Build a static site with "pelican" https://blog.getpelican.com/
  2. Copy output files after the build to "docs" folder (it's a GitHub submodule for GitHub Pages)
  3. Update submodule with rebase.

Thank you for your contribution!

Best regards,

Lean-delivery Team