diff --git a/README.md b/README.md
index 0eb5756..df5b2b0 100644
--- a/README.md
+++ b/README.md
@@ -1,17 +1,109 @@
-# Website
+# CCExtractor Website
-This is the repository hosting the source code of our website (https://www.ccextractor.org).
+This repository contains the source code for the **CCExtractor** website. It is built using **Hugo** (Extended Version).
-It is being built automatically using [Hugo](https://gohugo.io/) with [Netlify's continuous deployment](https://gohugo.io/hosting-and-deployment/hosting-on-netlify/).
+## 🚀 Getting Started
+Follow these steps to set up the project on your local machine.
-## Build and run
+### 1️⃣ Install Dependencies
-- Install hugo and go
-- Run `hugo serve`
+Ensure you have the following installed:
+#### 🔹 **Install Go (Golang)**
-## Contributing
+Download and install Go from the official site:
+[🔗 Download Go](https://go.dev/dl/)
-We welcome all improvements to our website, feel free to open up a Pull Request with changes.
+#### 🔹 **Install Hugo Extended Version**
+##### **Windows (Using Chocolatey)**
+
+```bash
+choco install hugo-extended -y
+```
+
+##### **Linux (Debian/Ubuntu)**
+
+```bash
+sudo apt-get install hugo
+```
+
+##### **MacOS (Using Homebrew)**
+
+```bash
+brew install hugo
+```
+
+##### To verify the installation, run:
+
+```bash
+hugo version
+```
+
+##### Ensure the output includes extended, e.g.:
+
+```bash
+hugo v0.143.1+extended windows/amd64 ...
+```
+
+## 🌎 Theme Setup
+
+The website uses the **Compose** theme, which can be set up in two ways:
+
+### 🔹 Option 1: Default Setup (No Theme Modifications)
+
+By default, the theme is included as a **Hugo module**, as seen in `config.toml`:
+
+```toml
+theme = ["github.com/Techno-Disaster/compose"]
+```
+
+##### If you're not modifying the theme, update dependencies:
+
+```bash
+hugo mod get -u
+hugo mod tidy
+```
+
+## 🔹 Option 2: Customizing the Theme Locally
+
+If you need to make changes to the theme, use a local version instead of the module.
+
+### 1️⃣ Clone the theme manually into the `themes/compose` directory:
+
+```bash
+git clone https://github.com/onweru/compose.git themes/compose
+```
+
+### 2️⃣ Modify `config.toml` to use the local theme:
+
+```bash
+# Comment out the Hugo module theme
+# theme = ["github.com/Techno-Disaster/compose"]
+
+# Use the local theme
+theme = "compose"
+```
+
+## 🏗️ Build and Run
+
+Once the theme setup is complete, build and run the website locally:
+
+### 1️⃣ Run the following command to clean up the site:
+
+```bash
+hugo --gc
+```
+
+### 2️⃣ Serve the site locally:
+
+```bash
+hugo serve
+```
+
+Now, open [http://localhost:1313/](http://localhost:1313/) in your browser to view the site. 🚀
+
+## 📜 License
+
+This project is licensed under the **Apache-2.0 License**. See the [LICENSE](LICENSE) file for details.
diff --git a/content/docs/classic_ideas.md b/content/docs/classic_ideas.md
index 5e8e908..0465d19 100644
--- a/content/docs/classic_ideas.md
+++ b/content/docs/classic_ideas.md
@@ -3,37 +3,43 @@ title: "Google Summer of Code (GSoC) 2025 ideas page - classics"
weight: 1
---
-*This page contains ideas that we find interesting and we would love to do but maybe there are too niche or complicated and no one ever picks them up :-)*
+_This page contains ideas that we find interesting and we would love to do but maybe there are too niche or complicated and no one ever picks them up :-)_
Thanks for visiting this page!
These projects have the same importance as those in the main page. We just moved them to their own page to help keep things tidy.
+**Note:** For new and evolving project ideas, check out the [GSoC 2025 Ideas Page](https://ccextractor.org/docs/ideas_page_for_summer_of_code_2025/).
#### CCExtractor core
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ----------- |
-| [Add support for DTMB countries](/public/gsoc/dtmb) | DTMB is the standard for Chinese TV, also implemented by countries such as Cuba. What kind of student is ideal for this task? One with lots of analytic skills and patience. If you are one of those, don't disregard this task just because you don't speak (or maybe, even care) about Chinese. The experience on dealing with this will be extremely valuable in the future.We will use part of the organization funds to buy standard documents you might need, a capture device, and in general, anything required to make your life easier. | Rust | DTMB Video standards Hardware Research | Unknown | Discuss |
-| [Add Japanese support](/public/gsoc/japanese) | Captions are used by people all over the world on a regular basis. Most of us are familiar with regular horizontal captions at the bottom of the screen, but did you know that in Japan a common position for captions is vertically on the right or left side of the screen? Come learn more about what Japanese audiences need out of captions as well as how captioning standard likes IMSC and WebVTT support these features.| Japanese (or be good with foreign languages), Rust | Depends | Suspected hard | Discuss |
-#### New subtitles tools
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | -------------------------------------- | -------------- | ------- |
+| [Add support for DTMB countries](/public/gsoc/dtmb) | DTMB is the standard for Chinese TV, also implemented by countries such as Cuba. What kind of student is ideal for this task? One with lots of analytic skills and patience. If you are one of those, don't disregard this task just because you don't speak (or maybe, even care) about Chinese. The experience on dealing with this will be extremely valuable in the future.We will use part of the organization funds to buy standard documents you might need, a capture device, and in general, anything required to make your life easier. | Rust | DTMB Video standards Hardware Research | Unknown | Discuss |
+| [Add Japanese support](/public/gsoc/japanese) | Captions are used by people all over the world on a regular basis. Most of us are familiar with regular horizontal captions at the bottom of the screen, but did you know that in Japan a common position for captions is vertically on the right or left side of the screen? Come learn more about what Japanese audiences need out of captions as well as how captioning standard likes IMSC and WebVTT support these features. | Japanese (or be good with foreign languages), Rust | Depends | Suspected hard | Discuss |
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
-| [Subtitle quality quantification tool](/public/gsoc/2022/subtitle_quality/) | Writing a subtitle quality quantification tool | (Some) Rust, Some (C) | CCExtractor internals | Medium | 350 hours |
+#### New subtitles tools
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| --------------------------------------------------------------------------- | ---------------------------------------------- | --------------------- | --------------------- | ---------- | --------- |
+| [Subtitle quality quantification tool](/public/gsoc/2022/subtitle_quality/) | Writing a subtitle quality quantification tool | (Some) Rust, Some (C) | CCExtractor internals | Medium | 350 hours |
#### Systems
+
| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
| [ Linux tuning for network throughput ](/public/gsoc/linuxtuning) | Come up with a system that tunes the linux kernel to maximize network throughput for a number of workloads, such as web server or BitTorrent. We will provide access to a server with a huge pipe (10 Gbit/s, SSD, lots of cores) and your task is to build a tool that maximizes the throughput (and prove it!) | Linux | Kernel internals, Networking | Medium | 175 hours |
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ---------------------------- | ---------- | --------- |
+| [ Linux tuning for network throughput ](/public/gsoc/linuxtuning) | Come up with a system that tunes the linux kernel to maximize network throughput for a number of workloads, such as web server or BitTorrent. We will provide access to a server with a huge pipe (10 Gbit/s, SSD, lots of cores) and your job is to build a tool that maximizes the throughput (and prove it!) | Linux | Kernel internals, Networking | Medium | 175 hours |
+
#### Research
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
-| [ BitTorrent over TLS ](/public/gsoc/bittorrent-tls) | BitTorrent protocol is not secure. Its encryption mechanism is outdated and weak. Even for obfuscation, it is ineffective. Nowadays, even an entry-level gateway has the capability to detect and block BitTorrent traffic at little to no risk. The BitTorrent community would benefit from a new standard encryption mechanism that allows strong encryption, forward secrecy and resistance to censorship. | Depends | Networking, Standardization | Hard | 350 hours |
-| [ The next peer-to-peer protocol ](/public/gsoc/cloudtorrent) | BitTorrent is of course the world's most used peer to peer protocol. It's great, but it was designed before the cloud was ubiquitous and it doesn't make use of the places where you have the most storage or the most bandwidth. Can we design something for the next decade? | Depends | Peer-to-peer, cloud | Unknown | 175 hours |
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | --------------------------- | ---------- | --------- |
+| [ BitTorrent over TLS ](/public/gsoc/bittorrent-tls) | BitTorrent protocol is not secure. Its encryption mechanism is outdated and weak. Even for obfuscation, it is ineffective. Nowadays, even an entry-level gateway has the capability to detect and block BitTorrent traffic at little to no risk. The BitTorrent community would benefit from a new standard encryption mechanism that allows strong encryption, forward secrecy and resistance to censorship. | Depends | Networking, Standardization | Hard | 350 hours |
+| [ The next peer-to-peer protocol ](/public/gsoc/cloudtorrent) | BitTorrent is of course the world's most used peer to peer protocol. It's great, but it was designed before the cloud was ubiquitous and it doesn't make use of the places where you have the most storage or the most bandwidth. Can we design something for the next decade? | Depends | Peer-to-peer, cloud | Unknown | 175 hours |
#### rTorrent
@@ -41,10 +47,10 @@ We use [jesec/rtorrent](https://github.com/jesec/rtorrent). It provides a more m
Note - we want to have a unified rtorrent that gets the best from jesec's and novik's work. See the first project in this section.
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
-| [ Unify flood and ruTorrent's rtorrent versions ](/public/gsoc/rtorrent_unification) | Each of the two most important rTorrent frontends have their own backend version. We need to create a version that works with both ruTorrent and Flood. | C++ | Mostly Docker and rTorrent internals | Easy-Medium | 350 hours |
-| [ a modern RPC interface ](/public/gsoc/rtorrent-modern-rpc) | rTorrent currently uses an antique XMLRPC interface, which is limited in capability, not scalable, hard to use, insecure and low-performance. Community needs a modern RPC interface with full bidirectional, stream processing, incremental data loading and high concurrency capabilities, which allows real-time events for RPC users, reduced serialization/transfer overheads, potentially better security (with authentication and/or TLS), etc. | C++ | RPC, Event Loop | Medium/Hard | 350 hours |
-| asynchronous name resolution | UDP tracker name resolution is not asynchronous at the moment, which causes blocking in the main thread and can block (timeout) other ongoing/incoming connections/transfers. c-ares or libwebsockets implementation is preferred, as c-ares is already used by curl, which rTorrent depends on, while libwebsockets may be used by a future WebSockets RPC interface. | C, C++ | Threading, Event Loop | Medium | 350 hours |
-| improve scalability | rTorrent has a well-defined threading behaviour, which makes it stable and light on resources. There are 3 permanent threads only: main, disk and scgi. However, in the age of Gigabit/10G connections, 3 threads are often not sufficient. Implement a new threading model with better scalability. | C++ | Threading | Hard | 350 hours |
-| scheduling/queuing | In some cases, users might want to download a series of torrents one-by-one without having to manually start the next when the previous is completed. Implement a scheduler along with a queue to allow users to limit the number of maximum simultaneous downloads. Enqueue if the user adds a download or decrease the limit. Dequeue when a download is completed or the user increases the limit. Keep the queue state across reboots. | C++ | Scheduling | Medium | 350 hours |
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | ------------------------------------ | ----------- | --------- |
+| [ Unify flood and ruTorrent's rtorrent versions ](/public/gsoc/rtorrent_unification) | Each of the two most important rTorrent frontends have their own backend version. We need to create a version that works with both ruTorrent and Flood. | C++ | Mostly Docker and rTorrent internals | Easy-Medium | 350 hours |
+| [ a modern RPC interface ](/public/gsoc/rtorrent-modern-rpc) | rTorrent currently uses an antique XMLRPC interface, which is limited in capability, not scalable, hard to use, insecure and low-performance. Community needs a modern RPC interface with full bidirectional, stream processing, incremental data loading and high concurrency capabilities, which allows real-time events for RPC users, reduced serialization/transfer overheads, potentially better security (with authentication and/or TLS), etc. | C++ | RPC, Event Loop | Medium/Hard | 350 hours |
+| asynchronous name resolution | UDP tracker name resolution is not asynchronous at the moment, which causes blocking in the main thread and can block (timeout) other ongoing/incoming connections/transfers. c-ares or libwebsockets implementation is preferred, as c-ares is already used by curl, which rTorrent depends on, while libwebsockets may be used by a future WebSockets RPC interface. | C, C++ | Threading, Event Loop | Medium | 350 hours |
+| improve scalability | rTorrent has a well-defined threading behaviour, which makes it stable and light on resources. There are 3 permanent threads only: main, disk and scgi. However, in the age of Gigabit/10G connections, 3 threads are often not sufficient. Implement a new threading model with better scalability. | C++ | Threading | Hard | 350 hours |
+| scheduling/queuing | In some cases, users might want to download a series of torrents one-by-one without having to manually start the next when the previous is completed. Implement a scheduler along with a queue to allow users to limit the number of maximum simultaneous downloads. Enqueue if the user adds a download or decrease the limit. Dequeue when a download is completed or the user increases the limit. Keep the queue state across reboots. | C++ | Scheduling | Medium | 350 hours |
diff --git a/content/docs/ideas_page_for_summer_of_code_2025.md b/content/docs/ideas_page_for_summer_of_code_2025.md
index 6c4d574..9609cb2 100644
--- a/content/docs/ideas_page_for_summer_of_code_2025.md
+++ b/content/docs/ideas_page_for_summer_of_code_2025.md
@@ -3,13 +3,15 @@ title: "Google Summer of Code (GSoC) 2025 ideas page"
weight: 1
---
-
### This is work in progress! However we intend to have a number of project listed early this year, so check often.
+**Note:** For classic, well-established project ideas that have been part of CCExtractor's GSoC program for several years, check out the [GSoC 2025 Classic Projects](https://ccextractor.org/docs/classic_ideas/) page.
+
{{< tip >}}
+
### **NEW: Office Hours**
-Starting **February 2, 2025**, we will be holding **weekly office hours every Sunday** (depending on your timezone). This is an open session where you can drop in, ask your questions, and have a conversation with an **org admin and/or mentor**—maybe more. There’s no need to be formal, and if you’re shy, you don’t even have to turn your camera on.
+Starting **February 2, 2025**, we will be holding **weekly office hours every Sunday** (depending on your timezone). This is an open session where you can drop in, ask your questions, and have a conversation with an **org admin and/or mentor**—maybe more. There’s no need to be formal, and if you’re shy, you don’t even have to turn your camera on.
To join, simply use this **[Google Meet link](https://meet.google.com/swu-vmra-tyh)**. The sessions will begin at **8:30 AM San Francisco Time**, which serves as the official reference time.
@@ -33,15 +35,14 @@ To join, simply use this **[Google Meet link](https://meet.google.com/swu-vmra-t
}
-There is **no fixed agenda** for these meetings. Whether you want to ask about **GSoC, the organization, your project, or anything else**, you’re welcome to join. If others are discussing something, you can also stay and listen. We will be available for **at least 30 minutes**, but if a conversation is ongoing at **9:00 AM San Francisco Time**, we’ll **continue as long as needed**.
+There is **no fixed agenda** for these meetings. Whether you want to ask about **GSoC, the organization, your project, or anything else**, you’re welcome to join. If others are discussing something, you can also stay and listen. We will be available for **at least 30 minutes**, but if a conversation is ongoing at **9:00 AM San Francisco Time**, we’ll **continue as long as needed**.
Feel free to drop by, ask questions, or just hang out. We look forward to seeing you there!
{{< /tip >}}
{{< tip >}}
[How not to get selected to GSoC](/public/gsoc/how_not_to_be_selected_for_gsoc)
-{{< /tip >}}
-
+{{< /tip >}}
Welcome to our ideas page. It's great you want to start early. Please join us in our Zulip space! (we'll leave this as an exercise for you to find --- it's on our website).
@@ -78,7 +79,7 @@ resources we will provide to you, etc.
{{< tip >}}
Some tasks descriptions are still vague. We know that. Feel free to
get in touch for questions, or just check their page from time to time.
-We will update the descriptions often.
+We will update the descriptions often.
{{< /tip >}}
#### Niche ideas
@@ -88,23 +89,24 @@ These ideas are not less important, but because they require more specialized sk
#### CCExtractor Core
-Since we are now feature complete, and the subtitles work have changed a lot (We won! Almost everything is subtitled now!) it's time to settle down, prepare a really good, stable, battery included release so we can rest on our laurels for a bit after a fantastic run on our core tool.
+Since we are now feature complete, and the subtitles work have changed a lot (We won! Almost everything is subtitled now!) it's time to settle down, prepare a really good, stable, battery included release so we can rest on our laurels for a bit after a fantastic run on our core tool.
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ----------- |
-| [CCExtractor Release 1.00](/public/gsoc/2025/ccextractor_v1) | This is our ambitious project for the summer - work directly with the core team to prepare 1.00 - our first major version bump ever, by getting our PR's from last year vetted, tested and integrated | Some of these: Rust, C, Flutter, Docker, GitHub actions | The rest from the previous list. | Hard | 350 hours |
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | -------------------------------- | ---------- | --------- |
+| [CCExtractor Release 1.00](/public/gsoc/2025/ccextractor_v1) | This is our ambitious project for the summer - work directly with the core team to prepare 1.00 - our first major version bump ever, by getting our PR's from last year vetted, tested and integrated | Some of these: Rust, C, Flutter, Docker, GitHub actions | The rest from the previous list. | Hard | 350 hours |
#### Flutter
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
-| [ Ultimate Alarm Clock III ](/public/gsoc/2025/ultimate_alarm_clock_3) | The ultimate alarm clock, with features no other one has. And free! | Flutter | Good application design | Medium | 350 hours |
-| [ Beacon Watch Companion](/public/gsoc/2025/beacon_watch_companion) | Beacon was started in 2021 and it got a great push also during 2022 and 2024. It aims to ease the group travelling (or hiking). This project is intended to be a companion for the beacon project for smart watches. | Flutter | Scalability | Medium | 175 hours |
-| [ Ultimate Alarm Clock Watch Companion](/public/gsoc/2025/ultimate_alarm_clock_watch_companion) | Ultimate Alarm Clock launched in 2023 and gained significant momentum in 2024. It aims to offer unique features that set it apart from other alarm clock apps—all for free!. This project is intended to be a companion for the ultimate alarm clock project for smart watches. | Flutter | Scalability | Medium | 175 hours |
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ----------------------- | ---------- | --------- |
+| [ Ultimate Alarm Clock III ](/public/gsoc/2025/ultimate_alarm_clock_watch_companion) | The ultimate alarm clock, with features no other one has. And free! | Flutter | Good application design | Medium | 350 hours |
+| [ Beacon Watch Companion](/public/gsoc/2025/beacon_watch_companion) | Beacon was started in 2021 and it got a great push also during 2022 and 2024. It aims to ease the group travelling (or hiking). This project is intended to be a companion for the beacon project for smart watches. | Flutter | Scalability | Medium | 175 hours |
+| [ Ultimate Alarm Clock Watch Companion](/public/gsoc/2025/ultimate_alarm_clock_watch_companion) | Ultimate Alarm Clock launched in 2023 and gained significant momentum in 2024. It aims to offer unique features that set it apart from other alarm clock apps—all for free!. This project is intended to be a companion for the ultimate alarm clock project for smart watches. | Flutter | Scalability | Medium | 175 hours |
| [ Smart Health Reminder ](/public/gsoc/2025/smart_health_reminder) | A fun and interactive health tracking app with smart reminders, challenges, and gamification. Stay healthy effortlessly! | Flutter | Gamification & UX design | Medium | 350 hours |
-| [ support more torrent clients ](/public/gsoc/flutter-more-clients) | We'd like to add support for other clients to our ruTorrent mobile interface (which of course will get a new name): [Flood](https://flood.js.org) and [Deluge](https://deluge-torrent.org). | Flutter | API, Teamwork | Medium | Discuss |
+| [ support more torrent clients ](/public/gsoc/flutter-more-clients) | We'd like to add support for other clients to our ruTorrent mobile interface (which of course will get a new name): [Flood](https://flood.js.org) and [Deluge](https://deluge-torrent.org). | Flutter | API, Teamwork | Medium | Discuss |
#### Systems
+
| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
| [URL shortener, with a twist](/public/gsoc/2025/urlshortener) | A URL shortener converts a long URL into a shorter one. There are many use cases. Some times it's just the shortening itself we want, for example to share it on twitter. Other times it's about obfuscation. We want to create our own, but with some unique features. | Any language you want | Internet infrastructure | Medium | 175 hours |
@@ -115,11 +117,10 @@ Since we are now feature complete, and the subtitles work have changed a lot (We
#### New things we're currently interested on
-| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
-| ----------- | ----------- | ----------- | ----------- | ----------- | ------ |
-| [ Mouseless for Linux v2 - i3 edition ](/public/gsoc/2025/mouseless_i3) | Mouseless is a nice tool to practice keyboard shortcuts for a few popular apps. Unfortunately it's only available for Mac. Last year we created an open source one that runs on Linux. Using that work or not (this is your choice) we want to create one that helps use i3vm (the fantastic windows manager) using keys only. | Your choice | ?? | Unknown | 175 hours |
-| [Desktop Actions in Ilia](/public/gsoc/2025/ilia_context_menu) | Desktop Actions defined in `.desktop` files are used by app launcher to provide access to additional functionalities, typically via context menus. Ilia is an app launcher that currently doesn't support for Desktop Actions due to its keyboard based approach. | Vala, GTK | GTK | Medium | 175 hours |
-
+| Name | Description | Tech you need to know | Tech you will learn | Difficulty | Size |
+| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | ------------------- | ---------- | --------- |
+| [ Mouseless for Linux v2 - i3 edition ](/public/gsoc/2025/mouseless_i3) | Mouseless is a nice tool to practice keyboard shortcuts for a few popular apps. Unfortunately it's only available for Mac. Last year we created an open source one that runs on Linux. Using that work or not (this is your choice) we want to create one that helps use i3vm (the fantastic windows manager) using keys only. | Your choice | ?? | Unknown | 175 hours |
+| [Desktop Actions in Ilia](/public/gsoc/2025/ilia_context_menu) | Desktop Actions defined in `.desktop` files are used by app launcher to provide access to additional functionalities, typically via context menus. Ilia is an app launcher that currently doesn't support for Desktop Actions due to its keyboard based approach. | Vala, GTK | GTK | Medium | 175 hours |
#### About us
@@ -128,14 +129,14 @@ impact. It's not going to mean a 0.5% improvement on a big project ---
it's going to be more than 10% on a medium size one. If you like
challenges and want a chance to shine this is your place.
-We have *we think* statistically amazing continuity in the team: Most
+We have _we think_ statistically amazing continuity in the team: Most
GSoC students from all the past years are still involved, even if they
are no longer eligible as students. They still contribute code, and they
mentor both in GSoC and the sister program GCI. As mentors, they also
come to the Summer of Code summit which traditionally takes place in
October.
-We have *mentors all over the world* (North America, Europe, Asia and
+We have _mentors all over the world_ (North America, Europe, Asia and
Australia), so time zones are never a problem. Our main channel of
communication is a [Zulip instance](/public/general/support) to
which everyone is welcome. We expect all accepted students to be
@@ -222,46 +223,46 @@ Qualification: Our selection system is based on several factors. Of
course no student ranks in all criteria, so don't worry when you read
the list below.
- **Work on our core tool**: Even if you are going to be working
- on something totally different. This might seen counter
- intuitive, but the thing is if you prove you can dig into our
- (messy) code base, find yourself your way around it, and fix a
- few bugs, you are just the kind of person we can trust to
- "figure things out". GSoC is among other things, a learning
- experience. No matter what project you decide to work on,
- there's going to be roadblocks, things you don't know how to
- do, etc. So we really like it when students embrace those
- situations.
+**Work on our core tool**: Even if you are going to be working
+on something totally different. This might seen counter
+intuitive, but the thing is if you prove you can dig into our
+(messy) code base, find yourself your way around it, and fix a
+few bugs, you are just the kind of person we can trust to
+"figure things out". GSoC is among other things, a learning
+experience. No matter what project you decide to work on,
+there's going to be roadblocks, things you don't know how to
+do, etc. So we really like it when students embrace those
+situations.
- **Qualification tasks specific to the project**: The detail page
- for some projects contains specific qualification tasks that
- apply to them.
+**Qualification tasks specific to the project**: The detail page
+for some projects contains specific qualification tasks that
+apply to them.
- **Contributions to existing open source projects**: This can be
- anything. From a good GitHub profile to pull-requests sent to
- any other existing project, participation in hackathons, Google
- Code-In, past GSoCs and so on.
+**Contributions to existing open source projects**: This can be
+anything. From a good GitHub profile to pull-requests sent to
+any other existing project, participation in hackathons, Google
+Code-In, past GSoCs and so on.
- **A good proposal**: This is the one criteria that is
- non-negotiable. Your proposal has to be good, period.
+**A good proposal**: This is the one criteria that is
+non-negotiable. Your proposal has to be good, period.
- **Project popularity**: Some ideas just have more competition,
- so if participating in GSoC is a top priority for you (over
- working on a specific project), consider applying to one of the
- "niche" ideas. After all, that's a great way to get your foot
- in the door :-)
+**Project popularity**: Some ideas just have more competition,
+so if participating in GSoC is a top priority for you (over
+working on a specific project), consider applying to one of the
+"niche" ideas. After all, that's a great way to get your foot
+in the door :-)
- **Best core tool tasks**
+**Best core tool tasks**
We're added a difficulty level to most of our [open issues on GitHub](https://github.com/CCExtractor/ccextractor/issues).
Best thing you can do is head there and see if you are able to fix some
diff --git a/themes/compose b/themes/compose
index 7b1d094..fe432ab 160000
--- a/themes/compose
+++ b/themes/compose
@@ -1 +1 @@
-Subproject commit 7b1d0940bfec595242d33eb3cfb13ee1875705b9
+Subproject commit fe432ab9dec7bc2afda4841891a5b29731b4b995