We actually made the course ourselves, following James Stewart's Calculus and our own approach to teaching these topics (we're two PhD students). We wrote everything in English first, then translated it into other languages.
AI accelerated our workflow, we prompted the visuals and explanations we wanted, then polished the results ourselves. So we're confident in the teaching quality and correctness of these videos, they're not pure AI artifacts :)
We want to nail the fundamentals first: Single-variable Calculus, Linear Algebra, Differential Equations, Physics, Machine Learning etc. These are the courses with the largest audiences, and we need that reach to sustain this project. But if you think focusing on advanced topics instead would make more sense, I'd love to hear your perspective!
Yeah, that's a stupid one from me. I'll get that working now. In the meantime, if you create an account, you can use the application for free without exporting
Thank you so much for the kind words, and I'm sorry for the trouble the changes caused you.
To give some context: I hadn't worked on RenderCV for about six months, and when I came back, I had grown technically and my design taste had changed. I decided to do a significant overhaul rather than preserve backwards compatibility. It felt necessary to maintain my enthusiasm for this project long-term.
You're right about semantic versioning. I used a two-number scheme (MAJOR.MINOR) back in 2023 when I didn't know much about releasing software. By the time I understood the benefits of MAJOR.MINOR.PATCH, I didn't want to change it mid-stream. I'm planning to switch after v3. It will give me more flexibility to tag updates appropriately.
I'm also adding migration documentation to my list. You're right that I should have done this. Going forward, there will be clear migration guides.
Regarding the Markdown issue where sections show only titles, that sounds like a bug. If you could open an issue with details, I'd appreciate it.
The JSON Resume schema did not support what we needed, so we deliberately created our own.
We wanted to define 9 different entry schemas that could be used under any section title. In our schema, each section, regardless of its title, contains a list composed of one of these nine entry types. This is different from the JSON Resume approach, where specific entry schemas are tied to specific sections (work schema for work section, etc.).
In RenderCV, users can choose any section title they want and use any of the 9 entry types within it. Each entry type is rendered differently in the generated PDF.
It’s completely flexible. However, it's not done through CSS. We use Typst to generate PDFs, and we template Typst files using Jinja2 from YAML. You can override the built-in Typst templates; see the guide here: https://docs.rendercv.com/user_guide/how_to/override_default...
Yes, unfortunately, you will need to convert them to YAML. I think an LLM can easily do that for you, though. This has been requested before, but we haven’t implemented it in order to keep our schema robust and simple. Maybe we should add it.
OK, thanks. I don't have a lot of publications or anything, so for me it wouldn't be too much of an issue, but in certain fields I thought a CV was mostly publications/citations.
Thank you. We will add an analysis of how RenderCV PDFs perform with applicant tracking systems in docs at some point, but users have been reporting positive results. We generate the PDFs using Typst, which adheres to modern PDF standards.
We actually made the course ourselves, following James Stewart's Calculus and our own approach to teaching these topics (we're two PhD students). We wrote everything in English first, then translated it into other languages.
AI accelerated our workflow, we prompted the visuals and explanations we wanted, then polished the results ourselves. So we're confident in the teaching quality and correctness of these videos, they're not pure AI artifacts :)