Identify new modules for D&I documentation and create skeleton structure in docs.fp.o/en-US/diversity-inclusion/
On 21 March 2021, the D&I Team held a team meet-up to discuss the history, present, and future of the team. One outcome of the discussion was a new focus on the kinds of information we publish in our documentation site. There are opportunities now to think about our documentation more strategically, thanks to the upkeep work done in 2020.
This allows us to build a contribution pathway for working with the D&I Team through sharing and contributing knowledge to a community-wide resource. It enables us to be a voice of expertise and leadership in areas where the Fedora Community needs support.
Questions we thought about in the meet-up:
To successfully complete this ticket, we need to brainstorm a list of modules, or areas of knowledge, we want to focus on first. Each module should have lots of room for new content underneath that module. Some examples of modules brainstormed during our meet-up are below:
We should aim for at least one but at most three modules, to kick-start this effort off. Once we agree on a final list of modules, we need a volunteer to update the documentation site with new skeleton structure for the modules. The team can share feedback or more guidance on how to do this with the volunteer if needed.
To summarize, there are two key actions to close this ticket:
Discussed in 2022-04-25 team meeting.
Noting this is still relevant for 2022 but the scope should be reduced. A good starting exercise to start is reviewing our existing content to see what is relevant, what is outdated, and then looking at how we organize the content in Antora.
Metadata Update from @jflory7: - Issue untagged with: good first issue, help wanted
Migrated to gitlab.com:fedora/home#18.
@jonatoni and I reviewed this ticket while going through @rwright's HackMD pad with all of our Pagure tickets. This ticket is stale but the need for looking at our docs is still true. A refocus should instead be an audit/review of our content and figuring out what is outdated, what is relevant, and what we could improve.
The new GitLab issue captures this new focus on review instead of strategy. Therefore, I am closing this Pagure ticket as moved so we can continue with the DEI Team migration to GitLab.
moved
Metadata Update from @jflory7: - Issue close_status updated to: moved - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.