Update press release css and add BR 0.1.8 release

[jholdstock]

Adds a press release for Bison Relay 0.1.8, as well as reviewing formatting for existing press releases.

Closes #1121

[xaur]

I find the "long lines" much easier to work with because they are more "responsive" and auto-reflow in editors and less capable Markdown renderers as shown below. Our Press Releases will not be published as GitHub Releases ofc but it is a good example of what happens when the renderer is not smart enough to join the lines. The problem is best shown on more narrow screens. The same happens in the text editor if its window is made smaller than 80 characters wide.

Am I missing out on some benefits of wrapped lines?

[jholdstock]

We've discussed this before, and all of the reasons there are still holding true.

While it's largely a question of personal preference, it also depends on the type of work and tooling. Developer and terminal tools are often optimized to work with a fixed line length (80 characters has been a standard for developers since ~1950s punch-card programming). Publishing and communication tools are usually better equipped to deal with longer lines. GitHub and git are developer tools which are both better at handling fixed line lengths, so I'd argue we should stick with to developer standards.

[xaur]

Thanks for digging that link. I forgot that, it seems my workflow is too different. I wrote up the differences for myself to not forget it again. I'm good with whatever works best for repo maintainers.