|
| 1 | +### Project ideas |
| 2 | + |
| 3 | +#### LLM-Integrated Quiz for DailyCode |
| 4 | + |
| 5 | +##### Summary |
| 6 | + |
| 7 | +DailyCode is a core feature of 100xDevs, designed to help developers practice and refine their coding skills. This project aims to integrate an LLM into DailyCode so that for every new module added, the LLM automatically generates quizzes. Additionally, there will be a dedicated quiz section where time-based quizzes are created, allowing users to test their understanding effectively. |
| 8 | + |
| 9 | +##### Expected outcomes |
| 10 | + |
| 11 | +- LLM integration to generate quizzes dynamically for each module. |
| 12 | +- A separate quiz section with time-based quizzes. |
| 13 | +- A structured database for quiz storage and tracking user progress. |
| 14 | +- A well-documented and scalable implementation. |
| 15 | + |
| 16 | +##### Implementation |
| 17 | + |
| 18 | +This project will require integrating an LLM API into the DailyCode platform. The implementation will include designing a robust quiz generation system, building a UI for the quiz section, and ensuring the quizzes align with the added modules. The backend will store quiz data, track progress, and manage timing logic. |
| 19 | + |
| 20 | +##### Skills |
| 21 | + |
| 22 | +- TypeScript |
| 23 | +- PostgreSQL |
| 24 | +- Recoil (State Management) |
| 25 | +- TailwindCSS |
| 26 | +- Monorepo architecture |
| 27 | +- LLM APIs |
| 28 | + |
| 29 | +##### Mentors |
| 30 | + |
| 31 | +- **Lead:** TBC |
| 32 | +- **Support:** TBC |
| 33 | +- **Support:** TBC |
| 34 | + |
| 35 | +##### Size |
| 36 | + |
| 37 | +Expected size of project: **approximately 350 hours.** |
| 38 | + |
| 39 | +##### Difficulty rating |
| 40 | + |
| 41 | +High |
| 42 | + |
| 43 | +--- |
| 44 | + |
| 45 | +#### Blogging Platform with Admin & Super Admin Dashboards |
| 46 | + |
| 47 | +##### Summary |
| 48 | + |
| 49 | +This project aims to transform 100xDevs into a blogging platform where users can write articles, submit them for review, and get them published by admins. An admin and super admin dashboard will be created to manage articles, approve/reject submissions, and oversee the platform. |
| 50 | + |
| 51 | +##### Expected outcomes |
| 52 | + |
| 53 | +- A blogging system where users can write and submit articles. |
| 54 | +- An admin dashboard for managing submissions. |
| 55 | +- A super admin dashboard with higher-level controls. |
| 56 | +- A seamless publishing workflow with role-based access control. |
| 57 | + |
| 58 | +##### Implementation |
| 59 | + |
| 60 | +The project will involve building a CMS-like structure within 100xDevs. The frontend will allow users to draft and submit articles, while admins will have tools to review and publish content. Super admins will oversee all activities. The backend will manage article storage, user roles, and approval workflows. |
| 61 | + |
| 62 | +##### Skills |
| 63 | + |
| 64 | +- TypeScript |
| 65 | +- PostgreSQL |
| 66 | +- Recoil (State Management) |
| 67 | +- TailwindCSS |
| 68 | +- Monorepo architecture |
| 69 | +- Role-based access control |
| 70 | + |
| 71 | +##### Mentors |
| 72 | + |
| 73 | +- **Lead:** TBC |
| 74 | +- **Support:** TBC |
| 75 | +- **Support:** TBC |
| 76 | + |
| 77 | +##### Size |
| 78 | + |
| 79 | +Expected size of project: **approximately 350 hours.** |
| 80 | + |
| 81 | +##### Difficulty rating |
| 82 | + |
| 83 | +Medium |
| 84 | + |
| 85 | +--- |
| 86 | + |
| 87 | +#### UI/UX Improvement and Codebase Sanitization |
| 88 | + |
| 89 | +##### Summary |
| 90 | + |
| 91 | +This project focuses on improving the overall UI/UX of the 100xDevs application, ensuring a better user experience while optimizing the codebase for maintainability and scalability. |
| 92 | + |
| 93 | +##### Expected outcomes |
| 94 | + |
| 95 | +- A modernized and visually appealing UI with TailwindCSS. |
| 96 | +- Improved user experience with consistent design patterns. |
| 97 | +- Refactored and optimized code for better performance. |
| 98 | +- Improved accessibility and responsiveness. |
| 99 | + |
| 100 | +##### Implementation |
| 101 | + |
| 102 | +This will involve auditing the current UI/UX, identifying areas for improvement, and redesigning critical pages. The codebase will be refactored to improve readability, performance, and maintainability. Best practices for TailwindCSS and TypeScript will be applied. |
| 103 | + |
| 104 | +##### Skills |
| 105 | + |
| 106 | +- TypeScript |
| 107 | +- TailwindCSS |
| 108 | +- UI/UX Design Principles |
| 109 | +- Frontend Optimization |
| 110 | +- Monorepo architecture |
| 111 | + |
| 112 | +##### Mentors |
| 113 | + |
| 114 | +- **Lead:** TBC |
| 115 | +- **Support:** TBC |
| 116 | +- **Support:** TBC |
| 117 | + |
| 118 | +##### Size |
| 119 | + |
| 120 | +Expected size of project: **approximately 175 hours.** |
| 121 | + |
| 122 | +##### Difficulty rating |
| 123 | + |
| 124 | +Easy |
| 125 | + |
| 126 | +--- |
| 127 | + |
| 128 | +### Project proposal: your own idea |
| 129 | + |
| 130 | +You can also propose your own idea. Your proposal should: |
| 131 | + |
| 132 | +- Have a concrete task. |
| 133 | +- Give a solid idea of what will constitute success. You tell us. |
| 134 | +- Present a detailed design specification. |
| 135 | +- Give insight into who you are. If you propose something ambitious, convince us that you are up to the task. |
| 136 | +- Give insight into your previous projects and experience. |
| 137 | +- Tell us about your experience with TypeScript, TailwindCSS, PostgreSQL, and Recoil. |
| 138 | +- Provide a schedule, including a detailed work breakdown and major milestones. |
| 139 | +- Contain your motivation and curriculum vitae. |
| 140 | + |
| 141 | +#### Note: |
| 142 | + |
| 143 | +- The project ideas above are starting points for your submission, but aren’t enough by themselves. You’ll need to come up with a more complete project plan and use your own words. |
| 144 | +- Do not feel limited to the project ideas above. |
| 145 | +- If you have a project idea not listed, please direct message the organization admins. They can evaluate its feasibility and pair you with a mentor for initial feedback. |
| 146 | + |
| 147 | +### Project proposals should fall into one of three categories: |
| 148 | + |
| 149 | +1. Work on 100xDevs itself (core product). |
| 150 | +2. Work on tools to support 100xDevs. |
| 151 | +3. Development of third-party integrations or libraries. |
| 152 | + |
| 153 | +### The project you propose should be: |
| 154 | + |
| 155 | +- Useful for 100xDevs. |
| 156 | +- A single well-scoped project. |
| 157 | +- Achievable within the GSoC timeframe. |
| 158 | +- Something the core developers can help mentor you on. |
| 159 | + |
| 160 | +#### Template for submitting your project idea: |
| 161 | + |
| 162 | +``` |
| 163 | +### [Project Idea Title] |
| 164 | +##### Summary |
| 165 | +[Brief description of the project.] |
| 166 | +
|
| 167 | +##### Expected outcomes |
| 168 | +[List of key deliverables.] |
| 169 | +
|
| 170 | +##### Implementation |
| 171 | +[Outline of how you plan to implement the project.] |
| 172 | +
|
| 173 | +##### Skills |
| 174 | +[List the key technologies required.] |
| 175 | +
|
| 176 | +##### Mentors |
| 177 | +- **Lead:** |
| 178 | +- **Support:** |
| 179 | +
|
| 180 | +##### Size |
| 181 | +Expected size of project: **approximately 350 / 175 hours.** |
| 182 | +
|
| 183 | +##### Difficulty rating |
| 184 | +Low / Medium / High |
| 185 | +``` |
0 commit comments