redux-essentials-example-app VS scaffold-eth

You're right, it is related. But I think that Flux- and ELM-like architectures are making it even worse by forcing any "external" interaction to became the gap. Look how they suffer when it comes to executing any async operation like network request. Initially we have this relatively simple framework, but then we had to add "Middleware" to just run network request (which is a good example of the Remainder issue). I love the idea behind these architectures, which makes logic more predictable and testing way easier. I even was using them by myself. But now they looks like something turned inside out for me. I believe we could do better. I'm finishing my proposal right now. It will take couple more weeks to edit and translate it, but soon I'll show what I mean.

Hi, I maintain Redux and wrote most of our docs (including our current tutorials).

Can you give some details on which parts of our docs you feel are "incomprehensible"? I'm curious which specific pages you've been looking at, and for what purpose.

We've tried to organize the docs using the "Documentation System" approach described at [0]: Tutorials for teaching step-by-step, Explanations and How-To guides for specific topics, and References for API details.

Generally we want people to go through our "Redux Essentials" tutorial [1] as the primary way to learn how to use Redux correctly. It teaches "modern Redux" patterns with Redux Toolkit as the standard way to write Redux logic (including RTK Query for handling data fetching), and React-Redux hooks in components.

I'm genuinely interested in feedback on what explanations aren't clear and how we can improve things!

[0] https://documentation.divio.com/

[1] https://redux.js.org/tutorials/essentials/part-1-overview-co...

https://redux.js.org/tutorials/essentials/part-1-overview-concepts (covers how to use Redux Toolkit and RTK Query)

If you want to learn to develop apps for the EVM (Thats Ethereum, Polygon, xDai, Aurora and many others) then you should read through the code in the various branches of https://github.com/austintgriffith/scaffold-eth for really good full-stack examples

git clone [https://github.com/austintgriffith/scaffold-eth.git](https://github.com/austintgriffith/scaffold-eth.git) challenge-2-token-vendor cd challenge-2-token-vendor git checkout challenge-2-token-vendor yarn install

In this blog post, I’m going to cover the first scaffold-eth speed run project: creating a Staking dApp. If you want to know more about scaffold-eth and my current journey in the web3 world you should read my previous article: My journey in Web3 development: scaffold-eth.

https://github.com/austintgriffith/scaffold-eth is a great ethereum boilerplate project that uses yarn workspaces in a monorepo, its a pretty standard practice that I've seen in the NFT/blockchain dev space.

I'm a fullstack JS developper, i've working and looking heavily into building on ethereum, so this is my first dive into the space. I would love some feeback from more senior devs on this, on the React and Dapp part. It is heavily based on scaffold-eth (and some Uniswap-interface code reading) so I'd recommend starting there if you're starting out rather than my starter, the docs and content there are first class. The stack is just the stack i am used to working with: Tailwind UI, Typescript and Redux Toolkit, and more. I'll be adding more examples other than the Greeter soon. Also i am for hire if you're looking for junior Dapp devs :) Thank your for your time !