# GSoC 2026 Introduction | Aashir Aslam

**URL:** <https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785>\
**Category:** Google Summer of Code\
**Tags:** gsoc-website, gsoc-period-reachout\
**Created:** [February 28, 2026, 6:17am UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785 "2026-02-28T06:17:28Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aashir\_Aslam](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/aashir_aslam/32/3321_2.png) [@Aashir\_Aslam](https://precice.discourse.group/u/Aashir_Aslam)\
**Post date:** [February 28, 2026, 6:17am UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/1 "2026-02-28T06:17:28Z")

</div>

Hello @fsimonis , @Makis and the preCICE community,

My name is **Muhammad Aashir Aslam**. I am a sophomore Software Engineering student, and I am highly interested in the **Website Modernization** project.

I have been exploring the preCICE ecosystem and contributing by identifying and fixing issues in the website.

* * *

## Contributions So Far

- **[#818](https://github.com/precice/precice.github.io/pull/818) & [#773](https://github.com/precice/precice.github.io/pull/773)**: Identified and corrected an issue in the search indexing workflow.
- **[#813](https://github.com/precice/precice.github.io/pull/)**: Fixed a GitHub workflow that had been silently skipping execution for around 1.5 years, helping resolve the indexing failure related to issue [#388](https://github.com/precice/precice.github.io/issues/388).
- **[#797](https://github.com/precice/precice.github.io/pull/797)**: Fixed missing focus outline in Firefox and Chromium.
- **[#776](https://github.com/precice/precice.github.io/pull/776)**: Fixed a broken markdown link on the Open Projects page.
- **[#798](https://github.com/precice/precice.github.io/pull/798)**: Fixed multiple structural HTML issues including missing tags, duplicate elements, and stray closing tags across the landing page and layouts. (Resolved issue [#772](https://github.com/precice/precice.github.io/issues/772)).

* * *

## Entry Test Work

Since the project involves migrating from Jekyll to Hugo, I **[recreated the landing page](https://github.com/MuhammadAashirAslam/precicelandingpage)** using Hugo and the latest Bootstrap version.

I also implemented:

- A **dark theme toggle** using CSS custom properties with localStorage persistence.
- A **contributors footer** powered by the GitHub API.

**Live demo:** [https://precicelandingpage.netlify.app/](https://precicelandingpage.netlify.app/)

_(Note: This demo currently includes only the landing page. The goal was to replicate the structure while modernizing the implementation.)_

* * *

## Motivation

I believe open source is the best way to apply knowledge in a real, collaborative environment. GSoC is the perfect opportunity for me to **contribute meaningfully while learning under mentorship**.

* * *

## Why This Project?

Coming from a strong web development background, the **Jekyll to Hugo migration** strongly interests me.

I understand the need for modern features such as a **proper dark theme, dynamic contributor visibility, and improved search support**. Moving away from fragile Jekyll plugins toward a more maintainable Hugo setup is an important step forward.

This project focuses on **long-term maintainability and modern UX improvements** , which aligns well with my skills.

* * *

## Relevant Experience

- **Languages & Foundations:** Strong foundation in HTML, CSS, JavaScript, C++, and Python.
- **Web Frameworks:** Experience with MERN stack projects, Bootstrap, Tailwind, React and Next.js.
- **Practical Experience:** I have participated in hackathons and built production-style web applications.

* * *

## Git & Collaboration

I regularly work with Git using **branch-based workflows, pull requests, and review-driven iteration** , and I am very comfortable collaborating asynchronously.

* * *

I am excited about the possibility of contributing to this modernization effort and learning through collaboration with the preCICE community.

Thank you for your time and consideration.

---

<div class="post-metadata">

**Author:** ![Aashir\_Aslam](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/aashir_aslam/32/3321_2.png) [@Aashir\_Aslam](https://precice.discourse.group/u/Aashir_Aslam)\
**Post date:** [March 8, 2026, 7:23am UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/2 "2026-03-08T07:23:27Z")

</div>

Hey @Makis,

Hope you are doing well. I just wanted to ask about the proposal process. Do you have any template or specific writing style in mind for the proposals (as some organizations do for GSoC)?

Usually, proposals are around ~30 pages long, but they are highly tailored and coherent to the specific project being applied for.

Also, I wanted to ask what the next step in the process will be. Will the maintainers reach out to contributors as described on the contributors page, or should we contact mentors directly to share our GSoC proposal drafts for feedback?

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![hanzalahwaheed](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/hanzalahwaheed/32/3273_2.png) [@hanzalahwaheed](https://precice.discourse.group/u/hanzalahwaheed)\
**Post date:** [March 8, 2026, 2:04pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/3 "2026-03-08T14:04:32Z")

</div>

> [@GSoC 2026 Introduction - Hanzalah Waheed](https://precice.discourse.group/t/gsoc-2026-introduction-hanzalah-waheed/2745/4):
>
> Hi @hanzalahwaheed, I still want to reply to everyone over the next couple of weeks. This week is going to be quite busy for me. There is still quite some time left for the application phase to open.

---

<div class="post-metadata">

**Author:** ![Makis](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/makis/32/25_2.png) [@Makis](https://precice.discourse.group/u/Makis)\
**Post date:** [March 8, 2026, 5:44pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/4 "2026-03-08T17:44:15Z")

</div>

> [@Aashir\_Aslam](#):
>
> Usually, proposals are around ~30 pages long, but they are highly tailored and coherent to the specific project being applied for.

I still need to look at everything, but I just stumbled upon this: definitely not 30 pages per proposal, please! We don’t have a template at the moment, but anything more than two pages would be rather inaccessible.

Note that humans will read the proposals. The text must be original.

---

<div class="post-metadata">

**Author:** ![Aashir\_Aslam](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/aashir_aslam/32/3321_2.png) [@Aashir\_Aslam](https://precice.discourse.group/u/Aashir_Aslam)\
**Post date:** [March 18, 2026, 4:16pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/5 "2026-03-18T16:16:33Z")

</div>

Hi @Makis,

Sorry to bother you. I have a couple of questions while drafting my GSoC proposal:

1. My most technical PR is actually the result of three linked PRs of identifying and solving Algolia indexing and the large record size issue. Should I present them as a single PR for the proposal?
2. For the line “Which tools did you use for these PRs, and how much time approximately did you need?” does “tools” refer to AI/code assistants specifically or general development tools as well?

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![Makis](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/makis/32/25_2.png) [@Makis](https://precice.discourse.group/u/Makis)\
**Post date:** [March 18, 2026, 7:09pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/6 "2026-03-18T19:09:36Z")

</div>

> [@Aashir\_Aslam](#):
>
> My most technical PR is actually the result of three linked PRs of identifying and solving Algolia indexing and the large record size issue. Should I present them as a single PR for the proposal?

Just choose one, we will find the rest.

> [@Aashir\_Aslam](#):
>
> For the line “Which tools did you use for these PRs, and how much time approximately did you need?” does “tools” refer to AI/code assistants specifically or general development tools as well?

I would be interested in both, but this is mainly your AI tools disclaimer. As you know, there is a lot of discussion in the field on how to deal with AI in coding, and we just want to know what people use in practice. If we are to work together later, we would anyway need to know.

---

<div class="post-metadata">

**Author:** ![Aashir\_Aslam](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/aashir_aslam/32/3321_2.png) [@Aashir\_Aslam](https://precice.discourse.group/u/Aashir_Aslam)\
**Post date:** [March 27, 2026, 1:22pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/7 "2026-03-27T13:22:25Z")

</div>

Just some updates, I have 2 more PRs merged :

- [#840](https://github.com/precice/precice.github.io/pull/840): Fixed search dropdown overflow by constraining it to viewport height, ensuring all results remain accessible across screen sizes.

- [#856](https://github.com/precice/precice.github.io/pull/856): Implemented a native Jekyll plugin to correctly compute last modified dates for submodule files using `git log`, replacing the abandoned gem (closing #404) .

* * *

### Availability

Also, I forgot to mention earlier: I will not have any other commitments during the coding period and community bonding period. GSoC will be my primary focus, and I will dedicate consistent, full-time effort to ensure timely and high-quality deliverables.

* * *

Also , I have submitted my GSoC proposal and understand that maintainers are busy. If you get a chance to review it, I would really appreciate any feedback or suggestions for improvement.

---

<div class="post-metadata">

**Author:** ![Makis](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/makis/32/25_2.png) [@Makis](https://precice.discourse.group/u/Makis)\
**Post date:** [March 27, 2026, 7:03pm UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/8 "2026-03-27T19:03:15Z")

</div>

Thank you very much for all the PRs so far, @Aashir_Aslam. These were all very useful and easy to merge. Since you asked, I had a first look through your submitted proposal, and it looks very good. The work packages and the timeline are reasonable. I have not yet looked deeper into the technical details, but you seem to be describing these quite accurately.

---

<div class="post-metadata">

**Author:** ![Aashir\_Aslam](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/aashir_aslam/32/3321_2.png) [@Aashir\_Aslam](https://precice.discourse.group/u/Aashir_Aslam)\
**Post date:** [March 28, 2026, 2:57am UTC](https://precice.discourse.group/t/gsoc-2026-introduction-aashir-aslam/2785/9 "2026-03-28T02:57:30Z")

</div>

Thanks sooooo much , really really appreciated ❤❤
