update the website?

[evertbouw]

Is it worth fixing the website, should it be redone, or taken down?

Personally I'm fine with just readmes on github. I don't want to put too much effort into a website because in 2024 I'd recommend looking at a bunch of different solutions before reaching for redux middleware.

[MaximeBernard]

With Redux releasing a new major version, maybe it will regain a new audience.

Also, I'd be interested to know how many visitors the website has (I saw GTag). With 225,150 weekly downloads on NPM, some people maintaining legacy projects might still be happy with the current website.

That being said, I agree we shouldn't put too much effort into it. I have no idea how the website is updated but maybe updating some MD files would be enough?

[evertbouw]

There were some scripts to turn the md files into a website, it's published by pushing to https://github.com/redux-observable/redux-observable/tree/gh-pages

[jayphelps]

Yeah I'm not even sure if building the website works anymore as it depending on an old version of gitbook that I recall was deprecated. Hopefully it doesn't require any of that company's server APIs.

Here's a breakdown of visits from Nov 7th-Dec 7th.

[piyushchauhan2011]

I was wondering we can use docusaurus or vitepress and manage different redux-observable version docs efficiently. I would be happy to help since we have been using redux-observable since 1.0.0 and now running 3.0.0-rc2 for quite some time now

[evertbouw]

Yes some help to get a new docs site running would be very welcome. The text in the docs can use a rewrite but let's call that out of scope for now. Hopefully we can keep the same paths or at least redirect (for SEO?). We won't need a blog. The most fancy feature I can think of is an interactive example that can be an embedded codesandbox or MDX widget.