@jflory7 Could you please let me know your thoughts on the changes I made? :grinning:

Minor nitpick, but there are two sentences on this line. Can split out to two lines. :)

• s/focussing/focusing/
• s/some of the many/the/

This line might take some word-smithing. While the Fedora Women community long precedes the D&I Team, it is no longer active or maintained. I think the Fedora Women initiative naturally "fell" to us once the team launched, but I'm not sure if we have done much to keep it up and runnig, with the exception perhaps of Fedora Women's Day events.

My preference is not to include articles (the, a, an) in hyperlinks. Search engines pick up on the text you use for hyperlinks, so I usually prefer to omit articles since they don't add much for Search Engine Optimization (S.E.O.).

I think this xref will break now that #179 is merged.

Maybe we should expand the LUG acronym since it is not obvious like it was 20 years ago. LUG == Linux User Group.

s/nvolved/involved/

Lines 95 and 96 can go together on one line. We don't need to split new lines by commas. :)

s/get-involced.adoc/get-involved.adoc/

s/Thurday/Thursday/

Looking at this… I almost wonder if we should add new attributes, e.g. {MEETING-DAY} and {MEETING-TIME}, and then we can use those attributes on several different pages while only requiring an update to it in a single place. Historically, we sometimes forget to update our docs when our meeting day/time changes!

Might not be in scope for this PR if you do not have time to tweak it. But it would be more convenient this way.

Split to two lines after exclamation point.

Hi @ramyaparimi, this PR looks good! I had specific feedback that I left in-line for you to review. Once the feedback is addressed, we can merge this and close out #166.

Also curious what others (@jonatoni, @amsharma, @riecatnor, @nasirhm, @orionstar25, @lilyx) think of this update and if it is what they all expect too.

@jflory7 Thank you very much for taking your time to look at it :grinning:

In my local preview the xref link to demographic questions was not working. I am not sure what I am doing wrong.

Same with policy page xref as well! Not sure why it is not working.

Hello everyone! I made the changes suggested and tried to fix xref links. Couple of them are not working. Not sure why. Please let me know what I am doing wrong.
Thank you!

It would be really nice to see more specifics on what sort of diversity you are focusing on and what "inclusive" means.

Like is the focus on a diversity of life experience or under represented groups in free software or historically marginalized groups?

To me, being inclusive means everyone feels comfortable and empowered to participate and contribute. This means not only a respectful community but also one that is accessible for the disabled, has multiple avenues for communication to account for different styles and has people's privacy and safety a high priority. If Fedora has any pages on a user privacy policy that should be linked.

Maybe you can state the problem you are trying to address with the goals too. Something like,

"The Fedora community stands on strong pillars of mutual respect, tolerance and encouragement, however this is not enough to increase the participation of socially marginalized groups in the Fedora community. To do this, Fedora is taking an active role to encourage more diverse participation by..."

A lot of people don't understand the purpose of diversity initiatives because they think just being kind to others is good enough. I think a tiny bit of explaination can help with getting people to understand why having education and active involvement is important.

If possible maybe we could get some newbie people to have a look here and see if their questions get answered.

In my local preview the xref link to demographic questions was not working. I am not sure what I am doing wrong. xref:survery:index.adoc[Demographic Survery]

I am not a 100% positive but you are trying to access modules/survey/pages/index.adoc from module/root/pages/index.adoc. Hence you need to specify the correct relative path so that the file can be found.
https://docs.antora.org/antora/2.2/asciidoc/page-to-page-xref/#different-module

Similar for policy link.

W.r.t to the structuring of the landing page, I seem content with this approach. With all bugs fixed, I think this is fairly organized. Good work on the easy flow of topics @ramyaparimi!

If we talk about the relevant content improvement that needs to go here, I'd rather have that discussion abstracted out in another ticket. This ticket serves as a good baseline for restructuring and further creativity.
I am however of the opinion that the landing page should be crisp and ready to route people to relevant (and maybe more important) links. Having too much explanation/content on the landing page itself can get overwhelming.

But, I feel that we can add @meskarune 's well explanatory suggestions along with the introduction text (right before the infographic). It will set the correct tone for the entire docs. :thumbsup:

grammar edit needed: "anyone who supports women's involvement in Fedora"

Thank you @orionstar25 @meskarune @lilyx for the feedback!!

I added a couple of lines to address @meskarune feedback. I tried to get the idea and also tried to keep it short. Let me know your thoughts!

I agree that the landing page now can be a good foundation and there is always room for creativity to add more information. May be creating other pages with additional information that can be xrefed and placed in nav bar could be an idea? So folks interested in getting more information can go ahead without getting to too much information in the landing page.

Thanks @meskarune for the thoughtful feedback. I opened issue #183 to track your feedback, because I think that can actually be tied into something much bigger for the team. :grinning:

From my point-of-view, the content in this Pull Request is ready to go. There are 12 commits in this PR though; it would be nice to squash them down into a single commit so the git commit log remains easy to read and legible. I'll follow up in DM about squashing a PR down to one commit. :)

Any other final feedback before we merge? Thanks all for taking a look!

Merged via #185, closing this PR.