Help build the hub

Found a tool, community, or recurring program that belongs in the directory? Use the form - we review submissions weekly before anything goes live.

1. 1.Open the suggestion form and fill in the name, URL, and category.
2. 2.Explain who it helps and why it fits a curated student hub (not a generic link dump).
3. 3.Submit - you get a GitHub issue link you can track while we triage.

We triage weekly. Your issue stays open until a maintainer accepts or asks for more detail.

Dead link, outdated program dates, typo in a guide, or something misleading? Tell us so we can fix it.

1. 1.Open a GitHub issue with a short title (e.g. "Dead link on Interview Prep guide").
2. 2.Include the page or article name and what is wrong vs what it should say.
3. 3.Add the URL if it is an external resource - screenshots help but are optional.

A maintainer labels and schedules the fix; small content fixes often ship within a few days.

Bug fixes, layout improvements, accessibility, or small features - all through pull requests on our public repo.

1. 1.Fork the repo on GitHub and clone your fork locally.
2. 2.Create a branch (`fix/nav-label`, `feat/browse-filter`, etc.).
3. 3.Make your change, run the app locally if you can, then open a PR against `develop`.
4. 4.Describe what changed and why in the PR - link an issue if one exists.
5. 5.Wait for review; maintainers may request edits before merge.

PRs are reviewed by student maintainers. Focused, small PRs merge faster than large rewrites.

Have an idea for an internal article (recruiting timeline, OA strategy, portfolio tips)? Pitch the topic - we pair you with editorial review before anything publishes.

1. 1.Open a GitHub issue or email us with a working title and who the guide is for.
2. 2.Include 2–3 bullet points on what the reader should be able to do after reading.
3. 3.If you want to draft it yourself, say so - we will point you at the repo folder and style guide.

We reply when the topic fits the roadmap; not every pitch becomes an article immediately.