Getting Started

Welcome developer! It’s great to have you here 🎉

There’s a few essentials to get through before getting started, but we should have you up and running in no time 🏃🏽‍♀️‍➡️

GitHub

We use GitHub to manage all of our code and documentation across the various projects that make up Grief Matters.

Our organization, is set up as Grief Matters Inc., and all of our repositories are attached to this organization. If you are a long-term contributor you may have been invited to join the organization. Your membership and role within the organization will determine what you can see (and edit) in this area.

Projects

There is a single Project on GitHub from which all development work is coordinated…

Todo

This section is a work in progress 🚧

Repositories

There are a few repositories that make up the Grief Matters project

grief-matters-cms

The repository for our Sanity Studio headless CMS - built with Sanity and deployed automatically to Cloudflare

whygriefmatters.org

The repository for our website - built with Astro, connected to our Sanity Content Lake and deployed automatically using Cloudflare

docs

Documentation for Content Editors and Developers contributing to the Grief Matters project (this site).

project-documentation

This was a repository capturing all aspects of discovery, requirements and design. Mainly used for reference.

guide-converter

A simple Node app that converted the original PDF document into machine-readable data that could be imported into our Sanity Content Lake

Contributions

We utilise the two common development models at Grief Matters. “Fork and pull” and “Shared repository”

If you’re a long term contributor you may have been added to the organization and assigned a role in one or more of our repositories. If you have write access to a repo then you can pull the repo and make pull requests directly.

If you are a transient contributor then you’ll be using the “fork and pull” workflow. if you’re unfamiliar with the process GitHub have great docs on the topic.