Mark Bakhit

In order to take advantage of why users want SSR (namely SEO), IDOM might need to be modified to use HTTP instead of websockets.

I did some investigation and here's what I came up with. ## The Ugly - The currently accepted "best methods" for SSR within React seems to rely frameworks such as...

@rmorshea I've discovered react actually has an API for this. https://beta.reactjs.org/reference/react-dom/client/hydrateRoot

I don't think we should use that pre-rendering API. If we do, then 1) We are making the assumption that IDOM knows where HTML static pages should be stored. -...

I've been doing some thinking on this. I think we might need to take a "zero rehydration" policy and always double render (HTTP followed by WS render). Since the HTTP...

I created a draft of the new docs structure using `mkdocs`. Used `django-idom` docs as the initial template. https://github.com/Archmonger/idom-docs Currently, the only thing that has been developed is the navigation...

But this makes a lot of linters and IDEs not happy. We shouldn't have to make people modify their linting config to use ReactPy without getting warnings.

The best way of doing this would be using vscode configuration, which would automate the docker setup. Only thing users would need to do is install docker. On Windows, that...

Not really sure if this belongs in v1 or v2. Could go either way. IDOM is _technically usable_ without this, but only Django-IDOM feels convenient to develop in. We did...

@rmorshea We still need to enable precommit on the repo