full-blockchain-solidity-course-py VS hardhat-template

I really liked this course for learning everything. https://www.youtube.com/watch?v=M576WGiDBdQ There are 13 lessons in it if u look at the description. So each lesson is an hour and a half about That gets you solidity + front end experience though https://github.com/smartcontractkit/full-blockchain-solidity-course-py Follows along with the video

View on GitHub

Also try to search for your problem here https://github.com/smartcontractkit/full-blockchain-solidity-course-py/discussions

I personally like brownie because I actually like Py and the best course I found online was using it. If you decide to go with Brownie I recommend it, Patrick is an awesome dude and the course is high level: https://github.com/smartcontractkit/full-blockchain-solidity-course-py

A lot of information is packed into this course, so don't do it all in one go! Remember to take breaks, and jump into the GitHub discussions and ask questions, or on Stack Overflow! This is easily one of, if not the most dense blockchain tutorial on the planet.

I have decades of experience as a programmer (.Net, php, JS, React) , but I have only completed Cryptozombies and I am halfway through FreeCodeCamp.org 's Full Blockchain Solidity Course lessons (featuring Ethereum, Solidity, Python, brownie - which is excellent btw).

I started with Cryptozombies, and now I am coding along with Free Code Camp's Solidity Blockchain Smart Contracts course.

Github Resources: https://github.com/smartcontractkit/full-blockchain-solidity-course-py

It seems like every single week, I see things about Foundry. As someone that has been using a fairly standard Hardhat template for my projects the past year, I feel like this gets the job done, but I am wondering what I am missing?

To help getting started easier I am looking into some boilerplate starter kits such as https://github.com/paulrberg/solidity-template etc. Basic question, but what is the best practice in terms of organizing your smart contract dev stuff such as .sol files, hardhat, solhint, solcover, etc. with your front-end (website) dApp code? Do you keep everything in one repository? Do you keep them separated? The front-end part (let's say Sveltekit for example) and ethers.js need the ABI json right? When you deploy your front-end website and are keeping everything in one repo, should you exclude your contract files from the build? I suppose the JS framework will already exclude folders like /contracts that are in the root from the build.

I also really like this template for a web3+React website with a simple connect button: https://github.com/PaulRBerg/solidity-template

..and if you are looking for a general toolchain I really love the starter template here: https://github.com/PaulRBerg/solidity-template