--- title: "#oppia articles | Hashnode" description: "Explore 28 articles tagged #oppia on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/oppia" --- Tag # #oppia 28 posts · 0 followers [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 15 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-15-with-oppia?utm_source=hashnode&utm_medium=feed) This week felt like the project was finally reaching beyond individual features. The earlier edge-to-edge work I had started before GSoC was now becoming part of the larger Android upgrade. PR #6214 a [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-15-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 14 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-14-with-oppia?utm_source=hashnode&utm_medium=feed) After the worked-example review became stable, I returned to one of the earlier features: the lesson progress indicator. The first version worked, but the progress bar changed too quietly. The connect [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-14-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 13 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-13-with-oppia?utm_source=hashnode&utm_medium=feed) This week I learned that sometimes the best part of a review comment is realizing that your original design is not the best design. While reviewing PR #6318, my mentor pointed out that the HTML parser [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-13-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 12 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-12-with-oppia?utm_source=hashnode&utm_medium=feed) This was one of those weeks where a lot happened, but most of it was not visible from the outside. The worked examples PR was open, and the review thread kept growing. There was no exciting new screen [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-12-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 11 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-11-with-oppia?utm_source=hashnode&utm_medium=feed) After finishing the first milestone, I started the most technically interesting part of my project: worked examples. A worked example contains a question and an answer. That sounds simple until both p [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-11-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 10 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-10-with-oppia?utm_source=hashnode&utm_medium=feed) This week I learned that sometimes the feature is not the thing that breaks. While preparing the alpha build, the protobuf dependency changes caused problems around the Android protobuf toolchain and [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-10-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 9 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-9-with-oppia?utm_source=hashnode&utm_medium=feed) The next challenge was taking the features from my branch and making them available in an alpha build. In PR #6299, I enabled lesson progress and study guides for alpha testing. This required more tha [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-9-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 8 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-8-with-oppia?utm_source=hashnode&utm_medium=feed) This week taught me that opening a PR is only the beginning. Both of my UI PRs were built on top of the domain-layer PRs. That meant I could not merge them independently. First the domain changes had [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-8-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 7 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-7-with-oppia?utm_source=hashnode&utm_medium=feed) After spending so much time inside the domain layer, this was the week when I could finally see something on the screen. I started working on the UI parts of my project through PR #6285 and PR #6286. [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-7-with-oppia?utm_source=hashnode&utm_medium=feed) [Neer Aryan Bhatta](https://hashnode.com/@neer-rn) Sep 3 · 2 min read ### [GSoC 2026: Week 6 with Oppia](https://gsoc2026.hashnode.dev/gsoc-2026-week-6-with-oppia?utm_source=hashnode&utm_medium=feed) I got so busy working through my backlogs that I completely forgot I had been writing weekly blogs to document my journey. Now, as I’m nearing the end, I finally remembered about them. Fortunately, I [gsoc2026.hashnode.dev](https://gsoc2026.hashnode.dev/gsoc-2026-week-6-with-oppia?utm_source=hashnode&utm_medium=feed)