#72 Writing your styles in JS ≠ writing inline styles
this week's favorite
I recently tested whether client-side rendering would prevent websites from being crawled by search engine robots. As my article showed, React doesn’t seem to hurt search engine indexing at all. Now I’m taking it to the next level. I’ve set up a sandbox React project to see exactly what Google can crawl and index.
We supply a react implementation antd following Ant Design specification, which designed to help developing RIA such as dashboards or other enterprise-like complex UI needs.
Redux is a state management library that lets you connect directly to application state from anywhere in your app. It also allows you manipulate application state from anywhere in your app. But, to work its magic, Redux requires that your app have a single data store.
As our applications grow, we often find that file structure and organization to be crucial for the maintainability of application code. What I want to do in this post is to present three organizational rules that I personally follow on my own projects. By following the rules, your application code should be easier to reason about, and you will find yourself wasting less time on file navigation, tedious refactoring, and bug fixes.