My GSoC Midterm Update: From Setup Struggles to a Deployed Site

Tue, 28 Jul 2026 00:00:00 +0000

Hi again! It has been a little over two months since I introduced myself and my project — the NSB User-Centric Website — in my first blog. This is my midterm update, and there is a lot to share.

The website is now live at nsb-ucsc.github.io/nsb, with the Home, Get Started, and Quickstart pages complete, and the Docs section well underway. Here is how it came together.

Getting the Foundation Right

Community bonding was less about writing code and more about becoming an NSB user myself. I set up NSB from scratch on Windows with WSL, worked through protobuf and Abseil dependency issues, built the NSB core, and verified the daemon and runtime end to end — documenting every point of friction along the way. That process shaped the entire project, because the problems I hit as a first-time user became the exact problems the website needed to solve.

Alongside setup, I dug into the architecture: how application clients, the NSB daemon, the SocketRTScheduler, and OMNeT++ all talk to each other through protobuf messaging and socket channels. This groundwork made the design conversations that followed much easier to reason about.

Designing Before Building

Before writing a single line of website code, my mentor Harikrishna (Hari) Kuttivelil and I spent real time on the presentation and design direction. I put together a full website structure deck, and during a team review, we landed on the visual identity: navy blue and gold for dark mode, turquoise cyan for light mode. We also sent out a feedback form to the wider team to validate the color scheme before committing to it, rather than guessing.

One design decision worth calling out: the mock simulator does not try to simulate a full NSB environment inside the browser. Instead, it is shipped as a downloadable file — simpler, honest about what a browser can and cannot do, and much easier for a new user to actually run.

Building the Pages, One at a Time

Home page. Week 1 went into the site structure and an animated hero illustration. It evolved more than once — we later reduced the amount of content on Home and moved the deeper explanations to a dedicated About page, keeping the first impression focused and light. The hero diagram also got a redesign: instead of the original architecture diagram, it now shows separate app and simulator boxes connected by glowing payloads — a small detail, but one that makes the “what does NSB actually do” question click visually before a user reads a word.

Get Started. This page took the most rethinking. Writing content by working through the repository’s READMEs and the latest NSB research paper was the easy part — the harder part was designing it so a brand-new user does not feel lost the moment they land on it, and so it does not just repeat what Quickstart or Docs would later say. Getting that separation right took real iteration.

Quickstart. Once Get Started was settled, Quickstart came together faster, with troubleshooting guidance built in from the start rather than added later, plus small touches like subtle arrow animations to guide the eye through the steps.

Docs. This is where content architecture really mattered. Early on, it was not clear why Tutorials should exist separately from Docs if both explained NS-3 and OMNeT++ setup. After refining the split, the structure now makes sense: installation lives in Get Started and Quickstart, deeper simulator setup moves to Tutorials, and Docs stays focused on reference material — configuration, architecture, and API details, with code blocks and an “On This Page” sidebar for easy navigation. Font choice even got its own small saga: we tried Monaspace Argon for code blocks, then decided the original font actually worked better and reverted.

A Deployment Bug Worth Mentioning

Not everything went smoothly. While preparing for deployment, the site kept failing to build — and the cause turned out to be a stray protobuf reference sitting in the root .env file. A small, easy-to-miss thing, but a good reminder that deployment issues are rarely where you expect them to be. Once fixed, the site deployed cleanly and Home and About were properly separated.

Where Things Stand at Midterm

By the midterm evaluation, the Home, Get Started, and Quickstart pages were complete, the Docs section had its introduction and configuration content in place, and the site was live and deployed. The architecture diagram is currently being refined further with Hari, with ideas to make the app and simulator boxes and their connectors even clearer.

What’s Next

The second half of the project is focused on:

Completing the API reference section in Docs
Finalizing the architecture diagram on the About page
Building out the Tutorials section (Beginner, Intermediate with NetworkX, Advanced with NS-3/OMNeT++)
Adding the Contribute and Community sections
Running usability validation to measure real time-to-first-success against the 15-minute target

Thank you for following along, and check out the live site at nsb-ucsc.github.io/nsb — I would love to hear what you think! Stay tuned for the final blog, where I will share how it all comes together.

If you would like to connect, find me on LinkedIn or GitHub.

Developing a User-Centric Website for the Network Simulation Bridge

Thu, 18 Jun 2026 00:00:00 +0000

Hi! Thanks for stopping by.

In this first blog post of a series of three, I’d like to introduce myself, my mentor, and my project.

My name is Avantika Pandey — a third-year Computer Science student at UIET, Panjab University Chandigarh, with a background in full-stack web development and open source contribution. This summer, I am contributing to the NSB User-Centric Website project as part of Google Summer of Code 2026 under UC OSPO. I am very grateful to be mentored by Harikrishna Kuttivelil. Feel free to read my accepted GSoC proposal and browse the wireframe prototype I built before writing the proposal.

The Problem

The Network Simulation Bridge (NSB) is a middleware layer that connects real application code to network simulators — letting developers and researchers test distributed systems under controlled network conditions (specific latency, packet loss, topology) without needing real infrastructure. NSB is technically solid. Its Python and C++ API documentation is detailed and well-written.

But here is the catch: none of that is easy to find.

After reading every file in the NSB repository and tracing the full setup sequence from scratch as a first-time user, I identified a single root cause behind multiple surface-level problems: there is no guided path from “I just found NSB” to “I have a working example running.” No quickstart, no architecture diagram, undocumented config fields, and eight prerequisites before a single line of user code runs. The result: getting NSB running for the first time takes an estimated 3–4 hours. The goal of this project is to bring that down to 15 minutes.

The Project

My project builds a complete 7-section public website for NSB: Home → Get Started → Quickstart → Docs → Tutorials → Contribute → Community. Every design decision is guided by one principle: First Success First — get the user to a working NSB message exchange before asking them to understand anything. Once they have seen it work, documentation stops being an obstacle and starts being a resource.

A few key decisions that shape the project:

The Quickstart ships with a pre-built mock simulator so a first-time user can observe a full message round-trip without writing a single line of simulator code — both endpoints provided, out of the box.
Simulator integration (NS-3, OMNeT++) is deliberately deferred to the Tutorials section, introduced after the user already has a working foundation.
Windows users get a dedicated WSL2 tab on the Get Started page with step-by-step instructions.
The Docs section fully annotates every config.yaml field, adds a troubleshooting guide with 20+ error/fix pairs, and unifies the Python and C++ API reference into one searchable hub.

Expected Deliverables

Complete NSB website — all 7 sections, publicly deployed, responsive on desktop and mobile
Quickstart onboarding — platform-specific install guide (macOS, Linux, Windows WSL2) with a clear 15-minute path to first message exchange
Structured documentation hub — full config.yaml reference, unified Python/C++ API docs, architecture and message flow diagrams in Mermaid
Tutorial series — Beginner, Intermediate (user builds their own mock with NetworkX), and Advanced (NS-3 / OMNeT++ integration)
Contributor infrastructure — CONTRIBUTING.md, Good First Issues list, PR/issue templates
Usability validation report — measured time-to-first-success with real first-time users

Stay tuned for the midterm and final posts — there is a lot to build, and I am excited to share how it unfolds!

If you find this work interesting, feel free to connect on LinkedIn or follow along on GitHub. Great to meet the UC OSPO community — thanks for reading!

NSB | UCSC OSPO