herodot:1.0.0

[gnist-dev]

I am submitting

• a new package
• an update for a package

Description:

Added the following fields for customizing the timeline:

• event.offset field for setting the length of an event's vertical line mark
• logic for taking into account whether an event is above or below the timeline, and how that should affect it being displayed
• replaced the timeline.spanheight field for eventspan.spanheight field, so that it can be set on a per time-span basis (breaking backwards compatibility)

also:

• bumped cetz from 0.4.1 to 0.4.2

[elegaanz]

Two small remarks to improve your README. The second is really more of a suggestion. We didn't really have these rules/tips in our package review process previously, which is why I didn't suggest them for the previous versions.

[elegaanz]

Actual image descriptions would be appreciated here. They don't have to go into much detail, but should convey the main idea behind the image to people relying on screen readers (or for whom the image couldn't properly load, for example if they have poor internet connectivity). You can imagine that you are reading the README to someone on the phone, and you have to describe what the images show with words, this generally helps to come up with a good alternative text.

[elegaanz]

I think it would be nice to link to this file in the README too, so that users can use this file as a sort of reference: they can scroll through the PDF to find a timeline configured the way they want, and then navigate to the corresponding section of the source to copy it.

If you do so, updating this import to @preview would be better, as it would allow people to just copy/paste the file to get started, and get a valid result without further modification.

[elegaanz]

Great, thank you!