practicalli / practicalli/practicalli.github.io

Article: running practicalli on a minimal budget

Open
#8 0 comments 0 reactions 1 assignee View on GitHub

@practicalli-johnny is already working on this.

Since Mar 30, 2025.

Dominant language
Makefile
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Ptracticalli has been invaluable to my own learning of Clojure and wider software engineering concepts & tools.

I am humbled and motivated when people tell me how useful it has been to them. I am also very thankful for the sponsorship I have recieved.

  • static sites can be deployed without financial cost

Book & Blog content

mkdocs is a feature rich and mature tool for creating

NOTE: asciidoc is very powerful too and I did evaluate https://readsthedocs.com/ although I would have to convert 1,000s of markdown pages too ascidoc (which wasn't viewed as valuable use of time)

Managing content

GitHub projects

Projects has really evolved in the last yeat to be an excellent tool for managing workloads effectively.

A kanban board is used to capture and prioritise work

NOTE: I used GitHub mobile to capture this article idea and content as I wasn't near my computer. I wrote most of the copy in Neovim, running in Termux on my android smart phone

Book & Blog publishing

Mkdocs has a build command to generate a static site

A simple workflow is used to publish the book

setup-python action is used to provide an environment to build the website

The files foe the website are committed to gh-pages branch and the new version f the website is ready to view.

Standardising

Moving common documents to the Practicalli GitHub Org

  • funding.yaml for sponsorship details
  • licence ?
  • GitHub workflows

Almost zero ?

Domain names aren't free

My time to create and maintain

  • content creation
  • content updates (new libraries, updated versions, etc)
  • enabling other people to contribute effectively
  • github workflows & actions
  • security around github org

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.