mautic / mautic/low-no-code

[Content] Review and update content on Governance page on mautic.org

Open
#3 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content-writing-editing design good first issue hacktoberfest help wanted no-code
Dominant language
No language data
Stars
7
Forks
35
PR merge metrics
No merged PRs in 30d

Description

This task has a Jira ticket at https://mautic.atlassian.net/browse/WR-76, details copied below. Ping us in #hacktoberfest if you need inviting to Jira.

You will find the wireframes for the new website at https://www.figma.com/design/OIqb9D6IT3mOP2HjqlZ230/Mautic.org-website-wireframe?node-id=71-267&t=wmMT8GYs1z5xCZuH-1 which shows the kinds of blocks (far right) and layouts we have available.

You can use just the regular content template but if you'd like to make a mockup on Figma / Canva / Whatever to show the web team how you'd like this page to look (e.g. if you want to use images, layouts etc), please do (and share it with us in the issue comments).

This issue relates to updating the content for Governance, which you can find at https://www.mautic.org/about/governance. If there are any comments from the team they will be found below.

Governance details can be found at https://contribute.mautic.org/governance, ask in #wg-governance if you have any questions. It would be good to create a more detailed page which explains Mautic's governance structures, perhaps using imagery / illustrations to show the structures and how it all ties together.

The link for writing the updated content can be found at https://docs.google.com/document/d/1Z0c_A-FQU1CsGPCoZnaACbfiDjQ0-9YSyzDtd-2dHM8/edit?usp=drivesdk.

Thanks for your help!

Please ask for help in #hacktoberfest if you need any guidance.

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

Start with the current Governance page at mautic.org/about/governance, then read the governance details at contribute.mautic.org/governance and the linked Google document for the proposed content. Use the linked Figma wireframes to choose an available layout, and consider imagery or illustrations if useful; done means the page content and structure have been updated and shared with the web team.

Written by the indexing model from the issue text.

Assessment

Tech stack
figma
Domain
content, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 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.