thunderbird / thunderbird/thunderbird-website

Add webpage for the Council

Open
#786 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
298
Forks
118
Avg merge
1d 14h
Merged PRs (30d)
4

Description

I would like to request a dedicated webpage for the Thunderbird Council to explain our purpose, keep the community better informed and encourage contributors to join the election roll.

For reference, I created a prototype of the content for this webpage, which is available here. Feedback is welcome. We were thinking it could be published on a subpage of the main thunderbird.net website, such as thunderbird.net/council or council.thunderbird.net. What are MZLA's thoughts on this? We considered putting it on the Mozilla Wiki, which does already have some limited information about the Council, but we believe it would be more discoverable on a subpage and the Mozilla Wiki seems deprecated (no longer updated or used for new projects).

The Council would need to be able to update the information/links occasionally, but it would not need to be localized. Of course, any help improving the style/UX would be greatly appreciated. If possible, I would like to get this published in the next 1-2 weeks before the current Council term is over, but I understand that may be unrealistic. Please let us know how we can help.

This could be a companion (or alternative) to #98/#785.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the thunderbird-website repository's existing page structure and the linked Council content prototype first. Confirm whether the page should use thunderbird.net/council or council.thunderbird.net, then establish how the Council can update links and information. Done means a published, discoverable webpage with the agreed content and update workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
content, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.