- Makefile 48.5%
- M4 24.2%
- Shell 16%
- CSS 6.4%
- HTML 4.9%
| LICENSES | Licensing | |
| src | MUCH better font flow | |
| .gitignore | First shot at bare bones build system. | |
| build.sh | MUCH better font flow | |
| Makefile | Missed a spot | |
| package-lock.json | MUCH better font flow | |
| package.json | MUCH better font flow | |
| README.md | Documentation architecting. | |
Blog
Another attempt at making a blog, this time with less dependencies.
Development
Pre-Requisites
One wants to have the following tools in order to work with this project.
POSIX Compliant Tooling
Have access to a posix compliant shell with the following tools installed:
- make
- m4
- cat
- sh
- touch
- rm
- mkdir
- find
See https://pubs.opengroup.org/onlinepubs/9799919799/ for more detail about what should be required, behavior wise, from these tools and what it means to have a posix compliant shell.
Node
Have the following installed:
- Node v20.19.2
- npm 9.2.0
The architecture of this project is designed such that node and npm are not essential requirements. To get rid of the node dependency, all you need to do is:
- Find a dev server solution which can run the static website found in
site, i.e. replace thenpm run devcommand found inpackage.json. - Find a new tex to mathml core compiler and refactor
<single script or command>to call that new compiler instead of temml.
fontmake
See: https://github.com/googlefonts/fontmake
I currently use version 3.10.0.
This tool can in principle be easily replaced, one just needs to find a tool
that can handle the UFO formatted fonts in src/font and then replace the
<whatever command> found in build.sh.
See: https://unifiedfontobject.org/ for the UFO 3 specification (which is what we use here).
I also use FontForge found here: https://fontforge.org/en-US/ in order to orient myself sometimes, but please be certain that I maintain these UFO folders by hand and they are meant to be read and interacted with by hand.
Build
In the shell, run:
npm installsh build.sh
This builds the static website in site.
Run Locally
In the shell, run:
npm run dev
Cleanup
In the shell, run:
rm -rf node_modulesmake clean_build
This will remove everything that the build steps generated.
Documentation
Pre-Requisites
In order to read and interact with the documentation, one must have the following:
emacs with org mode
TeX Live
Build
- Run
make docsin the shell.
Navigate
- Check out the
index.org. The rest is navigable from there.
Cleanup
- Run
make clean_docsin the shell. This will remove anything thatmake docsgenerated.
Licensing
All code is under AGPL as described in LICENSES/agpl.txt and anything else
is under CC-BY-SA 4.0 as described in LICENSES/cc-by-sa-4-0.txt.