Planning the expansion of the Docs homepage content #6
Labels
No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Depends on
#8 Creating a Beginner's Guide to Fedora
docs/tickets
Reference
docs/tickets#6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A first draft of the expansion is available at https://pboy.fedorapeople.org/draft/.
The basic structure has already been approved in various discussions. It remains to be decided exactly what details should be included.
Currently under discussion are:
its good to see someone taking the lead
it's certainly a big area that needs to be looked into.
The first thing that come to my mind looking at the draft is the webpage width.
Modern websites tend to keep it around 1130px for better readability.
It makes it easier to implement for mobile UI and is generally easier on the eyes
That being said, I would like to help in any way I can.
@perpetrator I think there are two tasks for this ticket:
I think this ticket is more focused on Task 1, but we could potentially expand the scope to include Task 2. Otherwise, we likely need to open new tickets here to track the general UI/UX work, or work from commops/tickets#71 (which should probably be a ticket over here now anyways).
Ran out of time to discuss in 2026-02-24 Docs Team meeting.
We did not discuss this ticket in today's meeting, even though it did make the agenda. We encouraged Docs Team members to weigh in asynchronously on this issue.
@perpetrator Agreed! But I would like to handle UX / design questions on a separate track. We need a team with a different skill profile for this. And – hopefully – if we exactly know which content to present, the designer can create a more accurate and right to the point graphical design.
And – with limited resources in docs – we have to do one step after the next. So I'll open a new tracking ticket for this.
Created a post at Join SIG Matrix room if they want to add something.