front-end-guide
react-atomic-design
Our great sponsors
front-end-guide | react-atomic-design | |
---|---|---|
2 | 8 | |
15,082 | 1,730 | |
0.1% | - | |
0.0 | 0.0 | |
11 months ago | over 1 year ago | |
JavaScript | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
front-end-guide
react-atomic-design
-
Atomic design
https://github.com/danilowoz/react-atomic-design maybe this as an example
-
The Art of Writing Ugly Code That Works, Then Beautifying It for Optimal Functionality
Once I started learning about software development best practices such as the SOLID principles, Atomic Design, abstraction and design patterns my first instinct when writing any piece of new code was to write beautiful code from the very beginning. I wanted to make sure that my code was readable, maintainable, and scalable. However, I quickly realized that this approach was not only time-consuming but also led to frustration. I was spending too much time trying to make my code look perfect, and not enough time focusing on getting the job done. This got worse when I started working on larger projects with more complex code and TypeScript, where typing can be a bit tedious for reusable components.
-
100+ Must Know Github Repositories For Any Programmer
2. React Atomic Design
-
Questions about using useCallback
React's biggest selling point is _declarative composability_. If you want to split functionality into other components, _just make other components_. It is common (and probably best) practice to design components [atomically](https://danilowoz.com/blog/atomic-design-with-react). If you need to share state between them, _hoist that state to a common ancestor_ component and pass it down through props. If you need props from a much more general location, you can look at using contexts, although be careful about this as they have some significant drawbacks.
- Atomic Design Examples?
- Atomic design & react question
-
React architecture
I feel like this frees you up to use things like Atomic design with your components, which helps on the more folder-structure side of things.
- [React] How do you structure your Components directory? I have a lot of components now and I have no idea how to separate them into different directories.
What are some alternatives?
vanilla-javascript-boilerplate-spring-boot - A boilerplate of Vanilla-JavaScript, SCSS with Webpack for MPA (multi page application)
boilerplate - Responsive CSS, HTML and JavaScript front-end starting point, plus components!
express-webpack-react-redux-typescript-boilerplate - :tada: A full-stack boilerplate that using express with webpack, react and typescirpt!
react-neon-ui-demo - Demo-documentation for react-neon-ui
dr4ft - Multiplayer Online MTG Draft and Sealed Simulator
borrow-ui - A simple component library made with React.
ipfs-webui - A frontend for an IPFS Kubo node.
jatayu - A CLI tool to generate production-ready hand-made React Apps.
react-d3-speedometer - React Speedometer component using d3.js ⚛️
eleventy-react - Use React components in Eleventy.
SaltGUI - A web interface for managing SaltStack based infrastructure.
express-react-boilerplate - (Deprecated) 🚀🚀🚀 This is a tool that helps programmers create Express & React projects easily base on react-cool-starter.