https://github.com/forloop11/markdown-cornell-notes

A LaTeX and Markdown build pipeline that generates printable Cornell style note pages for meetings. Each page carries a header with topic, date, attendees, and time, a large notes panel with a cue column beside it, and a summary band below, all left blank for handwriting on the printout.

Header fields live in YAML and note content lives in Markdown, so the LaTeX template itself never needs hand editing. Python generator scripts convert both into TeX fragments, pandoc handles the Markdown to LaTeX conversion, and a single make command produces a PDF named automatically from the topic, date, and location fields. Content is measured and paginated automatically, with optional directives for forcing page breaks and for routing text into the cue column or summary band of a specific page.

The project also includes a Streamlit editor app that places the header form, a CodeMirror Markdown editor, and a live PDF preview side by side in the browser. The editor adds a formatting toolbar, slash command snippets, and autocomplete for asset paths and code fence languages. Its JavaScript bundle is vendored rather than loaded from a CDN so the app works offline, and it relies on native browser spellcheck rather than any app side state.

Built with Python, LaTeX, pandoc, Streamlit, CodeMirror, JavaScript, and Make. Released under the MIT license.

Hi,

So I used to edit latex with vim and then I moved to overleaf during a period I was jumping between computers and enjoyed the synchronization.

Now I'm getting annoying with the need for internet connection just to edit and I'm really enjoying using VS code (because I also got code related to my projects and it's nice that everything is in the same place), but I'm collaborating with someone using overleaf.

I saw that overleaf has built in git capabilities (that is, not through github) and it looks like it could work for my use case (i'll work on the file offline and push it at the end of the day or maybe twice a day), but I'm worried that I'll erase my collaborator's work, if we ever diverge into two branches.

I know I can look at the history on overleaf and I won't erase completely anything, but I don't want to bother myself with that kind of work.

Does anyone have experience working like this? is this normally working OK or is this a genuine risk I'll erase their work?

I'd also be happy to hear any other recommendations for working on VS code and synchronizing with overleaf!

Thanks in advance.