How webmobtechnologies/react-projects works
Main components
• Each project in the repository (Countdown-Timer, Drawing-App, Github-Profiles, Movie-App, Notes-App, Password-Generator, Quiz-App, Recipe-App, Todo-App, Weather-App, meme-generator, and shortlink-generator) should be represented as an individual component.
• Since some projects are front-end applications (e.g., Countdown-Timer, Meme Generator) and some include backend or mobile-native parts (e.g., Password-Generator, Todo-App, shortlink-generator), classify them accordingly – for example: Frontend components, Mobile/Native components, and Server-side or API components.
Relationships and interactions
• Although these projects generally operate independently, you might want to show that they reside within the same open-source repository and contribute to the broader Hacktoberfest 2020 community.
Architectural patterns and design principles
• For the front-end projects, make note of their typical component-based architecture (for instance, React’s component hierarchy) using patterns like separation of concerns (UI, logic, assets).
• For backend components (like shortlink-generator), emphasize standard MVC or routing patterns, with clear segregation between controllers, models, and routes.
• For full-stack or mobile projects (e.g., Password-Generator and Todo-App that include Android and iOS directories), indicate both the native layer and possibly a shared middle layer (e.g., Redux, if used).
Relevant technologies, frameworks, and libraries
• Frontend frameworks and libraries (e.g., React) for several apps.
• Standard configuration and build tools (e.g., Webpack, Babel, ESLint) mentioned in the file tree for some projects.
• For mobile apps, showcase Android (Gradle, Java) and iOS (Xcode project structure) components.
• Node.js and Express-like patterns in projects like shortlink-generator.