Find Us An External Tool To Generate Timeline Images as .png

If you're interested, assign it to yourself.

paste the link to the external tool's website and/or docs as a comment to this issue, and attach a `.png` of some kind of timeline example generated with the tool. No need to spend too much time on this.

What I think Makes Sense a portable timeline artifact is a handy thing to have for a project. The format: an image. Just throw it into a google doc, a power point slide, a website, or whatever you want. But sometimes you want to start with a rough timeline, and then change it frequently. It would be annoying if generating the changed image required expertise or time. So, we can find a tool that's simple to use, free, and produces a pleasing timeline.png asset. Online tools are fine, too. It doesn't have to be collaborative. Dimensions (width, height)? Whatever you want, if you think it's a reasonable thing to do in the context once you finish reading this GitHub Issue.

Where We're Going to Use It In the Context Of THIS SPRINT, and the next two sprints the point of the timeline artifact isn't necessarily to iron in stone our schedule so that any deviation is punishable by death and frowned upon. The task and functionality that this particular GitHub Issue concerns is using the timeline asset/artifact as a justification mechanism for external stakeholders. So, outside the team, some external stakeholder comes, says, "We're worried about this critical project. We want some justification that things are on schedule. What do we do? Well, we use the tool to generate the static asset using either (a) supplied values when the image is created, or (b) edited image after creation. And then we embed that document with some text content and supply it to the external stakeholder as justification. And images tend to be more likely to have a stronger persuasive force, which could be useful, or not.

A Thought To Consider

Maybe we shouldn't be using .png format. Wouldn't it make more sense to have one copy of a resizable vector image? Why? Because it's possible to lose some quality for some .png, while vector images are generated from

Response To The Thought

In theory, it would be better to have a vector image that could never lose any properties that reduced some quality metric when resized, other things being equal (I think I'm remember this right, could be off). But I think in this context, other things aren't equal. Why? I've noticed that there tends to be a fair amount of freely available software/online web tools that seem to work okay for my simple image editing needs. for .png. However, not so much for .svg image format. I find .svg files more complicated to deal with, and sometimes I get weird results. Given that the processes and ecosystems of online '.png' manipulation are simpler and more reliable than their .svg counterparts, I suggest we opt for working with .png

cmneal26 / Tech-Writing-Project