Welcome to the Community Blog! The Community Blog provides a single source for Fedora community members to share important news, updates, and information about Fedora with others in the community. The Fedora Community Blog connects all the different projects, groups, and efforts going on in the community every day. Teams share their goals, achievements, and calls for help on this blog to help increase the overall interconnectedness of the community. As part of the goals for the Community Operations team, this intends to bring more “heat and light” to the various areas in Fedora.

Writing for the Community Blog

Want to share news of what you and your team are working on in the world of Fedora? Getting started is easy. Anyone can be a writer for any topic, but you are encouraged to discuss this among your own sub-project or team before writing articles on the Community Blog.

1. Write a first draft in the Community Blog.

Using your Fedora Account System (FAS) account, sign into the Community Blog here. You should log into the default WordPress interface. At the top bar, press the “+ New” button to begin writing a draft.

Tips: Short, sweet, to the point

When writing articles for the Community Blog, you should aim to keep your articles short, sweet, and to the point. News from all different parts of the community will be posted here, so there can be a lot of content to keep up with. However, it is encouraged to link to more detailed blog posts, articles, or other news sources to help those who are interested learn more about what you and your subgroup are working on! Ideally, your Community Blog article should be a quick “headliner” pointing out the “big stuff” to grab attention.

If importing from somewhere else…

Are you taking the content for an article from somewhere else? If so, please follow these steps to help speed up the review process:

  1. Remove all HTML tags from your post except for headings, bold / emphasis formatting, hyperlinks, and tables.
    1. WordPress doesn’t show advanced kinds of HTML well. It helps the review process if the article is clean from tags that may be added by other blogging or publishing platforms.
  2. Upload any images in the article to the Community Blog and embed them from the uploaded version.
    1. Sometimes images embedded from third-party websites display at limited resolutions or do not scale well. It makes it easier to understand any pictures / screenshots if uploaded directly to the Community Blog.

2. Basic requirements: Categories, tags, one image.

Every article must have a few things to be published. First, your article must be added to categories relevant to your team. If you are writing an article about a new software being worked on, your post would be categorized as “Development”. If your post is about a Fedora Activity Day for the Design Team, you would use the “Design” and “Events” categories. And so on.

Additionally, add a few tags to your article to help categorize posts and make them easily searchable. You are free to add any tags you wish, but a good number is between 3-6 per article.

Finally, every article must have at least one image before being published. Whether it’s a Badge, a group picture, a screenshot, or anything else is alright, but your article should have at least a single picture to help give a visual to readers. Having a hard time finding a suitable picture? Unsplash has a large library of images released in the public domain that you can choose from – just try to keep it related to what you’re writing about! If you need help finding a picture, we can help design a featured image for your post.

If you need help identifying and selecting categories and tags, you can contact the Community Operations team via email or on IRC (contact information is at the bottom of the page).

3. Email for final approval.

Once you have finished writing your article, change from “Draft” status to “Pending review”. Afterwards, send an email to the Community Operations mailing list with a link to your article announcing that it is ready for review. An editor will review your article, add any final polish, and add it to the publishing schedule. Be on the watch for any feedback on your article if needed.

Once your article is published, it is automatically shared to the @FedoraCommunity Twitter, as well as other social media channels to help bring greater exposure to your article.


Have questions about getting started or run into unexpected problems? The CommOps team is here to help. Stop by our IRC channel, #fedora-commops, on Freenode or drop a line on the mailing list.

Image courtesy of Hope House Press – originally posted on Unsplash as Untitled.