BruinJournal/journal
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix a couple of grammar errors
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Details

Browse source
This commit is contained in:
Isaac Mills 2024-04-21 14:04:48 -04:00
parent e5d11deabe
commit bf9c790a46
Signed by: fnmain
GPG key ID: B67D7410F33A0F61
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/how_to_run_a_journal.dj
View file

@ -61,7 +61,7 @@ Because our CI tool is running this code, we can know which articles need compil
- Stat the changed files, which is how we know which files need to be compiled, and which files have been deleted
- Run a blame on new articles, which is how we figure out who wrote them
- See if we are we have changed the production branch, and index new articles if so
- See if we have changed the production branch, and index new articles if so
Everything I've described that the program can do so far can be done in just \~400 lines of Rust. This is the effect of buidling simple on top of simple, _and making an effort to retain simplicity_ by making the most out of the simple building blocks. (P.S: Our Rust code now also generates a title card image for each article, so they look better on platforms like Twitter and Discord. By using the same stradegy, I only needed to add \~230 lines to our Rust code)