# Proposed Gsoc 2026 projects

**URL:** <https://talk.openelis-global.org/t/proposed-gsoc-2026-projects/1950>\
**Category:** GSOC\
**Tags:** gsoc2026\
**Created:** [February 17, 2026, 6:12am UTC](https://talk.openelis-global.org/t/proposed-gsoc-2026-projects/1950 "2026-02-17T06:12:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lemeri123](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/lemeri123/32/781_2.png) [@Lemeri123](https://talk.openelis-global.org/u/Lemeri123)\
**Post date:** [February 17, 2026, 6:12am UTC](https://talk.openelis-global.org/t/proposed-gsoc-2026-projects/1950/1 "2026-02-17T06:12:32Z")

</div>

Hello, I had some proposed projects in mind  
Let me know your thoughts on this

**1. Migration to Modern Build Tooling (Vite)**

- **The project uses** `react-scripts` (Create React App), which is now deprecated and has slower startup/build times.

- **Code splitting is simulated with** `require` rather than using modern `React.lazy`.

**So;**

- **Migrate to Vite:** Switch the system from Webpack (CRA) to Vite for instant server start, faster Hot Module Replacement and better build optimization.

- **Modern Routing:** Implement dynamic code splitting using `React.lazy` and `Suspense` to reduce the initial bundle size.

- **React Router v6:** Upgrade from v5 to v6 to take advantage of the new data APIs and simpler route configuration.

This will help improve the developer experience and faster loading times for users.

**2. UI/UX Modernization & Carbon Design System Upgrade**

- The app uses `@carbon/react` based on Carbon v10 and `carbon-components`.

- Carbon v11 is the latest major version, featuring a new grid system, better accessibility, and distinct color tokens.

**So;**

- **Upgrade to Carbon v11:** Update dependencies and refactor components to align with Carbon v11’s implementation.

- **Theming:** Implement a proper theming engine using Carbon’s CSS custom properties to support dark mode and better branding customization.

- **Responsive Design:** Audit and improve responsiveness across the application to ensure mobile/tablet compatibility.

This will help create a modern, accessible, and highly polished user interface that compares to the latest design standards. (edited)

---

<div class="post-metadata">

**Author:** ![ketanop321](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/ketanop321/32/1139_2.png) [@ketanop321](https://talk.openelis-global.org/u/ketanop321)\
**Post date:** [February 20, 2026, 4:59pm UTC](https://talk.openelis-global.org/t/proposed-gsoc-2026-projects/1950/2 "2026-02-20T16:59:29Z")

</div>

Hi @Lemeri123 and mentors,

I’m very interested in the **Vite Migration** project. I’ve been actively contributing to OpenELIS Global and have 7+ PRs submitted/merged covering both backend Java and React frontend changes (PRs #2835, #2837, #2839, #2849, #2855, #2858, #2891, #2893).

I did a preliminary feasibility analysis of the frontend codebase for this migration:

- **~533 source files** (271 JS, 130 JSX, 56 TS/TSX)

- **Zero `process.env` usage** — config uses `config.json`, so no env variable rewrites needed

- **Zero webpack overrides** — stock react-scripts, cleanest possible starting point

- **Only 12 `require()` calls** in 4 production files to convert to ESM

- **No `React.lazy` yet** — opportunity to add code splitting during migration

- Sass/SCSS and TypeScript both natively supported by Vite

I believe this is a very feasible Medium-size (~175h) project. Would love to discuss the scope further with mentors.

— Ketan