| 8 Mar 2024 |
 @johannes.kirschbauer:scs.ems.host | * But Is this website really what we'd like to give to our users?
many off-the shelf rendering frameworks are really awesome (compare to our website), and they dont require us to maintain our own markdown parser and instead have more freedom because their community maintains the framework, while we can focus on writing documentation (and maybe add some plugins) | 10:08:26 |
 @pennae:matrix.eno.space | have you considered: it took multiple years to do one migration, it has regressed, and it was only possible because we didn't use off-the-shelf components or we would've regressed even more. | 10:09:04 |
| @pennae:matrix.eno.space | do you really want to bind up another few years worth of work after the first migration hasn't even been shipping for six months | 10:09:27 |
| @pennae:matrix.eno.space | it's so far from "just drop in another framework", we're not sure you even understand what you're setting yourselves up for. | 10:10:18 |
 danielsidhion | My approach to looking into other frameworks is based on a simpler thought: we currently have 5k lines of custom code to render the manuals into what we see online. As far as I know, there is currently not a lot of flexibility in the tool to produce things in different ways, which means that if we want to change something, we'll need to go change the code. This is a big overhead that makes it hard to add improvements to the manuals. So I decided to look into other frameworks to see how much of our needs they can satisfy out of the box, and how much extra effort would be needed to satisfy the other needs. Because honestly, I actually find borderline absurd to assume that nobody out there has been able to solve some of the same problems we have into a tool that's more popular, has people to maintain it, and has a bigger ecosystem of documentation/plugins/knowledge to source from | 10:11:24 |
| @pennae:matrix.eno.space | most people out there are not multiple distros in a trench coat | 10:12:29 |
| danielsidhion | But our documentation doesn't have to follow suit | 10:13:54 |
| @pennae:matrix.eno.space | we can only stress again: make sure you're familiar with the problem domain before trying to Be Like The Others. | 10:14:32 |
