This commit is some long overdue clean-up on the Fedora Community Ops
docs. First, the `/all-assets/` module is done away with entirely. It is
not actually matching the Antora structure and all the files in that
module were simply dumped there. Now, the assets are imported into the
`ROOT` module `assets/` directory, which is where assets are supposed to
be served from in the first place.
Additionally, I added or updated several pages with authorship info and
approximate date last edited, to help make it more obvious when browsing
the docs. Most of the pages touched were from the 2020 Ambassadors
Outreach Revamp.
There is still a lot of work to do with the 2020 Ambassadors Outreach
Revamp outputs, to make this work visible. The `/design-assets/` module
either needs to be cleaned up, or perhaps the Design Team should
consider adopting this information into the official Design Team docs. A
lot of this content feels like it could be maintained by the Fedora
Design Team more reliably than Community Ops. Community Ops folks should
be helping people to discover and find this content when they need it.
CC: @ekidney@madelinepeck
Expect more changes to come related to this change, so that the CommOps
Fedora Docs content is better organized, and useful content is rehomed
to the most appropriate place.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit is a major reworking of the CFP Reviewer Guidelines page, to
match the focus, themes, and other details for Flock 2026. I am making
several of these changes following a live, recorded call for the Flock
CFP reviewer committee, which consists of members of Council, FESCo, and
Mindshare Committee. This is a critical doc to help reviewers both
understand the Pretalx interface and better understand the meaning of
their votes in the review system.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit starts a brand new git repository, using the Fedora Docs
content that was previously hosted in the Community Ops "tickets" repo.
Since we moved to Forgejo, it makes more sense to split out our docs
content into its own dedicated repository, making it easier to discover
and having specific issues and bugs related to content.
A new Pull Request will be made to the "tickets" repo to remove the docs
content from there, to avoid duplication of content.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
