# Resources for creating a blog/website for a Fortran learning journey

**URL:** <https://fortran-lang.discourse.group/t/resources-for-creating-a-blog-website-for-a-fortran-learning-journey/8768>\
**Category:** Help\
**Created:** [October 29, 2024, 3:56pm UTC](https://fortran-lang.discourse.group/t/resources-for-creating-a-blog-website-for-a-fortran-learning-journey/8768 "2024-10-29T15:56:24Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ricriv](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@ricriv](https://fortran-lang.discourse.group/u/ricriv)\
**Post date:** [November 13, 2024, 7:36am UTC](https://fortran-lang.discourse.group/t/resources-for-creating-a-blog-website-for-a-fortran-learning-journey/8768/10 "2024-11-13T07:36:55Z")

</div>

I see your point, and that’s why I lock all the dependencies using [Poetry](https://python-poetry.org/). You can find [here](https://fortran-lang.discourse.group/t/how-to-use-ford-for-your-documentation/8272/2) a workflow for FORD, but it applies just as well to Jupyter Book and Sphinx. So, until I decide to update nothing can break, and when it does the CI will never deploy a broken website.

---

_[View the full topic](https://fortran-lang.discourse.group/t/resources-for-creating-a-blog-website-for-a-fortran-learning-journey/8768)._