New documentation

[proyb6]

I do find the existing documentations a little hard to read and sometime struggle when I need to trace back the page, while I have been using Astro for my projects, reading their documentations is a breeze that I love how organize is their docs.

https://starlight.astro.build/

HTTP Archive doc uses Starlight
https://har.fyi/

Would this be useful for Echo doc, I'm aware the previous creator no longer working on Echo but really need a refresh on the site.

[aldas]

I am skeptical about Starlight but similar Hugo template would be fine. With absolute minimal js dependencies. JS ecosystem is bottomless maintenance time sink.

[aldas]

@vishr maybe you want to organize something to be done with website design?

[OneSeven]

To be honest, I don't think the old site is worse than the new one. The overall schedule of the old site is much simpler than that of the new site. The default expanded directory has a small space between the directories, which can be quickly located. The visual style of the new site is too bright (although there are nighttime model), the theme content is too empty, and a lot of screen space is wasted. In general, it is better to stand quickly than to stand, capable and efficient。
@vishr Seriously, the new docs are abysmal compared to the old ones

[vishr]

@OneSeven Thanks for your feedback. Our intention is to shift away from using a custom-built frontend framework and instead depend on a widely supported and regularly updated end-to-end (e2e) tool. Docusaurus appears to be a suitable choice for this purpose. It allows flexibility in modifying the overall theme and CSS, and we are open to contributions. Currently, I am focusing on implementing the search functionality.

[aldas]

@vishr could you check https://github.com/labstack/echox/security/dependabot these alerts are being sent every day by email.

[vishr]

Sure

[vishr]

The search is back.

[OneSeven]

The website is live. I haven't changed the content.

PS: I am still working on search and redirects (if possible)

@aldas

Concerned about the recent launch of a new documentation site,
However, the search-related functions are not perfect yet.
It is recommended to switch to the old documentation site, and wait for the new documentation site to improve before switching over

[proyb6]

Understand on the JS ecosystem, my ideas is that the docs can provide some simple UI components e.g. React, Vue, etc to interactive demostrate how Echo can interact with Astro and other frontend with some recipes and examples.

I like the new doc, but using Docusaurus with 122KB of JavaScript/React serving on home page and docs with no interactivity seem a lot.

[aldas]

Lets not get into discussion of JS framework/library. This is bottomless timesink as lifetime of a JS lib is like fruit fly - short. Discussions like that are almost bikeshedding as hart part here is actually creating helpful/useful documentation. JS is convenient distraction for the tech-people from the hard parts.

Custom stuff is big no from my side - I really do not want to maintain from my free time anything related to frontend quirks. In that sense Hugo was excellent as if required almost zero maintenance.

---

about 122KB, maybe there is a way to treeshake Docusaurus js to get smaller files or something like that?

[proyb6]

I can understand the effort to maintain documentation.

Assume Docusaurus is using ReactJS as a runtime, the large starting bundle size will only grow and no way to treeshake it. Hugo is fine since there aren't any interactivity.

If you plan to extract your contents as fast as possible, DivMagic is handy for my project.
https://divmagic.com/