After create a React project by some CLI tools, we need to create some folders to structure the project. React official said they doesn’t have opinions on how you put files into folders. In my personal opinion, I recommend to use the following folder structure.
There are many ways to create a React project. In this post, I will introduce the commonly used methods for creating a React project.
Organize Docker compose.yaml examples here.
Organize Dockerfile examples here.
In this post, I will cover the technologies that should be used in new software projects in 2025.
Creating a Dockerfile is a critical part of building container images. Following best practices not only leads to optimized images but also enhances security and maintainability. The following are some best practices to consider when writing your Dockerfile.
In this post, I will cover Docker’s common use based on my experience.
Component files: Use CamelCase. E.g. MyComponent.js
Non-component files (like helpers, hooks, or utilities): Use kebab-case or camelCase. E.g. useCustomHook.js or myUtility.js.
Custom hooks files: with a use prefix. E.g. useFetch.js, useForm.js.
Use kebab-case for folder names. E.g. my-folder, components, utils.
Test folder name: __tests__
Often there is a lot of trivial code in open-source projects that we don’t need to read. To read a Java open-source project, the most important thing is to understand the core functionalities of the project.
In the post, I will cover common tools for reading source code.