Bunch of new updates that are mostly hidden in settings:

• spaced events in the editor,

• the option to turn off autosave and save manually,

Updated the parser a bit ago for a simpler parse result and to include some BCE parsing improvements thanks to Deuh

Timelines and documents are now private by default.

If you want to share a timeline or markwhen document with someone, you will need to specify their email in the document's header .

What is remark.ing and how to get started

Remark.ing is a chronological aggregation of blog posts (or "remarks"). It is very similar to twitter, mastodon, bluesky, or an RSS reader. You write your remarks using markwhen and the meridiem editor and they become public entries on remark.ing if your document is shared and has the right entries in its header. More on that below.

👋

hello

Upgraded timeline & free collaborative editing

The timeline has been upgraded in a lot of cool ways!

Reminders & commands

Hello! A couple updates from the past month and preview of things being worked on:

Commands

Blogging with markwhen, the return of pages, and more

I have been working on making markwhen and markwhen.com more of a utility that I can use daily, such that I find its flaws more easily and can make stuff for it that I want as a user. Admittedly I don't make that many timelines but I have found that it is very useful for journaling and blogging. In fact if you're reading this post on re.markwhen.com, it was written it markwhen! How cool is that.

Pages (tabs) are back on markwhen.com, and represent completely separate files. You can have tabs open for browser documents, files on your computer, and cloud markwhen documents all at the same time.

Markwhen CLI

I have published a markwhen cli that you can use to generate markwhen views (single html files) from the command line 🤯.

Installation

Behind the scenes work

I've been working on some more behind-the-scenes stuff with markwhen, which I both like and dislike doing: dislike because it doesn't have any immediate value for users, like because it enables more value for users long-term.

I have been separating the views (timeline/map/calendar) from the editor. At this point, every view is its own standalone application that communicates with the editor via a standard API.

Recurring events

It was suggested that supporting recurring events would be a welcome addition to markwhen, so I added it.

2

Gantt view & autocomplete

"But Rob, I though there was already a gantt view?"

Yes, but this view is even ganttier.

Calendar

There's now a calendar view for markwhen.com and the VS code extension.

2

Maps are back, nesting groups, and markdown-style images

First, the map view is back. Use it to plot out events that have locations associated with them, like so:

VS Code Extension update

The visual studio code extension has been updated with a few features:

• Updated UI to match markwhen.com

J is for Jump, and other updates

I wanted to go over two and a half updates that I have not yet written about in the new UI: jumping, autosave, and collaborative editing.

• Jumping

And we're back!

First off, sorry for the long lull between updates. I recently moved, had covid, and got my finger infected all in the past month. But all that should be behind us now; update cadence should improve.

Frontend update

Markwhen beta

Markwhen Beta

Work is ongoing for a new foundation for markwhen, that will be the new basis for the website and allow markwhen to be integrated into other editors, notably initially VS Code. Aside from supporting other editors, the new version is an upgrade from vue 2 to vue 3 and will have better mobile support, among other things.

VS Code extension

The initial release of the Markwhen VS code extension is out, you can find it here.

To switch between the text editor and the timeline view, select View: Reopen editor with... from the command palette and choose Text Editor.