I tried to avoid custom commands and environments to keep it simple. Your content in org text should fit nicely with this.
It also has a template where the preamble is stored in different file such that you can try a different look by just un/commenting a different preamble file.
I remember watching it on YouTube. Really liked the book design. How expensive/difficult is it to have each page in different colour? Tell me more about the page quality. Also it looked like "product sans" at first glance, if yes then how is it licensed? Why didn't you choose flat binding?
Anyway congratulations on the book release. It's really a beautiful creation and worthy of being an art piece.
Glad that you liked it. Will do that in future. I'm still trying to organise the info in a meaningful manner without being overwhelming.
My intent is to make a collection of just the impactful players (influential typefaces, designers and foundries) in a concise manner. I have many other lists in the pipeline (other files in the repo). Finding it really difficult to be objective/professional about (some silly) typeface when writing about it. Although I don't want to put my opinions on a list about fonts but still feel so strongly about it that most descriptions are still left blank. Hopefully I'll be able to compile a (not so long) list about fonts very soon.
Simple tweaks like adjusting colors or fonts can make a big difference in the look and feel of the resume. I also chose not to use `fontspec` to avoid xelatex etc. There are a few [more templates showing other possibilities](https://github.com/subidit/rover-resume).
I crafted the options for formatting with LaTeX enthusiasts in mind, anticipating their desire to personalize the layout effortlessly. But not many people are actually modifying anything.
I thought to include working code snippets showing how to achive a particular formatting, like different ways to format SKILLS section or the NAME and contract information header. But feel that would make it look more messy. Ultimately ended up dumping those snippets in a `user-guide.md` file. I feel it could be better organised. Please advise. Thanks.
This makes sense but I feel there might be an opportunity for people who knows how to train compact versions of these LLMs which run on local machines and solve a very specific use case for that business.
What could be a bootcamp like curriculum for someone who wants to learn only how to train a LLM (upto a sellable standard)?
I tried to avoid custom commands and environments to keep it simple. Your content in org text should fit nicely with this.
It also has a template where the preamble is stored in different file such that you can try a different look by just un/commenting a different preamble file.