In the Marketing email list, Paul Frields (pfrields / stickster) recently shared a guide on how to create featured images for Fedora Magazine articles (same can also apply for Community Blog, although we don't require featured images). The information is key and critical for contributors and writers who are familiar with design tools or are looking to try picking up some new abilities to create graphics for articles.
The information for this should be in a more visible place other than a mailing list. decause pointed out that it would be a good idea to add this to the "Writing articles for the Community Blog". I think this would be a good idea, although since we don't require featured images for articles, I'm wondering if it would be best to add this to that page or just write an article about it either on the Magazine or CommBlog.
More discussion is needed to decide how we want to go about this! I can take ownership of this ticket and we can decide what to do at the 2016-01-12 meeting.
Of course, I created this ticket without reading the entire mailing list thread. Paul created a page on the Fedora Magazine about [https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/ creating featured images]. With this in mind, we should decide how we want to go about publicizing this further. Perhaps adding a section in the "Writing for the CommBlog" page about featured images and linking to the Magazine about how to make one for an article if you want to?
Closing ticket as outdated.
At the time when I filed, I was not aware of Paul's detailed walkthrough about creating featured images. Since his article does an effective job of communicating the process, I do not see a need to re-publish this anywhere on the Magazine.
As for the Community Blog, it may make a good resource, but I do not see this being something useful for us since we have a much lower barrier to entry for writing on our blog. Featured images are not as important of a part in our workflow as it is for the Magazine. Therefore, I believe the need for this ticket and action has expired.
Login to comment on this ticket.