Sebastian Beltran

@expressjs/docs-wg, what do you think? Should we stick with Jekyll? I don't want to block the maintenance of the page either, that's why I want to know, so we can...

Probably, we need to see the support GitHub wants to give to Jekyll. I mean, GitHub hasn't updated [pages-gem](https://github.com/github/pages-gem) in a while, Jekyll 4 (which will likely make my build...

For now, we are going to stick with Jekyll since we will be using Crowdin for i18n (which means we no longer have to copy and paste), and we have...

For those who aren't aware, express is planning a complete redesign. That's why I'm reopening this discussion, we need to clearly define the stack we're going to use for the...

> What maintainability issues are you running into currently? That the styles file is 1200 lines long? It's a very large and somewhat disorganized file, so if we can separate...

>[2025-02-13 00:23:13] ERROR /css/themes/light-theme.css' not found. >LiveReload: Browser connected I forgot to remove that request from the head, sorry about that. I've deleted it in this pr.

I'm trying not to delete or modify any CSS styles, as these are style changes of code.

This is not a priority, and it shouldn't be a dependency for creating PRs. I'm going to put it in draft for now, and I'll come back to it later.

We still need to make the TOC generate automatically, we can use this [plugin](https://rubygems.org/gems/jekyll-toc/) to achieve that

this would help reduce the existing layouts and would prevent the need to manually write the TOC (which is prone to errors). It would also reduce the maintenance load on...