Thank you for working on and sharing this project, it's a wonderful example of how maps help tell / connect the stories through the years. It was also nice to see the piece you drew inspiration from that you linked to in another comment.
I'm curious -- each section (after the transitional animation) seems like it translates quite well to being a fixed page, and I'm wondering if you've looked at there being an easy way to generate a version that could be printed?
The reason I ask is that I'm working on a family history project which involves various locations, maps, newspaper stories and old photographs, and whilst something interactive feels like it would be an engaging way to do it, for the long term it's always good to have a printed copy of anything :)
I could imagine if there was an easy way to generate a print version of your articles, some people would pay for a copy (that was printed professionally in a suitable photobook-style format).
Apologies if there is a simple way to generate this and I've missed it in my cursory glance around the code :)
I have not but this is a good flag and will think more about it! i think newsrooms have spent a lot of time thinking about how to translate online first material to print and vice versa so there may be some ideas to draw from. The freedom and creativity that comes with bespoke online first projects does cause some challenges to easy exporting to print versions.
Thanks for the quick reply -- yes, I imagine there is some prior art for this, although I'm often amazed at how hard it still is to print (even just to print to save a pdf) from many websites!
> For example, they seem to not care about instructions to only write a response and no explanation, thus making it impossible to use them in a pipeline
I was doing some local tidying up of recording transcripts, using a fairly long system prompt, and I saw the same behaviour you mention if the transcript I was passing in was too long -- batching it up to make sure to be under the max length prevented this.
Might not be what's happening in your case, but I mention it because it wasn't immediately obvious to me when I first saw the behaviour.
Took us about three months to pick Overleaf, we went for it largely because it was a single word, hard to confuse/mispell when said aloud (unlike writeLaTeX), had a connection with writing "over the page", and probably must importantly, we could get the .com domain.
Can you explain this part? The sound of "Leaf" could be represented by any number of possible spellings, eg "leave", "lief", "leeve"... - not all are standard English words, but neither is "Overleaf", and exotic/made-up spelling would be just par for the course for a tech product with an exotic/made-up name.
I actually really liked the domain name writelatex.com, because it pretty much tells you what you can do and it's easy to remember, even if you haven't used it in a long time (which could easily happen for a product that gets used a lot in academia and much less outside, eg someone returning to school after a few years of work).
Ah yes, I missed some important context - one of the reasons for moving to a name without LaTeX in it was because we'd just released the first beta version of the visual editor (the rich text mode at the time), and the goal was to keep lowering the barriers to getting started with LaTeX, and to make collaboration easier for non-LaTeX users. And so Overleaf came from a search for a broader name than writeLaTeX.
That's an interesting point about the pronunciation - overleaf is a standard English word, and certainly seemed less confusing than writeLaTeX when said aloud, but I agree it's not perfect! Was the best we could find at the time (especially given the other needs mentioned above).
Thanks Dang! You're right that's probably the better link to use, rather than the arXiv version -- I just have a liking for PDFs, which is why I linked to the preprint :)
Thanks w-m, glad you find Overleaf useful :) I can't quite believe it's been ten years since we started out -- time certainly does fly by.
I did appreciate the somewhat circular loop in posting this, so thanks also for noticing! And my H/T for spotting this originally goes to my friend & colleague Alf Eaton, who reshared Lukas's tweet: https://twitter.com/lukas_blecher/status/1696101110853910716