Meeting started at 2026-08-25 13:00:41 UTC

The Meeting name is 'Fedora Docs Team Meeting - 2026-08-25'

!hi

Eli Ridge: Eli Ridge (egret)

!hi

Petr Bokoc: Petr Bokoč (pbokoc)

!hi

Hristo Marinov: Hristo Marinov (hricky) - he / him / his

!hi

Peter Boy (ServerWG, Docs): Peter Boy (pboy)

Not a big crowd today it seems :) I think a bunch of people are on vacations around this time

I'm hoping activity will pick back up in the following weeks

Alright, let's get started. Do we have any announcements? I don't have anything this time.

None from me

Okay, if not, then

And now, today's agenda - it should be fairly short this time, too.

Im happy to start helping with the wiki pages manually.

Cool! Every little bit helps.

I finally got back to it after way longer than I wanted. I'll merge the PR later today (not directly after the meeting - I have another one directly after this) and then you'll be able to contribute to the repo again. (Wink wink Eli Ridge :P) Sorry it took so long, I should have made sure to finish before I left for PTO, that threw a wrench into everything.

I'm gonna keep both modules named - the ROOT module isn't required, it's just the default and I found out while working on it that it gets confusing when you have a named module, a ROOT, and then topic directories under the ROOT. You can't tell from the generated URL what's a module name and what's a topic. It's not a huge problem but it annoyed me.

OK, as soon as the PR is done, we should announce that on Discussion, together with i list ot task, that needs to b e done.

I'm not sure, it it isn't better to keep the ROOT module as is. It is the consistent way for all Fedora related docs.

We should keep it as consistent and common usage as possible.

It's not actually consistent anyway, there are a couple repos that don't have it already (they have a single module but it's named different).

OK, didn't came across that so far. 😏

Yeah, IIRC it's in repos that we don't usually touch, they're not "ours" (not under the docs organization in Forge)

Anyway, when it's finally merged a bit later, I'll drop a message in our channel

I think, the important ones as e.g. package guidelines and similar use all the ROOT for default, and sometimes a named dir for special additions. But anyway ....

Yeah, let's move on to the next topic

Perhaps slightly off topic, the _contribute to Docs_ guide, should this should be written with other teams in mind where someone wants to contribute to that teams docs (not necessarily the Docs Team org).?

Good question. I think, yes and no. ❤️😄

I think, we give the broader directions, e.g. about style, and we provide the tools and tools docs.

I mean, yeah, it mostly is, isn't it? There are sections with stuff like our contact info, but that's still relevant to people who are contributing to anything - in case they want to ask a question

We should definitely keep in mind that we're not actually the only ones writing docs

Yeah, I think it mostly is. I suppose there might be small hinds of 'Doc Team only' but it just helps to keep it in mind

Yeah, I think it mostly is. I suppose there might be small hints of 'Doc Team only' but it just helps to keep it in mind

Yes. Other items are universal, e.d. the meta data. Or the style guide. And maybe soon a style checker / linter.

Anyway!

Peter Boy (ServerWG, Docs) has been working on redesigning the frontpage, you can see a preview at the link. Do you want to talk about it a bit Peter?

The objectiv here is, to enhance the visibility of our contrib docs, at least the introdiuctionary parts.

We now have to collect ideas, which parts of the contrib docs we want to have in that section. And how we could give a good introduction and 'motivation enlarger'

The original idea (2 years ago) was, that the join team uses the big box to give an intro, offer help, etc. But obviously, the are not interested anymore. So we have to find something else for this.

We have / had a (curently outdated) page "What can I do ...".

Various options are presented here in a playful way.

You mean this one? https://whatcanidoforfedora.org/en#designexclamation

Something like that, yes. I remember it a bit different, the last time I had a look at it.

I had a short discussion with the original author. But don't remember the details out of my head.

Right.

I see we have 2 relevant issues here:

https://forge.fedoraproject.org/docs/tickets/issues/6 - This one is for the contents of the page, as in how it's structured, what's a direct link and what's a subsection

https://forge.fedoraproject.org/docs/tickets/issues/52 - This one is for changes in the visual presentation/styling

Anything else about the frontpage?

no

All right

This is more of an announcement, really. I'm putting together a little proposal to enhance the docs part of the Release Notes process. The idea is that we'll update the Change template on the Wiki with a set of clear questions to ask every Change owner that are meant to help us understand what each Change is about and document it if it needs to be. There are currently sections in the template for both "Release Notes" and "Documentation", but they're being largely ignored and even when someone puts something in, it tends to be barely useful most of the time.

Eventually we also want to expand relnotes to cover more than just formally accepted Changes + whatever people open issues and/or PRs for in the repo. It should be tied to the "docs captains" thing, where various SIGs and other groups would produce a summary of big changes in each release for us.

I had a discussion about the details with FESCo about 2 years ago, when we started a similiar endevour.

But that's a further goal, I'm gonna start small with the Change update & ask Aoife to tell all the Change owners that if they don't fill it out I'll be under their beds

We had some results, then. I'll search in my notes and protocolls and put it into the ticket (do we already have on for this?)

Turns out we actually don't, I just checked :) I'll open one in our tickets repo

And that's all the agenda today.

I'll keep the meeting open till the end of the hour, if anyone has anything else to discuss, now's the time. Or at any other time in our channel, of course :)

There is more progress on the issues I'm working on, but we can discuss this in the Docs room.

I have an interest in the visual style of the Docs front page. Who would be the person to ask if I wanted to give this a go? ( I probably cant be the one take the issue on though, due to not enough skill yet).

I think the first step would be to gather some basic ideas. I suppose it is not that easy.

I suppose it involve manually adjusting antora configuration and CSS. And perhaps building the entire site locally.

We need a modern design, but also one that can provide a lot of information – and flexibel, because the content may change regularly

I suppose it involves manually adjusting antora configuration and CSS files. And perhaps building the entire site locally.

Eli Ridge: Yes, mostly css. And maybe some js.

Okay, thanks for coming everyone and I'll see you back in #docs:fedoraproject.org!