mindshare/docs
mindshare/docs
6
2
Fork 3
Code Issues Pull requests Activity Actions

🐛 docs: Fix broken Antora xrefs that trigger build errors
All checks were successful
Antora docs CI / Build pages (main, mindshare namespace) (pull_request) Has been skipped
Details
Antora docs CI / Build preview (PR) (pull_request) Successful in 10s
Details
Antora docs CI / Build preview (PR) (push) Has been skipped
Details
Antora docs CI / Build pages (main, mindshare namespace) (push) Successful in 9s
Details

Browse source 
The reimbursements page used fully-qualified component paths
(`mindshare-committee:ROOT:`) for pages that live in the events and
policy modules, not `ROOT`. These xrefs resolve to nothing in any
environment. Similarly, `teams.adoc` referenced a nonexistent
`mindshare.adoc` instead of the actual index page.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit is contained in:
Justin Wheeler 2026-07-13 15:44:22 -04:00
commit 647076fa3f
Signed by: jflory7
GPG key ID: 7748B15FA8FA4C7E
2 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/teams.adoc
View file

@ -2,7 +2,7 @@
Mindshare Teams are focused on helping our community grow both the number of users and contributors.
The teams in Mindshare are each focused on a different aspect of this goal.
The xref:mindshare.adoc[Mindshare Committee] fosters communication amongst the Mindshare teams and helps facilitate Council strategy.
The xref:ROOT:index.adoc[Mindshare Committee] fosters communication amongst the Mindshare teams and helps facilitate Council strategy.
* xref:commops:ROOT:index.adoc[**Fedora Community Operations (CommOps)**] — Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.
* xref:fedora-docs:ROOT:index.adoc[**Fedora Docs**] — The group behind this very documentation site. Includes contributors' guidelines to Fedora Docs.

12
modules/policy/pages/reimbursements.adoc
View file

@ -56,11 +56,11 @@ For event-related expenses, this is typically the xref:mindshare-committee:ROOT:
. Follow the current procedures outlined by the Fedora Mindshare Committee below to request sponsorship.
These processes may be under review or restructuring, but they represent the publicly-known guidelines:
** xref:mindshare-committee:ROOT:events/requests/large.adoc[Large Event Requests]
** xref:mindshare-committee:ROOT:events/requests/medium.adoc[Medium Event Requests]
** xref:mindshare-committee:ROOT:events/requests/small.adoc[Small Event Requests]
** xref:mindshare-committee:ROOT:events/release-parties.adoc[Release Party Funding]
** xref:mindshare-committee:ROOT:events/requests/swag-only.adoc[Swag-Only Requests]
** xref:events:requests/large.adoc[Large Event Requests]
** xref:events:requests/medium.adoc[Medium Event Requests]
** xref:events:requests/small.adoc[Small Event Requests]
** xref:events:release-parties.adoc[Release Party Funding]
** xref:events:requests/swag-only.adoc[Swag-Only Requests]
. Once approved, you will use the public URL from the Mindshare Committee GitLab issue that documents this community approval and the budgeted amount.
*Keep this URL handy; you will need it later for your FRR.*
@ -153,7 +153,7 @@ For most Fedora-funded events, you are required to write an event report.
This could be a blog post or a summary on Fedora Discussion.
Alternatively, you can share social media posts about your participation and the event.
* Consult the Fedora Mindshare Committee's xref:mindshare-committee:ROOT:policy/events/reports.adoc[Event Report Policy] for guidance.
* Consult the Fedora Mindshare Committee's xref:policy:events/reports.adoc[Event Report Policy] for guidance.
* Publish your report.
Keep the URL handy; you will need to provide this link when you submit your FRR.