704 karma · joined April 3, 2012
Business: https://www.joyapp.com
I think this is great, especially because it's OSS.
But if you want to really outshine Strong and Heavy, I'd look into "auto progression" of exercises. Too often, people just... log the same thing for years. Some RIR / RPE / linear progression would keep people motivated.
[1] joyapp.com
But the ecosystem of React, including UI libraries, charting, forms, and so forth, is enormous.
In theory, you could swap in Svelte in there.
It swaps the templating engine for React. But still server side and using all the Django features you know and love. No SPA needed.
But to me, writing my markup in JSX (really, TSX with TypeScript) and using scoped CSS solutions was too good to pass up. I just couldn't bear writing text-based templates.
That's why I built Reactivated: combining the best of both worlds. Server-rendered, simple markup — albeit still in TypeScript — but you can add interactivity as needed.
Of course, HTMX is far less opinionated and framework-agnostic. So it can be used with any number of libraries / stacks.
[1] https://www.reactivated.io
[2] https://www.reactivated.io/documentation/philosophy-goals/#t...
[3] https://www.reactivated.io/documentation/philosophy-goals/#r...
[4] https://htmx.org/essays/how-did-rest-come-to-mean-the-opposi...
It's not drag and drop, but abstracts away all tooling and let's just get to just writing your code. Either in React or in Django templates.
Eventually, if you have any dynamic behavior, you're going to end up rebuilding a lot of what React does for you.
Full disclosure: I'm the creator.
See here: https://github.com/silviogutierrez/reactivated/blob/main/dev...
https://github.com/silviogutierrez/reactivated/blob/main/dev...
https://github.com/silviogutierrez/reactivated/blob/main/dev...
This does make testing a lot easier, as the server response is identical to the hydrated client.
Of course there's many ways around this, but doing them in a declarative, type-safe way is not trivial when using Django templates.
The docs site itself: www.reactivated.io . Notice no JS loaded on the client side. It's purely SSR. The code is in the repo under /website.
My personal blog: www.silv.io
And my business: www.joyapp.com
I don't track others that use it, but hopefully they're out there!
It incorporates most of these best practices, along with React server side rendering in addition to regular Django templates.
Full disclosure: I'm the creator.
Reach out if you have any questions! Email is on my GitHub profile.
It's like HTMX but uses React, and the JS bits are rendered on the server. You can then hydrate on the client.
The Reactivated docs site itself uses the project: https://github.com/silviogutierrez/reactivated/tree/main/web...
Built with Django + React SSR using https://www.reactivated.io
With that out of the way, I think having more opinionated Django frameworks is a great thing. Particularly around styling and forms.
I also think it's interesting to try to "productize" (I think there's a better word) what is often done as consulting. That is, bottling up and selling experience. So while the price may seem high, there's a ton of wisdom behind it. An experienced Django consultant is easily thousands of dollars per week.
I wish you the best!
Shameless plug here: https://www.reactivated.io/documentation/why-nix/
I'm not saying there's no downside, I'm asking against the downside of engineering cost. And that itself carries risk of failure when you go live. It's not guaranteed.
[1] AWS is so ubiquitous though, that half the internet would be affected so it makes it less individually noticeable.