react-atomic-design VS public-apis

https://github.com/danilowoz/react-atomic-design maybe this as an example

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.

2. React Atomic Design

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.

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.

For inspirations on what type of agents I should build, I turned to the Public APIs GitHub repository which has a curated lists of free APIs. I narrowed my search for an API that does not require sign-up or an API key and returns useful information. I ultimately decided to use the Free Currency Exchange Rates API, which seemed promising upon some basic testing.

✅ public-apis/public-apis : https://github.com/public-apis/public-apis

Public-Apis Github Repo — A list of free public APIs.

Interesting thread at https://github.com/public-apis/public-apis/issues/3104

Use curl to access a free public API and get a random joke, cat fact, or whatever.

I remember the forking of https://github.com/public-apis/public-apis and the long git issue discussions. The company owning the repository stopped maintaining it but didn't give up control either. Over the years you've put in a lot of work in publicapis.dev and that is much appreciated.

Also, that isn't really a list of "contributors", but of "organisations with the most stars". Those are different things.

For example "public-apis"[1] didn't "contribute" anything as that's not a person, and looking at GitHub[2] there are a bunch of substantial contributors (the person who created the organisation/repo only has 12 commits by the way);

[1]: https://opensource-heroes.com/o/public-apis

[2]: https://github.com/public-apis/public-apis/graphs/contributo...