Skip to content

More help for contributing#439

Open
jo-mueller wants to merge 2 commits intoome:mainfrom
jo-mueller:more-contribution-help
Open

More help for contributing#439
jo-mueller wants to merge 2 commits intoome:mainfrom
jo-mueller:more-contribution-help

Conversation

@jo-mueller
Copy link
Contributor

Fixes #323
Fixes #276
Re #184

This PR unravels the contribution section in separate subpages for contributing to the website and contributing to the spec. There are now:

  • some author guidelines for preferred markdown syntax
  • build instructions for ngff-spec page(s) and ngff page(s)
  • Some encouraging words to go ahead with contributing even if you are not familiar with all the markdown stuff

cc @erickmartins @govekk @SeanDuHare because we talked about this recently :)

@jo-mueller jo-mueller added the documentation Improvements or additions to documentation label Feb 16, 2026
Copy link
Contributor

@lubianat lubianat left a comment

Choose a reason for hiding this comment

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

Looks good!


In the future we will flesh out this page with a guide to RFCs, but in the
meantime the RFC process is outlined in the
[Implementation section of RFC 1](../rfc/1/index.md#implementation).
Copy link
Contributor

Choose a reason for hiding this comment

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

Re #427

please do so via a pull request (PR) against the `main` branch of the [ome/ngff-spec](https://github.com/ome/ngff-spec) repository.
Such a PR can contain a change of any of the following components of the ngff-spec repo:

- The spec text itself (`ngff-spec/inex.md`)
Copy link
Contributor

Choose a reason for hiding this comment

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

inex --> index; typo

You can then cite it in the text using the following syntax:

```markdown
This is a citation {cite:t}`citation_key`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe use a real example from references.bib? Could make sense to see it rendered.

Also, are there is a https://github.com/ome/ngff-spec/blob/main/references.bib and a https://github.com/ome/ngff/blob/more-contribution-help/references.bib. As the docs live in ngff, the "this repository" may sound ambiguous.

The spec document under the [ngff-spec](github.com/ome/ngff-spec) repository can be built as a standalone document to make writing and rendering a smoother experience.
To build the spec document, you first need to install the necessary dependencies:

After cloning the ngff-spec repo, navigate into the repository on your machine and install the dependencies using pip:
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe clarify that one needs to install deps + the repo as an editable package?

(at least that is pip install -e . behaviour)

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

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide contribution guide on how to proposed changes to JSON schemas Which copy of the SPEC should changes be proposed against?

2 participants