-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add a visual timeline based on history page (created by mogztter) #11
base: main
Are you sure you want to change the base?
Conversation
- created with Excalidraw - add optimized image, thanks to tinypng.com
Looking at the timeline again, I think we could improve it by using three "streams"
We could also probably use dynamic column width depending on how much happened in a given year (similar to https://recherche.julie-blanc.fr/timeline-publishing/) |
And if we really need to attach an event to Asciidoctor Ruby, AsciidoctorJ or Asciidoctor.js we could use a color code (but I don't think that would be necessary) |
I also added some more detail to the timeline in the docs that will hopefully make it easier to find the information to add. |
Btw, there's now an Excalidraw plugin available for IntelliJ. https://plugins.jetbrains.com/plugin/17096-excalidraw-integration |
Here's another proposal:
I didn't add all the history but I think it gives us more room. |
I like the direction you are headed.
That really was a busy time 😱 I think if we're going to give AsciiDoc.py a row, we need to address when Asciidoctor became the official reference implementation of AsciiDoc and steward of the AsciiDoc language definition (before the initial contribution). We could also mention when AsciiDoc.py was moved to asciidoc-py (thus vacating the asciidoc org on GitHub). |
One idea to make more room would be to make time vertical instead of horizontal. There are only a few categories and lots of years, so it would give us more room to groooooooooooooow. |
Another idea I had was to use the Asciidoctor row as a graph axis to draw the download/usage numbers.
|
Indeed!
We could add a chronological point in the AsciiDoc.py row to mention that the project was declared "legacy implementation" (maintenance mode).
I know it's a big deal for us right now but not sure if we should include it.
I would prefer to keep the timeline vertical. We can squeeze or stretch columns as needed. |
💯 |
That is absolutely fascinating. What a brilliant idea. 💡 |
Extracted from #5