You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
6
9
7
##### Expected outcomes
10
-
11
8
- LLM integration to generate quizzes dynamically for each module.
12
9
- A separate quiz section with time-based quizzes.
13
10
- A structured database for quiz storage and tracking user progress.
14
11
- A well-documented and scalable implementation.
15
12
16
13
##### Implementation
17
-
18
14
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
15
20
16
##### Skills
21
-
22
17
- TypeScript
23
18
- PostgreSQL
24
19
- Recoil (State Management)
@@ -27,40 +22,32 @@ This project will require integrating an LLM API into the DailyCode platform. Th
27
22
- LLM APIs
28
23
29
24
##### Mentors
30
-
31
-
-**Lead:** TBC
32
-
-**Support:** TBC
33
-
-**Support:** TBC
25
+
-**Lead:** TBC
26
+
-**Support:** TBC
27
+
-**Support:** TBC
34
28
35
29
##### Size
36
-
37
30
Expected size of project: **approximately 350 hours.**
38
31
39
32
##### Difficulty rating
40
-
41
33
High
42
34
43
35
---
44
36
45
37
#### Blogging Platform with Admin & Super Admin Dashboards
46
-
47
38
##### Summary
48
-
49
39
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
40
51
41
##### Expected outcomes
52
-
53
42
- A blogging system where users can write and submit articles.
54
43
- An admin dashboard for managing submissions.
55
44
- A super admin dashboard with higher-level controls.
56
45
- A seamless publishing workflow with role-based access control.
57
46
58
47
##### Implementation
59
-
60
48
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
49
62
50
##### Skills
63
-
64
51
- TypeScript
65
52
- PostgreSQL
66
53
- Recoil (State Management)
@@ -69,117 +56,147 @@ The project will involve building a CMS-like structure within 100xDevs. The fron
69
56
- Role-based access control
70
57
71
58
##### Mentors
72
-
73
-
-**Lead:** TBC
74
-
-**Support:** TBC
75
-
-**Support:** TBC
59
+
-**Lead:** TBC
60
+
-**Support:** TBC
61
+
-**Support:** TBC
76
62
77
63
##### Size
78
-
79
64
Expected size of project: **approximately 350 hours.**
80
65
81
66
##### Difficulty rating
82
-
83
-
Medium
67
+
High
84
68
85
69
---
86
70
87
71
#### UI/UX Improvement and Codebase Sanitization
88
-
89
72
##### 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.
73
+
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
74
93
75
##### Expected outcomes
94
-
95
76
- A modernized and visually appealing UI with TailwindCSS.
96
77
- Improved user experience with consistent design patterns.
97
78
- Refactored and optimized code for better performance.
98
79
- Improved accessibility and responsiveness.
99
80
100
81
##### Implementation
101
-
102
82
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
83
104
84
##### Skills
105
-
106
85
- TypeScript
107
86
- TailwindCSS
108
87
- UI/UX Design Principles
109
88
- Frontend Optimization
110
89
- Monorepo architecture
111
90
112
91
##### Mentors
113
-
114
-
-**Lead:** TBC
115
-
-**Support:** TBC
116
-
-**Support:** TBC
92
+
-**Lead:** TBC
93
+
-**Support:** TBC
94
+
-**Support:** TBC
117
95
118
96
##### Size
119
-
120
97
Expected size of project: **approximately 175 hours.**
121
98
122
99
##### Difficulty rating
123
-
124
-
Easy
100
+
Medium
125
101
126
102
---
127
103
128
-
### Project proposal: your own idea
104
+
#### Supporting Solidity on Algorithmic Arena
105
+
##### Summary
106
+
Algorithmic Arena currently supports various programming languages for competitive coding. This project aims to add Solidity support, allowing developers to write and execute Solidity-based solutions within the platform.
129
107
130
-
You can also propose your own idea. Your proposal should:
108
+
##### Expected outcomes
109
+
- Full integration of Solidity as a supported language.
110
+
- Execution and validation of Solidity-based solutions.
111
+
- Improved support for blockchain-based coding challenges.
112
+
- Proper sandboxing for Solidity execution.
131
113
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.
114
+
##### Implementation
115
+
This will involve extending the execution engine to support Solidity, integrating sandboxing mechanisms for security, and ensuring compatibility with existing problem structures.
140
116
141
-
#### Note:
117
+
##### Skills
118
+
- TypeScript
119
+
- PostgreSQL
120
+
- Solidity
121
+
- Recoil (State Management)
122
+
- TailwindCSS
123
+
- Monorepo architecture
124
+
125
+
##### Mentors
126
+
-**Lead:** TBC
127
+
-**Support:** TBC
128
+
-**Support:** TBC
142
129
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.
130
+
##### Size
131
+
Expected size of project: **approximately 350 hours.**
146
132
147
-
### Project proposals should fall into one of three categories:
133
+
##### Difficulty rating
134
+
Medium
135
+
136
+
---
148
137
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.
138
+
#### Ratings System for Algorithmic Arena
139
+
##### Summary
140
+
Competitive programming platforms like Codeforces have rating systems that help measure a participant's skill level. This project aims to implement a similar rating system for Algorithmic Arena.
152
141
153
-
### The project you propose should be:
142
+
##### Expected outcomes
143
+
- A dynamic rating system for users.
144
+
- Algorithm-based performance evaluation.
145
+
- A leaderboard showcasing top participants.
146
+
- Backend system to update ratings after each contest.
154
147
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.
148
+
##### Implementation
149
+
The rating system will be based on performance metrics such as problem difficulty, time taken, and accuracy. It will be implemented on the backend with a frontend leaderboard for visibility.
159
150
160
-
#### Template for submitting your project idea:
151
+
##### Skills
152
+
- TypeScript
153
+
- PostgreSQL
154
+
- Recoil (State Management)
155
+
- TailwindCSS
156
+
- Algorithm Design
161
157
162
-
```
163
-
### [Project Idea Title]
158
+
##### Mentors
159
+
-**Lead:** TBC
160
+
-**Support:** TBC
161
+
-**Support:** TBC
162
+
163
+
##### Size
164
+
Expected size of project: **approximately 175 hours.**
165
+
166
+
##### Difficulty rating
167
+
Easy
168
+
169
+
---
170
+
171
+
#### AI-Based Test Case Generator for Algorithmic Arena
164
172
##### Summary
165
-
[Brief description of the project.]
173
+
This project aims to use AI to generate high-quality test cases for problems in Algorithmic Arena, ensuring better coverage and reducing manual effort.
166
174
167
175
##### Expected outcomes
168
-
[List of key deliverables.]
176
+
- AI-powered test case generation.
177
+
- Increased problem validation accuracy.
178
+
- Automatic generation of edge cases.
179
+
- Improved overall problem-solving experience.
169
180
170
181
##### Implementation
171
-
[Outline of how you plan to implement the project.]
182
+
This will involve training AI models to analyze problem statements and generate diverse test cases, ensuring proper edge case coverage. The generated test cases will be evaluated for correctness before being integrated.
172
183
173
184
##### Skills
174
-
[List the key technologies required.]
185
+
- TypeScript
186
+
- PostgreSQL
187
+
- Recoil (State Management)
188
+
- TailwindCSS
189
+
- Machine Learning (AI Models)
175
190
176
191
##### Mentors
177
-
- **Lead:**
178
-
- **Support:**
192
+
-**Lead:** TBC
193
+
-**Support:** TBC
194
+
-**Support:** TBC
179
195
180
196
##### Size
181
-
Expected size of project: **approximately 350 / 175 hours.**
197
+
Expected size of project: **approximately 350 hours.**
0 commit comments