Skip to content

Conversation

@bendichter
Copy link
Contributor

Add new "Contributing to Website" page with comprehensive instructions for community members to contribute to the NWB website. The guide covers:

  • Quick edits via GitHub for minor changes
  • Local development setup with Hugo
  • Content structure overview
  • Instructions for adding news posts, events, and tools

Update navigation menus to include the new contributing page under the Community section, adjusting weights for existing menu items.

Add new "Contributing to Website" page with comprehensive instructions
for community members to contribute to the NWB website. The guide covers:
- Quick edits via GitHub for minor changes
- Local development setup with Hugo
- Content structure overview
- Instructions for adding news posts, events, and tools

Update navigation menus to include the new contributing page under
the Community section, adjusting weights for existing menu items.
@netlify
Copy link

netlify bot commented Dec 16, 2025

Deploy Preview for nwborg ready!

Name Link
🔨 Latest commit 724003b
🔍 Latest deploy log https://app.netlify.com/projects/nwborg/deploys/6941d02b36d8430008a47c77
😎 Deploy Preview https://deploy-preview-147--nwborg.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

url: "supporting-nwb/"
parent: "Community"
- name: "Team"
- name: "Contributing to Website"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just call it "Contributing"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if we just call it "Contributing" it will seem like a page about contributing to the NWB project in general, not a page specifically about contributing to this website

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. I think the answer here depends on if you like my suggestion for updating the page. Feel free to accept/reject these two suggestions as you see fit. I think either way is Ok. I just figured it would be easy to turn this into a bit broader page if we provide linkages to the other related docs.

Comment on lines +1 to +5
---
title: "Contributing to This Website"
description: "Guide for contributing to the NWB website through GitHub"
---

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if we just add a brief introduction with a short list of links to the various other documents, would help make this a more general guide for how to contribute to NWB. What do you think?

Suggested change
---
title: "Contributing to This Website"
description: "Guide for contributing to the NWB website through GitHub"
---
---
title: "Contributing to NWB"
description: "Guide for contributing to NWB"
---
NWB is a community-driven effort and welcomes contributions from the community:
* **Extending NWB:** To learn more about how to extend and contribute to the NWB data standard schema, please see the [Extending NWB](/extending-nwb/) page.
* **NWB Software:** All NWB software is available on GitHub as open source and welcome contributions via issues and pull requests. For information on how to contribute to a particular software, please see the instructions specific to tool. The [PyNWB Contributing](https://pynwb.readthedocs.io/en/stable/contributing.html) guide provides a general overview of how to contribute to the core NWB software.
* **NWB.org Website:** See the detailed guide below on [Contributing to the NWB Website](#contributing_to_the_nwb_website)
# Contributing to the NWB Website

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants