I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

@federico3 As someone with a hat in this, it's because other formats are pretty arbitrary too. #Markdown was designed to still be readable as plaintext -- something it fails at, yes, with that awful link syntax -- but the same complaint can be levied against ReST, #AsciiDoc etc which all have arbitrary and unusual syntax patterns that work for a parser but don't necessarily work for plaintext.

And plaintext, unlike programming languages, depends more on aesthetic principles that are more personal. Programmer may argue about line-break before `{` but the code still compiles -- that's not the case with markup languages!

For my databaseless forum I invented a markup syntax where the output can be copied and pasted as valid input: just leave the `*` & `_`'s in and style with CSS, it works surprisingly well. For ReMarkable I hewed closer to plain-text aesthetics but it needs some revisions, and it's difficult to swap one bad syntax for a better one down the line when the format is already in wide use.

Markdown would have seen a decline, until GitHub took off. I think that really cemented its modern usage more than anything. You can stab it with your steely knives, but you just can't kill the beast 🤷

@nielsk Think of the Family Guy meme to remember it. Markdown is the weird one.

#markdown #orgmode #asciidoc #plaintext