We need to decide on the site (and organization) colours! Discussion is currently on Slack but should be moved to GitHub.

cc @Miko999

Here are the current theme suggestions. Every suggestion is a pull request with a deploy preview. Open the pull request to find the link for the deploy preview.

Closed suggestions:

• Previous blue and orange theme on main suggested by @ye-eun-park
• #22
• #23

Current candidates:

• The currently applied theme on main
• #21

Edit: voting now closed.

This is complete. Just need feedback.

See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors

We should decide what permissions people have for certain actions with this repo. Options listed here https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization

I’d probably set up teams for our GitHub org:

• Organizing team should have triage role
• A website specific team should have write or higher role

Then we can just add people to the different teams to control permissions instead of doing it on an account by account basis

If you plan to contribute to the website could you please leave a comment below.

Once you do I’ll assign you an issue with instructions on your practice assignment. You can use that issue to provide feedback on your experience.

Members participating:

• Gwen

The organizing team can choose who to assign to these issues.

High priority

• #18
• #28
• #10
• #16
• #27
• #2

Low priority

• #3
• #12
• #20

Complete

• #19
• #17

To do once the logo is done

TODO:

• #8
• #1

Note: If anyone wants to test this out on their own, if you create a pull request of your theme changes then Netlify will create a deploy preview of the site with your changes that you can share with the group.

This is complete. Just need feedback.

The current fonts look nice, but the organizing team needs to decide if we want something different.

Right now I'm using Montserrat for the headings and navbar, and Atkinson Hyperlegible (a low-vision friendly font made by the Braille Institute) for the body.

Should we? Or is the text acronym good on its own?

If we don't we could add the logo as a hero image on the home page.

cc @Miko999

How do we want to deal with mailing list sign ups on the site?

We can just ask people to send an email to X account and have a button for that. Or we could set up a subscribe form with mailchimp (or if sharepoint comes with something that handles this we could use that).

cc @GwenvdW @MattKDawson

I added event posts for most of the past events, but most of them need to be edited by the organizing team to include the event descriptions.

The remaining members need to add their profiles to the contact page

TODO:

• #4
• #5

These are tasks that should be wrapped up to meet the terms of the site building contract:

• First draft of website
• Gathering feedback on site design
• Implementing feedback on site design
  • #9
  • #14

I've added the parameter linking to the favicon in _quarto.yml, so we can just add the file and uncomment this line once the favicon is created @Miko999.

Quarto comes with a built-in about page layout we can use https://quarto.org/docs/websites/website-about.html, or we could stick with a plain page (or a mix of the two). Organizing team needs to decide on this one.

Do we want one? e.g., osssg.com or osssg.ca.

Right now the about page is mostly a placeholder. I added some text to it from our values slides but that's it. The organizing team needs to decide what content will go on the about page. For example, the text and sections that will go there, any images, etc.

cc @GwenvdW

I ported some of our documentation over to markdown from word, but the conversion wasn't completely clean so they need some editing and review. Organizing team can assign someone to this.

TODO

• #13
• #15

Add content to pages the organizing team asked for