From a917f435a5b626222ce79affe97841fce9af5ea2 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 04 2019 14:06:42 +0000 Subject: [PATCH 1/148] init --- diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..9f3ebf5 --- /dev/null +++ b/.gitignore @@ -0,0 +1,3 @@ +build +cache +public diff --git a/README.md b/README.md index 73b9ce2..48aac47 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,56 @@ -# fedora-magazine +# Fedora Magazine docs -Resources for the Fedora Magazine editorial board \ No newline at end of file +This repository contains sources of the [Fedora Magazine documentation](https://docs.fedoraproject.org/en-US/fedora-magazine/). + +## Technical information + +``` +|-- README.md +|-- antora.yml ....................... 1. +|-- build.sh ......................... 2. +|-- preview.sh ....................... 3. +|-- site.yml ......................... 4. +`-- modules + `-- ROOT ......................... 5. + |-- assets + | `-- images ............... 6. + | `-- pizza.png + |-- nav.adoc ................. 7. + `-- pages .................... 8. + |-- index.adoc + |-- page.adoc + `-- another-page.adoc +``` + +1. Metadata definition. +2. A script that does a local build. Uses docker. +3. A script that shows a preview of the site in a web browser by running a local web server. Uses docker. +4. A definition file for the build script. +5. A "root module of this documentation component". Please read below for an explanation. +6. **Images** to be used on any page. +7. **Menu definition.** Also defines the hierarchy of all the pages. +8. **Pages with the actual content.** They can be also organised into subdirectories if desired. + +### Local preview + +This repo includes scripts to build and preview the contents of this repository. + +**NOTE**: Please note that if you reference pages from other repositoreis, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions. + +Both scripts work on Fedora (using Podman) and macOS (using Docker). + +To build and preview the site, run: + +``` +$ ./build.sh && ./preview.sh +``` + +The result will be available at http://localhost:8080 + +### Installing Podman on Fedora + +Fedora Workstation doesn't come with Podman preinstalled by default — so you might need to install it using the following command: + +``` +$ sudo dnf install podman +``` \ No newline at end of file diff --git a/antora.yml b/antora.yml new file mode 100644 index 0000000..93ff675 --- /dev/null +++ b/antora.yml @@ -0,0 +1,16 @@ +# Name will be mostly visible in the URL. Treat it as an indentifier. +# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) +name: fedora-magazine # <---- PLEASE MODIFY + +# Title will be visible on the page. +title: Fedora Magazine # <---- PLEASE MODIFY + +# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. +version: master + +# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. +start_page: ROOT:index + +# This lists all the menu definitions of your component. +nav: +- modules/ROOT/nav.adoc diff --git a/build.sh b/build.sh new file mode 100755 index 0000000..1e4db2d --- /dev/null +++ b/build.sh @@ -0,0 +1,46 @@ +#!/bin/sh + +image="docker.io/antora/antora" +cmd="--html-url-extension-style=indexify site.yml" + +if [ "$(uname)" == "Darwin" ]; then + # Running on macOS. + # Let's assume that the user has the Docker CE installed + # which doesn't require a root password. + echo "" + echo "This build script is using Docker container runtime to run the build in an isolated environment." + echo "" + docker run --rm -it -v $(pwd):/antora $image $cmd + +elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then + # Running on Linux. + # Check whether podman is available, else faill back to docker + # which requires root. + + if [ -f /usr/bin/podman ]; then + echo "" + echo "This build script is using Podman to run the build in an isolated environment." + echo "" + podman run --rm -it -v $(pwd):/antora:z $image $cmd + + elif [ -f /usr/bin/docker ]; then + echo "" + echo "This build script is using Docker to run the build in an isolated environment." + echo "" + + if groups | grep -wq "docker"; then + docker run --rm -it -v $(pwd):/antora:z $image $cmd + else + echo "" + echo "This build script is using $runtime to run the build in an isolated environment. You might be asked for your password." + echo "You can avoid this by adding your user to the 'docker' group, but be aware of the security implications. See https://docs.docker.com/install/linux/linux-postinstall/." + echo "" + sudo docker run --rm -it -v $(pwd):/antora:z $image $cmd + fi + else + echo "" + echo "Error: Container runtime haven't been found on your system. Fix it by:" + echo "$ sudo dnf install podman" + exit 1 + fi +fi diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc new file mode 100644 index 0000000..4e2f1bc --- /dev/null +++ b/modules/ROOT/nav.adoc @@ -0,0 +1,7 @@ +* xref:contributing.adoc[Contributing] +** xref:getting-access.adoc[Getting access] +** xref:writing-a-pitch.adoc[Writing a pitch] +** xref:writing-an-article.adoc[Writing an article] +** xref:creating-an-image.adoc[Creating a featured image] +* xref:tips-for-writers.adoc[Tips for writers] +* xref:editorial-meetings.adoc[Editorial meetings] \ No newline at end of file diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc new file mode 100644 index 0000000..c34e768 --- /dev/null +++ b/modules/ROOT/pages/contributing.adoc @@ -0,0 +1,18 @@ += Contributing to the Fedora Magazine + +Fedora Magazine welcomes contributions of content relevant to Fedora Users. + +Before the first contribution: + +1. xref:getting-access.adoc[**Get access**:] You need to have access to our Wordpress in order to contribute. + +Writers' steps: + +2. xref:writing-a-pitch.adoc[**Write a pitch**:] Propose your idea to the editorial board and get it accepted. +3. xref:writing-an-article.adoc[**Write the article**:] Write your article following the recommendations and let the editorial board know when you're ready. + +Editors' steps: + +4. **Edit the article**: An editor makes sure the article reads well, checks facts, and corrects typos. +5. xref:creating-an-image.adoc[**Create an image**:] Each article gets a cover image before its published. +6. **Schedule the article**: Finally, the article is scheduled for publishing! \ No newline at end of file diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc new file mode 100644 index 0000000..b5ab47b --- /dev/null +++ b/modules/ROOT/pages/creating-an-image.adoc @@ -0,0 +1,62 @@ += Creating a featured image for the Fedora Magazine + +Each article in the Fedora Magazine must have a featured image. The image gives the article added visual appeal. It also appears in links on social media, to attract more viewers. + +These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. + + + +== Getting the image repository + +Open a Terminal. (You’ll type commands into the terminal for some of the following steps.) + +Install the git and inkscape packages if you don’t have them installed already: + + + $ sudo dnf install git inkscape + + +If desired, change directory into the folder where you like to store your project work. This example uses the folder name projects, but you should use a folder you have on your system. This step is optional: + + cd projects + +Now clone the git repository of Fedora Magazine images: + + $ git clone https://pagure.io/fedoramagazine-images.git + +== Creating a new image using the template + +Open Inkscape, and choose File > Open… (or hit Ctrl+O). Navigate to the project folder, then into fedoramagazine-images, then into images. Choose the template.svg file. + +Save this as a new file with a different name. + +You can use the assets inside this file to start with the right-sized document, with some pre-configured backgrounds. Feel free to look at other SVGs for guidance. If you don’t have experience with these images, try to stick with fonts and motifs that you see in recent banners. But also feel free to experiment! For instance, use photographs (freely licensed, such as CC-BY or CC-BY-SA) with a text overlay for a nice look. https://unsplash.com/[Unsplash.com] has a large library of images in the public domain you can use to get started. + +=== Fonts + +There are a few fonts that are commonly used in featured images. You are encouraged to use these fonts in your images to help featured images fit into the general “theme” that other images follow. They are all freely available at the links provided. The fonts we commonly use on the Fedora Magazine are listed below. + +http://www.fontsquirrel.com/fonts/montserrat[Montserrat] (friendly and Sans-like) +http://fontsquirrel.com/fonts/roboto-slab[Roboto Slab] (friendly with serifs) +http://www.fontsquirrel.com/fonts/molot[Molot] (heavier font, feels technical) +http://www.fontsquirrel.com/fonts/grand-hotel[Grand Hotel] (for a fancy script-y feel) + +To use these fonts on your Fedora system, download the font and unpack the OTF or TTF file (if required) into your ~/.fonts folder. Then update your font cache: + + $ fc-cache + +You will need to close and reopen Inkscape, GIMP, or other applications to take advantage of the new fonts. + +== Getting your work reviewed + +If you’d like to post your work somewhere, convert it to a JPG first. This will typically be a smaller file. Make sure your SVG file is saved in the fedoramagazine-images/images/ folder as above. Typically these should be named after the article in some way to make it easier to find images later. For this example, let’s assume your SVG file is named using-inkscape.svg. + +Open a Terminal and go to the fedoramagazine-images/images/ folder: + + $ cd projects/fedoramagazine-images/images/ + +Now use the helpful make target we’ve provided. This creates the correct sized (1890x800 pixels) JPG automatically, if you provide the same name as your SVG file: + + $ make using-inkscape.jpg + +Now you can post this file, using-inkscape.jpg, online, and then provide that URL to the mailing list for review. Remember, don’t attach your JPG to a mailing list post. URLs are the correct way to have your file reviewed. \ No newline at end of file diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc new file mode 100644 index 0000000..25741ea --- /dev/null +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -0,0 +1,34 @@ += Fedora Magazine editorial meetings + +The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine. + +== Agenda + +Typically we practice the same agenda each meeting: + +1. Retrospective of last week's publishing and stats +** Ensure all posts were echoed to social media +** If any pending, reviewed stories are not published, schedule and assign social media duty +** See if any first time writers have been published and make a badge request if so +2. https://fedoramagazine.org/wp-admin/edit.php?post_status=pitch&orderby=date&order=asc[Pitch votes] (starting with oldest) +** GOAL: Determine whether pitch is appropriate for a story, and if so, move to Draft status and set publication date +** Include pitches in feedback +** If not, either: +*** Trash pitch, and assign someone to respond to author to thank them +*** Assign someone to work with author to refine story idea +3. https://fedoramagazine.org/wp-admin/edit.php?post_status=draft&post_type=post&orderby=date&order=asc[Drafts not finished] (starting with oldest) +** GOAL: Determine if draft is ready for final review, and if so, move to Pending Review status +** If not: +*** If author is still working, editor is responsible for ensuring completion +*** If author is MIA for 2nd week, drop back to Pitch and rearrange publication schedule +** Assign for review and set to Pending Review status +** Review/set publication date and add to schedule +4. https://fedoramagazine.org/wp-admin/edit.php?post_status=pending&post_type=post&orderby=date&order=asc[Pending Review] (starting with oldest) +** Confirm editor deadline +** Review/set publication date and confirm schedule + +== Exceptions + +The following types of articles generally can route around the weekly meetings. This helps us get critical information out to the audience without waiting for the next board meeting. + +* **Security updates:** Critical security updates that affect a broad user audience are pre-authorized. Generally an editor will write the update article. If possible, one other editor does a quick spot check. If that would affect the timing, however, the posting editor simply publishes the article and notifies the magazine list. An example is a Firefox security issue. \ No newline at end of file diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc new file mode 100644 index 0000000..ac80561 --- /dev/null +++ b/modules/ROOT/pages/getting-access.adoc @@ -0,0 +1,9 @@ += Getting access + + +**1. Get a Fedora FAS Account**: If you don’t already have one, sign up for a https://admin.fedoraproject.org/accounts/user/new[Fedora Account System (FAS) account here]. + +**2. Sign in to the Fedora Magazine**: Now, using your FAS Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here]. + +**3. Join the Magazine list and introduce yourself**: Next up, subscribe to the https://lists.fedoraproject.org/admin/lists/magazine@lists.fedoraproject.org[Fedora Magazine mailing list]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review. + diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc new file mode 100644 index 0000000..3934077 --- /dev/null +++ b/modules/ROOT/pages/index.adoc @@ -0,0 +1,26 @@ += Fedora Magazine + +http://fedoramagazine.org[Fedora Magazine] is a WordPress-based site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.) + +== What is the content of the Magazine + +The content of the magazine varies, but mostly includes: + +* General Announcements / News +* Tips on how to use software in Fedora +* Ideas for cool apps to try +* Ways to more effectively develop software using Fedora +* DIY hardware projects you can power with Fedora +* ... And everything else related to Fedora in general! + +== Join the Magazine Team + +We really need your help on the Magazine. Consider xref:contributing.adoc[writing an article]. You'll also find a link for how to join the marketing mailing list at that link. There is also a detailed guide on how to make a post on the magazine. + +We also have regular xref:editorial-meetings.adoc[editorial board meetings]. + +* IRC Channel: https://webchat.freenode.net/?channels=#fedora-magazine[#fedora-magazine] +* Mailing list: https://lists.fedoraproject.org/admin/lists/magazine@lists.fedoraproject.org/[magazine] + + + diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc new file mode 100644 index 0000000..095ae5e --- /dev/null +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -0,0 +1,70 @@ += Tips for article style, grammar, content, and SEO + +These tips will help your article sail through editing. Be kind to your editor(s), and read this before you start. + +== Markup + +Primary rule: don’t get too fancy. Legibility is important. + +1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write dnf install foo in the middle of a sentence, write dnf install foo. +2. **Use italics for system objects you mention in a sentence:** +** GUI or CLI elements like button text or menu entries +** other prompts the reader must find on the screen +** commands or package names +3. **Use the Preformatted style in the WordPress editor for command line input or output.** Use a shell prompt ($ or #) only where it genuinely affects the meaning, or to set the input apart from output. It also helps to use boldface for the input itself: ++ +[subs=quotes] +---- +$ **command arg1 arg2** +output line 1 +output line 2 +---- + + +4. **Use boldface only for an extremely important phrase or statement.** + + +== Grammar and style tips +1. **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. +** Incorrect heading: __Use Sentence Case for Post Titles in Fedora Magazine__ +** Correct heading: __Use sentence case for post titles in Fedora Magazine__ +2. **Check spelling and grammar.** Nobody likes nitpicky comments about this. Check your work before you send it to an editor. Editors: double-check all the work, that’s your job! +3. **Write clearly and use shorter sentences.** Brevity is good. Clarity is better. Don’t be excessively wordy when avoidable. If a longer sentence is easier to read, use the extra words. +4. **Avoid passive voice.** Passive voice is the use of the object of a sentence as the subject. For example: +** __Active voice__: The troops defeated the enemy. +** __Passive voice__: The enemy was defeated by the troops. +5. **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: +** __Weak, passive voice__: Setting the foobar configuration option will make the application listen on all interfaces. +** __Strong, active voice__: Set the foobar configuration option to make the application listen on all interfaces. +6. **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. +** __Weak__: Zambone is an app used for managing your private documents on a server. +** __Strong__: Zambone manages your private documents on a server. Or: Use Zambone to manage your private documents on a server. +** __Weak__: When setting up a file server, it is important to plan the directory structure carefully. +** __Strong__: Plan the directory structure of the file server carefully before you set it up. +7. **Use standard US English for spelling and other international differences.** US English is the lingua franca for the Fedora Project overall. +8. **Have a smooth flow from general information to specific instructions.** If you’re not sure how to structure your article like this, check out our starter template. + +== Content tips + +These tips are about things to do — and avoid — in what you tell users to do. Remember that thousands of readers trust Fedora Magazine to tell them how to carry out tasks. Be responsible and helpful, advocate best practices, and respect the user’s security and choice. + +1. **Leave packaged files alone.** Processes should not involve editing files under system folders like __/usr__ or __/lib*__. Edit __/etc__ or a user-specific configuration in the home directory. +2. **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. +3. **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. +4. **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). +5. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: +** __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ +6. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. + +== WordPress tips + +1. **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. +2. **Provide a featured image.** Look at https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[the information here] for tips on featured images. You can also feel free to ask the editors to assign this for you. If you make your own image, try to match the style of other images. Use the assets provided https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[in the featured image guide]. Don’t add your own fonts or deviate from the guide. +3. **Use good SEO practices.** Use the SEO plugin provided to maximize the search ranking of the article. Aim for a “green” rating in the __Publish__ box at top right of your article’s edit screen. Follow these guidelines: +** Enter a meaningful keyword in the SEO box under your article. (Most articles shouldn’t use __Fedora__.) +** If the Snippet doesn’t give an effective introduction or summary in the sample search result, rewrite it. +** Don’t feel like you have to eliminate every warning. A “green” rating overall is the only goal. + +== Other hints + +Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. \ No newline at end of file diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc new file mode 100644 index 0000000..d0c6d36 --- /dev/null +++ b/modules/ROOT/pages/writing-a-pitch.adoc @@ -0,0 +1,24 @@ += Writing a pitch for the Fedora Magazine + +== What is a pitch? + +A pitch is the first step for proposing a new article for the Fedora Magazine. If you are looking at getting started with the Magazine and are not yet familiar with what a pitch is, read how to begin contributing to the Magazine. Anyone who is ready to write a pitch should try to use the following format when writing their pitch. Using this format will ensure a speedy and easy review, and in the event that you do not plan to write the article, it will make it easier for a writer to hit key points. + +== Writing a pitch + +Create a new post with Pitch status in the Fedora Magazine WordPress interface. Pitch is the default status for a new post. In your newly-created post, write a brief outline of your post, what it will contain, and the target audience. The Fedora Magazine’s primary audience is Fedora users — including sysadmins and developers too. But in some cases we have content directed at both Fedora users and contributors. + +Once you’re happy with your pitch, email the Fedora Magazine mailing list with a preview link to your pitch. The Magazine editors will review your idea and give you some feedback, and hopefully approve your idea for an article. We review pitches so you don’t waste time on writing a full article that turns out not to fit the Magazine in the end. **Don’t write the whole article** before this step. Let us help you focus it well for best results! + +== Example Pitch + +__The following article serves as an example outline for proposing a new pitch for the Fedora Magazine. This example was used for the https://fedoramagazine.org/never-leave-irc-znc/[Never leave IRC again with ZNC] article.__ + +**Summary**: Describe how to set up an IRC bouncer using ZNC + +**Description**: The purpose of this article would be to describe what an IRC bouncer is and how someone can set up their own ZNC instance to connect to IRC networks and remain persistently connected to channels. The article would aim to educate the user about two things: what and how. Since IRC is a major communication platform for Fedora (and most free and open-source project communities), this article would ideally promote using IRC as well. The flow of the article would be as follows: + +* What is an IRC bouncer / proxy and how does it work? +* Introducing ZNC +* Download, installing, and configuring ZNC on a Fedora machine +* Configuring IRC client to use your ZNC bouncer \ No newline at end of file diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc new file mode 100644 index 0000000..50a4235 --- /dev/null +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -0,0 +1,8 @@ += Writing an article for the Fedora Magazine + +Now that you have an approved pitch, you can **write your article**. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from Pitch to Draft once you receive approval. + +As you write your draft, try to understand and follow the xref:tips-for-writers.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner. + +When you’re completely finished, **submit the article for review**. Set your article’s Status as Pending review in the Publish box at top right, and email the mailing list. The editors will review your draft, and provide feedback to you via the mailing list. Please note that once you mark your article as Pending review the editors assume you believe the article is ready to publish. + diff --git a/nginx.conf b/nginx.conf new file mode 100644 index 0000000..f7093b3 --- /dev/null +++ b/nginx.conf @@ -0,0 +1,14 @@ +server { + listen 80; + server_name localhost; + + location / { + root /antora/public; + index index.html index.htm; + } + + error_page 500 502 503 504 /50x.html; + location = /50x.html { + root /usr/share/nginx/html; + } +} diff --git a/preview.sh b/preview.sh new file mode 100755 index 0000000..acc52af --- /dev/null +++ b/preview.sh @@ -0,0 +1,18 @@ +#!/bin/sh + +if [ "$(uname)" == "Darwin" ]; then + # Running on macOS. + # Let's assume that the user has the Docker CE installed + # which doesn't require a root password. + echo "The preview will be available at http://localhost:8080/" + docker run --rm -v $(pwd):/antora:ro -v $(pwd)/nginx.conf:/etc/nginx/conf.d/default.conf:ro -p 8080:80 nginx + +elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then + # Running on Linux. + # Fedora Workstation has python3 installed as a default, so using that + echo "" + echo "The preview is available at http://localhost:8080" + echo "" + cd ./public + python3 -m http.server 8080 +fi diff --git a/site.yml b/site.yml new file mode 100644 index 0000000..f0149bd --- /dev/null +++ b/site.yml @@ -0,0 +1,20 @@ +site: + title: Fedora Magazine + start_page: fedora-magazine::index +content: + sources: + - url: . + branches: HEAD +ui: + bundle: + url: https://asamalik.fedorapeople.org/ui-bundle.zip + snapshot: true + default_layout: with_menu +output: + clean: true + dir: ./public + destinations: + - provider: archive +runtime: + pull: true + cache_dir: ./cache From bfcaba3d62d9b6b6d2f268c1a4dd9d2f84fe7452 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jul 02 2019 18:19:48 +0000 Subject: [PATCH 2/148] Make the pitch writing tips a little more readable --- diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc index d0c6d36..ea3cd0e 100644 --- a/modules/ROOT/pages/writing-a-pitch.adoc +++ b/modules/ROOT/pages/writing-a-pitch.adoc @@ -2,13 +2,15 @@ == What is a pitch? -A pitch is the first step for proposing a new article for the Fedora Magazine. If you are looking at getting started with the Magazine and are not yet familiar with what a pitch is, read how to begin contributing to the Magazine. Anyone who is ready to write a pitch should try to use the following format when writing their pitch. Using this format will ensure a speedy and easy review, and in the event that you do not plan to write the article, it will make it easier for a writer to hit key points. +A pitch is the first step to propose a new article for the Fedora Magazine. If you want to get started with the Magazine and are don't know what a pitch is, read xref:contributing.adoc[how to begin contributing to the Magazine]. + +If you're ready to write a pitch, try to use the following format. This format can help with a speedy and easy review. Furthermore, in the event you aren't able to write the article, it makes it easier for a writer to hit key points. == Writing a pitch -Create a new post with Pitch status in the Fedora Magazine WordPress interface. Pitch is the default status for a new post. In your newly-created post, write a brief outline of your post, what it will contain, and the target audience. The Fedora Magazine’s primary audience is Fedora users — including sysadmins and developers too. But in some cases we have content directed at both Fedora users and contributors. +Create a new post with __Pitch__ status in the Fedora Magazine WordPress interface. __Pitch__ is the default status for a new post. In your newly-created post, write a brief outline of your post, what it will contain, and the target audience. The Fedora Magazine’s primary audience is Fedora users — including sysadmins and developers too. But in some cases we have content directed at both Fedora users and contributors. -Once you’re happy with your pitch, email the Fedora Magazine mailing list with a preview link to your pitch. The Magazine editors will review your idea and give you some feedback, and hopefully approve your idea for an article. We review pitches so you don’t waste time on writing a full article that turns out not to fit the Magazine in the end. **Don’t write the whole article** before this step. Let us help you focus it well for best results! +Once you’re happy with your pitch, email the mailto:magazine@lists.fedoraproject.org[Fedora Magazine mailing list] with a preview link to your pitch. The Magazine editors will review your idea and give you some feedback, and hopefully approve your idea for an article. We review pitches so you don’t waste time on writing a full article that turns out not to fit the Magazine in the end. **Don’t write the whole article** before this step. Let us help you focus it well for best results! == Example Pitch @@ -21,4 +23,4 @@ __The following article serves as an example outline for proposing a new pitch f * What is an IRC bouncer / proxy and how does it work? * Introducing ZNC * Download, installing, and configuring ZNC on a Fedora machine -* Configuring IRC client to use your ZNC bouncer \ No newline at end of file +* Configuring IRC client to use your ZNC bouncer From 5ac756190e2afe14630d77f551f40d1459b89e5c Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jul 02 2019 18:31:33 +0000 Subject: [PATCH 3/148] Gratuitous markup fixes --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 095ae5e..7ca4169 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -6,7 +6,7 @@ These tips will help your article sail through editing. Be kind to your editor(s Primary rule: don’t get too fancy. Legibility is important. -1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write dnf install foo in the middle of a sentence, write dnf install foo. +1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write dnf install foo in the middle of a sentence, write __dnf install foo__. 2. **Use italics for system objects you mention in a sentence:** ** GUI or CLI elements like button text or menu entries ** other prompts the reader must find on the screen @@ -67,4 +67,4 @@ These tips are about things to do — and avoid — in what you tell users to do == Other hints -Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. \ No newline at end of file +Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 50a4235..e3dd007 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -1,8 +1,8 @@ = Writing an article for the Fedora Magazine -Now that you have an approved pitch, you can **write your article**. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from Pitch to Draft once you receive approval. +Now that you have an approved pitch, you can **write your article**. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. As you write your draft, try to understand and follow the xref:tips-for-writers.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner. -When you’re completely finished, **submit the article for review**. Set your article’s Status as Pending review in the Publish box at top right, and email the mailing list. The editors will review your draft, and provide feedback to you via the mailing list. Please note that once you mark your article as Pending review the editors assume you believe the article is ready to publish. +When you’re completely finished, **submit the article for review**. Set your article’s __Status__ as __Pending review__ in the __Publish__ box at top right, and email the mailing list. The editors will review your draft, and provide feedback to you via the mailing list. Please note that once you mark your article as __Pending review__ the editors assume you believe the article is ready to publish. From 23149847fd76a8e17c16a83e780e1a63b5c87405 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Aug 27 2019 14:15:46 +0000 Subject: [PATCH 4/148] Make a new editorial contribution section --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 4e2f1bc..0efb039 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,7 +1,9 @@ -* xref:contributing.adoc[Contributing] +* xref:contributing.adoc[Contributing content] ** xref:getting-access.adoc[Getting access] ** xref:writing-a-pitch.adoc[Writing a pitch] ** xref:writing-an-article.adoc[Writing an article] ** xref:creating-an-image.adoc[Creating a featured image] * xref:tips-for-writers.adoc[Tips for writers] -* xref:editorial-meetings.adoc[Editorial meetings] \ No newline at end of file +* xref:editorial.adoc[Contributing as an editor] +** xref:editorial-meetings.adoc[Editorial meetings] +** xref:approving-comments.adoc[Approving comments] diff --git a/modules/ROOT/pages/approving-comments.adoc b/modules/ROOT/pages/approving-comments.adoc new file mode 100644 index 0000000..5b56656 --- /dev/null +++ b/modules/ROOT/pages/approving-comments.adoc @@ -0,0 +1,17 @@ += Approving comments + +We moderate comments on the Fedora Magazine to make sure discussions stay constructive and useful. Some sites do not moderate comments, which usually results in spammers, trolls, or other bad actors creating a less appealing environment. Fedora Magazine editors agree that: + + * The Magazine is not a public place, but rather is like private property where we are holding an open-door event. + * We want the Magazine to retain a high value to the public and the community -- in other words, for all attendees to enjoy the event. + * We want to discourage bad actors from creating a negative environment -- in other words, that the event stays safe for everyone. + +Most comments that come in are constructive. Even comments that are critical can be constructive. However, some comments cross a line where they stop being constructive. They may express hostility or include no valuable ideas -- or simply may be spam. + +Therefore, Magazine editors follow a common set of guidelines to approve comments, and discard those that are not constructive. If you are helping moderate comments, here are some guidelines to follow: + + * Comments that are critical of a technology or article are OK to approve. However, they should offer alternative ideas or suggestions. + * Comments that criticize an author, or are hostile to a class of people, or put down Fedora in general should be discarded. + * Comments that point to technologies Fedora doesn't ship are OK to approve; the site has a legal disclaimer that says content expresses the views of individual authors only. + * Comments that are indirect spam should be discarded. You can usually recognize these comments because they are very general, do not include any context from the article, and include a product or other suspect URL as an author name and/or site. + * Duplicate comments should be discarded. (Sometimes comment authors don't read the text that tells them their comment will be held and moderated.) diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index c34e768..04f6642 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -1,4 +1,4 @@ -= Contributing to the Fedora Magazine += Contributing content to the Fedora Magazine Fedora Magazine welcomes contributions of content relevant to Fedora Users. @@ -15,4 +15,4 @@ Editors' steps: 4. **Edit the article**: An editor makes sure the article reads well, checks facts, and corrects typos. 5. xref:creating-an-image.adoc[**Create an image**:] Each article gets a cover image before its published. -6. **Schedule the article**: Finally, the article is scheduled for publishing! \ No newline at end of file +6. **Schedule the article**: Finally, the article is scheduled for publishing! diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc new file mode 100644 index 0000000..3aa23e8 --- /dev/null +++ b/modules/ROOT/pages/editorial.adoc @@ -0,0 +1,7 @@ += Contributing as a Magazine editor + +The duties of an editor are much like any blog owner. Occasionally editors also xref:contributing.adoc[contribute content] when the queue or backlog of content is running a little low. + +Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently. + +Like most blogs and news sites, the Magazine receives feedback and comments from the public. Editors xref:approving-comments.adoc[moderate comments based on common guidelines]. They ensure that discussions stay constructive and discourage trolls and other bad actors. From 8ba494300c8c976c4999629efb7789b2556dd6f0 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Aug 27 2019 14:20:59 +0000 Subject: [PATCH 5/148] Fix small missing markup on tips page --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 7ca4169..f023849 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -6,7 +6,7 @@ These tips will help your article sail through editing. Be kind to your editor(s Primary rule: don’t get too fancy. Legibility is important. -1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write dnf install foo in the middle of a sentence, write __dnf install foo__. +1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write `dnf install foo` in the middle of a sentence, write __dnf install foo__. 2. **Use italics for system objects you mention in a sentence:** ** GUI or CLI elements like button text or menu entries ** other prompts the reader must find on the screen From aadd32c1892b9da0dcefde8904f5b6cdab775227 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 09 2019 15:05:32 +0000 Subject: [PATCH 6/148] add workflow svg --- diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg new file mode 100644 index 0000000..75d1c78 --- /dev/null +++ b/graphics-sources/fedora-magazine-workflow.svg @@ -0,0 +1,2949 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + Publishing + by editors + + Edit & Image + by editors + + Final review + by editors + + Writing + by a writer + + Article proposal + by anyone + + + 1 + idea + + 2 + article spec + + 3 + in progress + + 4 + review + + 5 + to edit + + 6 + queued + + 7 + published + + + + + + + + + Initial review + by editors + + Edit & Image + by editors + + Publishing + by editors + + + Final review + by editors + + + + Writing + by a writer + + + Article proposal + by anyone + + + idea + + article spec + + in progress + + review + + to edit + + queued + + published + + + + + + + + Initial review + by editors + + + + + + Edit & Image + by editors + + Publishing + by editors + + Review + by editors + + Writing + by a writer + + Article proposal + by anyone + + + idea + + article spec + + in progress + + review + + to edit + + queued + + published + + + + + + + + Clarification + by editors + + + + + + + + 1 + 3 + 5 + 2 + 4 + 6 + + + + Edit & Image + by editors + + Publishing + by editors + + + Final review + by editors + + + + Writing + by a writer + + + Article proposal + by anyone + + + idea + + article spec + + in progress + + review + + to edit + + queued + + published + + + + + + + + Initial review + by editors + + + + + + + + + + 1 + 3 + 5 + 2 + 4 + 6 + + + + Article proposal + by anyone + + idea + + + 1 + + + + + Clarification + by editors + + + 2 + + idea + + article spec + + + + + Writing + by a writer + + article spec + + in progress + + review + + + + 3 + + + + + Review + by editors + + + + 4 + + in progress + + review + + to edit + + + + + Publishing + by editors + + + 6 + + queued + + published + + + + + Edit & Image + by editors + + to edit + + queued + + + 5 + + + From e4b4148ae1d35e4e2e544004b29e940bf6b420d7 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 09 2019 15:06:17 +0000 Subject: [PATCH 7/148] add workflow svg --- diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg index 75d1c78..8de741c 100644 --- a/graphics-sources/fedora-magazine-workflow.svg +++ b/graphics-sources/fedora-magazine-workflow.svg @@ -105,36 +105,6 @@ id="path13106" /> - - - - - - - - - - - Publishing - by editors - - Edit & Image - by editors - - Final review - by editors - - Writing - by a writer - - Article proposal - by anyone - - - 1 - idea - - 2 - article spec - - 3 - in progress - - 4 - review - - 5 - to edit - - 6 - queued - - 7 - published - - - - - - - - - Initial review - by editors - - Edit & Image - by editors - - Publishing - by editors - - - Final review - by editors - - - - Writing - by a writer - - - Article proposal - by anyone - - - idea - - article spec - - in progress - - review - - to edit - - queued - - published - - - - - - - - Initial review - by editors - 6 - - Edit & Image - by editors - - Publishing - by editors - - - Final review - by editors - - - - Writing - by a writer - - - Article proposal - by anyone - - - idea - - article spec - - in progress - - review - - to edit - - queued - - published - - - - - - - - Initial review - by editors - - - - - - - - - - 1 - 3 - 5 - 2 - 4 - 6 Date: Sep 09 2019 15:21:54 +0000 Subject: [PATCH 8/148] add new workflow pages and graphics --- diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg new file mode 100644 index 0000000..03c83a1 Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg new file mode 100644 index 0000000..a4f401d Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg new file mode 100644 index 0000000..73a1bd6 Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg new file mode 100644 index 0000000..9e30879 Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg new file mode 100644 index 0000000..f6d457f Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg new file mode 100644 index 0000000..d01f880 Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg new file mode 100644 index 0000000..eafd865 Binary files /dev/null and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 0efb039..79b2b66 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,3 +1,14 @@ +* xref:workflow.adoc[Editorial Workflow] +** xref:workflow-article-proposal.adoc[1 Article Proposal] +** xref:workflow-clarification.adoc[2 Clarification] +** xref:workflow-writing.adoc[3 Writing] +** xref:workflow-review.adoc[4 Review] +** xref:workflow-edit-image.adoc[5 Edit & Image] +** xref:workflow-publishing.adoc[6 Publishing] + + + + * xref:contributing.adoc[Contributing content] ** xref:getting-access.adoc[Getting access] ** xref:writing-a-pitch.adoc[Writing a pitch] diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc new file mode 100644 index 0000000..f65d92b --- /dev/null +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -0,0 +1,3 @@ += Proposing Articles + +image::fedora-magazine-workflow-1.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc new file mode 100644 index 0000000..be144c6 --- /dev/null +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -0,0 +1,3 @@ += Clarifying Proposals + +image::fedora-magazine-workflow-2.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc new file mode 100644 index 0000000..6be9bce --- /dev/null +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -0,0 +1,3 @@ += Editing and Creating Images + +image::fedora-magazine-workflow-5.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc new file mode 100644 index 0000000..746f6d6 --- /dev/null +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -0,0 +1,3 @@ += Publishing Articles + +image::fedora-magazine-workflow-6.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc new file mode 100644 index 0000000..214e0f2 --- /dev/null +++ b/modules/ROOT/pages/workflow-review.adoc @@ -0,0 +1,3 @@ += Reviewing Articles + +image::fedora-magazine-workflow-4.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-writing.adoc b/modules/ROOT/pages/workflow-writing.adoc new file mode 100644 index 0000000..60304b6 --- /dev/null +++ b/modules/ROOT/pages/workflow-writing.adoc @@ -0,0 +1,3 @@ += Writing Articles + +image::fedora-magazine-workflow-3.jpg[,100%,] \ No newline at end of file diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc new file mode 100644 index 0000000..699bcd5 --- /dev/null +++ b/modules/ROOT/pages/workflow.adoc @@ -0,0 +1,4 @@ += Fedora Magazine Editorial Workflow + +image::fedora-magazine-workflow.jpg[,100%,] + From 3565ca70f4425e2c702388d9e872119a3eadb905 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 10 2019 12:12:35 +0000 Subject: [PATCH 9/148] document individual steps of the new workflow --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index f65d92b..e9e67fa 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -1,3 +1,26 @@ = Proposing Articles -image::fedora-magazine-workflow-1.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-1.jpg[,100%,] + +Anyone is welcome to propose an article! + +The proposal can be either just an idea, or a specific pitch (an example is below). Proposing an article doesn't automatically mean the same person needs to write it — although they're definitely welcome to do that! + +== Submitting an idea + +The preferred way is to https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[**open an issue in the Fedora Magazine Taiga**]. + +An alternative option is to email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. + +== A specific pitch example + +__The following article serves as an example outline for proposing a new pitch for the Fedora Magazine. This example was used for the https://fedoramagazine.org/never-leave-irc-znc/[Never leave IRC again with ZNC] article.__ + +**Summary**: Describe how to set up an IRC bouncer using ZNC + +**Description**: The purpose of this article would be to describe what an IRC bouncer is and how someone can set up their own ZNC instance to connect to IRC networks and remain persistently connected to channels. The article would aim to educate the user about two things: what and how. Since IRC is a major communication platform for Fedora (and most free and open-source project communities), this article would ideally promote using IRC as well. The flow of the article would be as follows: + +* What is an IRC bouncer / proxy and how does it work? +* Introducing ZNC +* Download, installing, and configuring ZNC on a Fedora machine +* Configuring IRC client to use your ZNC bouncer diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index be144c6..8038e65 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -1,3 +1,17 @@ = Clarifying Proposals -image::fedora-magazine-workflow-2.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-2.jpg[,100%,] + +The Editorial Board reviews each proposal and creates a specific article description. + +Proposals might be discussed with the person who proposed them, with subject matter experts, and anyone who wants (or has the technical ability to) give an input. + +== Where to discuss + +The discussion happens in the respective issue or email thread. + +Issues are submitted in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[issue tracker in Fedora Magazine Taiga], and emails are sent to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list]. + +== Writing an article spec + +When the review is complete, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index 6be9bce..05679b3 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -1,3 +1,32 @@ = Editing and Creating Images -image::fedora-magazine-workflow-5.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-5.jpg[,100%,] + +Before an article can be published, it needs to be edited, and it needs a cover image. + +Members of the Editorial Board provide both of those. + +== Editing + +Articles that require editing are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. + +**Edit** the article for potential grammatical and spelling errors. + +When done, indicate that in the comments. + +If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + + +== Creating a cover image + +Articles that require a cover image are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. + +**Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions. + +When done, indicate that in the comments. + +If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index 746f6d6..6558c82 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -1,3 +1,13 @@ = Publishing Articles -image::fedora-magazine-workflow-6.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-6.jpg[,100%,] + +A member of the Editorial board either publishes or schedules an article for publishing. + +== Publishing an article + +Articles that are ready to be published are in the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +After publishing or scheduling them in Wordpress, move the card to the __Published__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +That's it! \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index 214e0f2..22d875d 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -1,3 +1,18 @@ = Reviewing Articles -image::fedora-magazine-workflow-4.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-4.jpg[,100%,] + +The Editorial Board makes a decision whether the article is ready to go. + +== Reviewing an article + +Articles that are ready for review are in the __Review__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +=== When article is good to go + +If the article is good to go, a member of the Editorial Board simply moves it to the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + + +=== When article needs changes + +If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __In Progress__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-writing.adoc b/modules/ROOT/pages/workflow-writing.adoc index 60304b6..bdc2584 100644 --- a/modules/ROOT/pages/workflow-writing.adoc +++ b/modules/ROOT/pages/workflow-writing.adoc @@ -1,3 +1,23 @@ = Writing Articles -image::fedora-magazine-workflow-3.jpg[,100%,] \ No newline at end of file +image::fedora-magazine-workflow-3.jpg[,100%,] + +Anyone with good writing skills is welcome to write an article for the Fedora Magazine! + +Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the [Becoming a Writer] page for more information. + +== Writing an article + +**Choose** any article you like in the __Article Spec__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +**Assign** the card you've chosen to yourself by opening the card and clicking on __Assign to myself__ on the right hand side. + +**Move it to __In Progress__** by simply dragging the card to the appropriate column. + +**Write** your article either in Wordpress (create a new article there) or anywhere you prefer. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. + +**Move it to __Review__** when done with writing. Please include a link to Wordpress or to the text in the card before moving it to the __Review__ column so the Editors can access it. + +And that's it! + +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. \ No newline at end of file From fcaad61844151509fab7a8dbb023bc46fb454ef9 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 10 2019 12:52:30 +0000 Subject: [PATCH 10/148] update other content for the new workflow --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 79b2b66..b130d8f 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,20 +1,16 @@ * xref:workflow.adoc[Editorial Workflow] ** xref:workflow-article-proposal.adoc[1 Article Proposal] ** xref:workflow-clarification.adoc[2 Clarification] -** xref:workflow-writing.adoc[3 Writing] +** xref:writing-an-article.adoc[3 Writing] ** xref:workflow-review.adoc[4 Review] ** xref:workflow-edit-image.adoc[5 Edit & Image] ** xref:workflow-publishing.adoc[6 Publishing] +* xref:writing-a-pitch.adoc[Proposing Articles] +* xref:contributing.adoc[Contributing as a Writer] +** xref:getting-access.adoc[Getting Access] +** xref:tips-for-writers.adoc[Tips for Writers] +* xref:editorial.adoc[Contributing as an Editor] +** xref:editorial-meetings.adoc[Editorial Meetings] +** xref:approving-comments.adoc[Approving Comments] +** xref:creating-an-image.adoc[Creating a Featured Image] - - - -* xref:contributing.adoc[Contributing content] -** xref:getting-access.adoc[Getting access] -** xref:writing-a-pitch.adoc[Writing a pitch] -** xref:writing-an-article.adoc[Writing an article] -** xref:creating-an-image.adoc[Creating a featured image] -* xref:tips-for-writers.adoc[Tips for writers] -* xref:editorial.adoc[Contributing as an editor] -** xref:editorial-meetings.adoc[Editorial meetings] -** xref:approving-comments.adoc[Approving comments] diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index 04f6642..51c3e1b 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -1,18 +1,7 @@ -= Contributing content to the Fedora Magazine += Contributing to the Fedora Magazine as a writer -Fedora Magazine welcomes contributions of content relevant to Fedora Users. +Anyone with good writing skills is welcome to write an article for the Fedora Magazine! -Before the first contribution: +See the xref:writing-an-article.adoc[Writing page] to learn how to do that. -1. xref:getting-access.adoc[**Get access**:] You need to have access to our Wordpress in order to contribute. - -Writers' steps: - -2. xref:writing-a-pitch.adoc[**Write a pitch**:] Propose your idea to the editorial board and get it accepted. -3. xref:writing-an-article.adoc[**Write the article**:] Write your article following the recommendations and let the editorial board know when you're ready. - -Editors' steps: - -4. **Edit the article**: An editor makes sure the article reads well, checks facts, and corrects typos. -5. xref:creating-an-image.adoc[**Create an image**:] Each article gets a cover image before its published. -6. **Schedule the article**: Finally, the article is scheduled for publishing! +If this is your first contribution, you will need to xref:getting-access.adoc[get access] first. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow-writing.adoc b/modules/ROOT/pages/workflow-writing.adoc deleted file mode 100644 index bdc2584..0000000 --- a/modules/ROOT/pages/workflow-writing.adoc +++ /dev/null @@ -1,23 +0,0 @@ -= Writing Articles - -image::fedora-magazine-workflow-3.jpg[,100%,] - -Anyone with good writing skills is welcome to write an article for the Fedora Magazine! - -Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the [Becoming a Writer] page for more information. - -== Writing an article - -**Choose** any article you like in the __Article Spec__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. - -**Assign** the card you've chosen to yourself by opening the card and clicking on __Assign to myself__ on the right hand side. - -**Move it to __In Progress__** by simply dragging the card to the appropriate column. - -**Write** your article either in Wordpress (create a new article there) or anywhere you prefer. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. - -**Move it to __Review__** when done with writing. Please include a link to Wordpress or to the text in the card before moving it to the __Review__ column so the Editors can access it. - -And that's it! - -Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index 699bcd5..4b8f4d5 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -2,3 +2,19 @@ image::fedora-magazine-workflow.jpg[,100%,] +Content on the Fedora Magazine is created using a 6-step workflow: + +1. xref:workflow-article-proposal.adoc[Article Proposal] by Anyone +2. xref:workflow-clarification.adoc[Clarification] by Editors +3. xref:writing-an-article.adoc[Writing] by a Writer +4. xref:workflow-review.adoc[Review] by Editors +5. xref:workflow-edit-image.adoc[Edit & Image] by Editors +6. xref:workflow-publishing.adoc[Publishing] by Editors + +During that process, the article goes through 7 states: __idea__, __article spec__, __in progress__, __review__, __to edit__, __queued__, and __published__. Each step in the workflow has its own page in this documentation that provides guidance. + +== Tracking + +Proposals in the **__idea__** state are represented as an issue in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[Issues section of the Fedora Magazine Taiga]. + +Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. \ No newline at end of file diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc index ea3cd0e..dae2272 100644 --- a/modules/ROOT/pages/writing-a-pitch.adoc +++ b/modules/ROOT/pages/writing-a-pitch.adoc @@ -1,26 +1,5 @@ -= Writing a pitch for the Fedora Magazine += Proposing Articles for the Fedora Magazine -== What is a pitch? +Anyone is welcome to propose an article to the https://fedoramagazine.org[Fedora Magazine]. -A pitch is the first step to propose a new article for the Fedora Magazine. If you want to get started with the Magazine and are don't know what a pitch is, read xref:contributing.adoc[how to begin contributing to the Magazine]. - -If you're ready to write a pitch, try to use the following format. This format can help with a speedy and easy review. Furthermore, in the event you aren't able to write the article, it makes it easier for a writer to hit key points. - -== Writing a pitch - -Create a new post with __Pitch__ status in the Fedora Magazine WordPress interface. __Pitch__ is the default status for a new post. In your newly-created post, write a brief outline of your post, what it will contain, and the target audience. The Fedora Magazine’s primary audience is Fedora users — including sysadmins and developers too. But in some cases we have content directed at both Fedora users and contributors. - -Once you’re happy with your pitch, email the mailto:magazine@lists.fedoraproject.org[Fedora Magazine mailing list] with a preview link to your pitch. The Magazine editors will review your idea and give you some feedback, and hopefully approve your idea for an article. We review pitches so you don’t waste time on writing a full article that turns out not to fit the Magazine in the end. **Don’t write the whole article** before this step. Let us help you focus it well for best results! - -== Example Pitch - -__The following article serves as an example outline for proposing a new pitch for the Fedora Magazine. This example was used for the https://fedoramagazine.org/never-leave-irc-znc/[Never leave IRC again with ZNC] article.__ - -**Summary**: Describe how to set up an IRC bouncer using ZNC - -**Description**: The purpose of this article would be to describe what an IRC bouncer is and how someone can set up their own ZNC instance to connect to IRC networks and remain persistently connected to channels. The article would aim to educate the user about two things: what and how. Since IRC is a major communication platform for Fedora (and most free and open-source project communities), this article would ideally promote using IRC as well. The flow of the article would be as follows: - -* What is an IRC bouncer / proxy and how does it work? -* Introducing ZNC -* Download, installing, and configuring ZNC on a Fedora machine -* Configuring IRC client to use your ZNC bouncer +See the xref:workflow-article-proposal.adoc[Article Proposal] page for how to do that. \ No newline at end of file diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index e3dd007..bd6c991 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -1,8 +1,33 @@ -= Writing an article for the Fedora Magazine += Writing Articles -Now that you have an approved pitch, you can **write your article**. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. +image::fedora-magazine-workflow-3.jpg[,100%,] + +Anyone with good writing skills is welcome to write an article for the Fedora Magazine! + +Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the [Becoming a Writer] page for more information. + +== Writing an article + +=== 1. Choose what to write + +**Choose** any article you like in the __Article Spec__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +**Assign** the card you've chosen to yourself by opening the card and clicking on __Assign to myself__ on the right hand side. + +**Move it to __In Progress__** by simply dragging the card to the appropriate column. + +=== 2. Write it + +**Write** your article either in Wordpress (create a new article there) or anywhere you prefer. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. + +https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. As you write your draft, try to understand and follow the xref:tips-for-writers.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner. -When you’re completely finished, **submit the article for review**. Set your article’s __Status__ as __Pending review__ in the __Publish__ box at top right, and email the mailing list. The editors will review your draft, and provide feedback to you via the mailing list. Please note that once you mark your article as __Pending review__ the editors assume you believe the article is ready to publish. +=== 3. Mark it as done + +**Move it to __Review__** when done with writing. Please include a link to Wordpress or to the text in the card before moving it to the __Review__ column so the Editors can access it. + +And that's it! +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. \ No newline at end of file From 1b04c0897a51d23f28aae152f6e3407e0a432032 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 16 2019 12:41:18 +0000 Subject: [PATCH 11/148] banner about the process change --- diff --git a/modules/ROOT/pages/approving-comments.adoc b/modules/ROOT/pages/approving-comments.adoc index 5b56656..dfdf4fe 100644 --- a/modules/ROOT/pages/approving-comments.adoc +++ b/modules/ROOT/pages/approving-comments.adoc @@ -1,5 +1,7 @@ = Approving comments +include::partial$workflow-change-banner.adoc[] + We moderate comments on the Fedora Magazine to make sure discussions stay constructive and useful. Some sites do not moderate comments, which usually results in spammers, trolls, or other bad actors creating a less appealing environment. Fedora Magazine editors agree that: * The Magazine is not a public place, but rather is like private property where we are holding an open-door event. diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index 51c3e1b..7b92122 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -1,5 +1,7 @@ = Contributing to the Fedora Magazine as a writer +include::partial$workflow-change-banner.adoc[] + Anyone with good writing skills is welcome to write an article for the Fedora Magazine! See the xref:writing-an-article.adoc[Writing page] to learn how to do that. diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc index b5ab47b..ac2577b 100644 --- a/modules/ROOT/pages/creating-an-image.adoc +++ b/modules/ROOT/pages/creating-an-image.adoc @@ -1,5 +1,7 @@ = Creating a featured image for the Fedora Magazine +include::partial$workflow-change-banner.adoc[] + Each article in the Fedora Magazine must have a featured image. The image gives the article added visual appeal. It also appears in links on social media, to attract more viewers. These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 25741ea..b63baed 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -1,5 +1,7 @@ = Fedora Magazine editorial meetings +include::partial$workflow-change-banner.adoc[] + The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine. == Agenda diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc index 3aa23e8..b707a07 100644 --- a/modules/ROOT/pages/editorial.adoc +++ b/modules/ROOT/pages/editorial.adoc @@ -1,5 +1,7 @@ = Contributing as a Magazine editor +include::partial$workflow-change-banner.adoc[] + The duties of an editor are much like any blog owner. Occasionally editors also xref:contributing.adoc[contribute content] when the queue or backlog of content is running a little low. Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently. diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index ac80561..096790d 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -1,5 +1,7 @@ = Getting access +include::partial$workflow-change-banner.adoc[] + **1. Get a Fedora FAS Account**: If you don’t already have one, sign up for a https://admin.fedoraproject.org/accounts/user/new[Fedora Account System (FAS) account here]. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 3934077..fb3d7a1 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -1,5 +1,7 @@ = Fedora Magazine +include::partial$workflow-change-banner.adoc[] + http://fedoramagazine.org[Fedora Magazine] is a WordPress-based site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.) == What is the content of the Magazine diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index f023849..c670414 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -1,5 +1,7 @@ = Tips for article style, grammar, content, and SEO +include::partial$workflow-change-banner.adoc[] + These tips will help your article sail through editing. Be kind to your editor(s), and read this before you start. == Markup diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index e9e67fa..766ca30 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -1,5 +1,7 @@ = Proposing Articles +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-1.jpg[,100%,] Anyone is welcome to propose an article! diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 8038e65..88ff17e 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -1,5 +1,7 @@ = Clarifying Proposals +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-2.jpg[,100%,] The Editorial Board reviews each proposal and creates a specific article description. diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index 05679b3..adcf91c 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -1,5 +1,7 @@ = Editing and Creating Images +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-5.jpg[,100%,] Before an article can be published, it needs to be edited, and it needs a cover image. diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index 6558c82..8411800 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -1,5 +1,7 @@ = Publishing Articles +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-6.jpg[,100%,] A member of the Editorial board either publishes or schedules an article for publishing. diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index 22d875d..da7e1e5 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -1,5 +1,7 @@ = Reviewing Articles +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-4.jpg[,100%,] The Editorial Board makes a decision whether the article is ready to go. diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index 4b8f4d5..cef711d 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -1,5 +1,7 @@ = Fedora Magazine Editorial Workflow +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow.jpg[,100%,] Content on the Fedora Magazine is created using a 6-step workflow: diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc index dae2272..43e589f 100644 --- a/modules/ROOT/pages/writing-a-pitch.adoc +++ b/modules/ROOT/pages/writing-a-pitch.adoc @@ -1,5 +1,7 @@ = Proposing Articles for the Fedora Magazine +include::partial$workflow-change-banner.adoc[] + Anyone is welcome to propose an article to the https://fedoramagazine.org[Fedora Magazine]. See the xref:workflow-article-proposal.adoc[Article Proposal] page for how to do that. \ No newline at end of file diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index bd6c991..bb906bf 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -1,5 +1,7 @@ = Writing Articles +include::partial$workflow-change-banner.adoc[] + image::fedora-magazine-workflow-3.jpg[,100%,] Anyone with good writing skills is welcome to write an article for the Fedora Magazine! diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc new file mode 100644 index 0000000..1234111 --- /dev/null +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -0,0 +1 @@ +NOTE: **Process change in progress.** The Fedora Magazine is currently moving to a xref:workflow.adoc[new editorial workflow]. Some inconsistencies might occur for a few days, starting 16 Sep 2019. Please follow the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list] for further updates. All changes are expected be finalized by the end of the week. \ No newline at end of file From 00986a5e4d946e8fe26ba355e6335c23fcb21847 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 16 2019 12:43:55 +0000 Subject: [PATCH 12/148] clarify channels for submitting ideas --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 766ca30..68436ae 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -10,9 +10,9 @@ The proposal can be either just an idea, or a specific pitch (an example is belo == Submitting an idea -The preferred way is to https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[**open an issue in the Fedora Magazine Taiga**]. +If you have a https://admin.fedoraproject.org/accounts/[Fedora account], the preferred way is to https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[open an issue in the Fedora Magazine Taiga]. -An alternative option is to email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. +If you don't have a https://admin.fedoraproject.org/accounts/[Fedora account], you can email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. == A specific pitch example From b3de3c91cece1cfdfa37bc392311a47fa7c53a7f Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 18 2019 11:23:51 +0000 Subject: [PATCH 13/148] update meeting agenda guidance --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index b63baed..5502fda 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -1,33 +1,95 @@ = Fedora Magazine editorial meetings -include::partial$workflow-change-banner.adoc[] - The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine. == Agenda -Typically we practice the same agenda each meeting: - -1. Retrospective of last week's publishing and stats -** Ensure all posts were echoed to social media -** If any pending, reviewed stories are not published, schedule and assign social media duty -** See if any first time writers have been published and make a badge request if so -2. https://fedoramagazine.org/wp-admin/edit.php?post_status=pitch&orderby=date&order=asc[Pitch votes] (starting with oldest) -** GOAL: Determine whether pitch is appropriate for a story, and if so, move to Draft status and set publication date -** Include pitches in feedback -** If not, either: -*** Trash pitch, and assign someone to respond to author to thank them -*** Assign someone to work with author to refine story idea -3. https://fedoramagazine.org/wp-admin/edit.php?post_status=draft&post_type=post&orderby=date&order=asc[Drafts not finished] (starting with oldest) -** GOAL: Determine if draft is ready for final review, and if so, move to Pending Review status -** If not: -*** If author is still working, editor is responsible for ensuring completion -*** If author is MIA for 2nd week, drop back to Pitch and rearrange publication schedule -** Assign for review and set to Pending Review status -** Review/set publication date and add to schedule -4. https://fedoramagazine.org/wp-admin/edit.php?post_status=pending&post_type=post&orderby=date&order=asc[Pending Review] (starting with oldest) -** Confirm editor deadline -** Review/set publication date and confirm schedule + +=== Roll call + + #startmeeting Magazine editorial board + #meetingname magazine + #topic Roll call + #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc + + +=== Agenda + + #topic Agenda + #info Fedora Magazine has moved to a new Editorial Workflow + #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ + #info Following is the meeting agenda that is a slightly different than before: + #info -- 1/ Last week's stats -- + #info -- 2/ In progress followup -- + #info -- 3/ Finished articles to review -- + #info -- 4/ Articles to edit -- + #info -- 5/ Publishing schedule -- + #info -- 6/ Article proposals to clarify / approve -- + #info -- 7/ Open floor -- + + +=== 1/ Last week's stats + + #topic 1/ Last week's stats + #info Week of : K pageviews -- + + +=== 2/ In progress followup + + #topic 2/ In progress followup + #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? + #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + + +=== 3/ Finished articles to review + + #topic 3/ Finished articles to review + #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback. + #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + + +=== 4/ Articles to edit + + #topic 4/ Articles to edit + #info Looking at the 'to edit' column, assign an editor and a cover image creator. + #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + + +=== 5/ Publishing schedule + + #topic 5/ Publishing schedule + #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period. + #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content. + #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + + #proposed #agreed PUBLISHING SCHEDULE: + DAY DATE, NAME (NICK:edit/NICK:image) --  + DAY DATE, NAME (NICK:edit/NICK:image) -- + DAY DATE, NAME (NICK:edit/NICK:image) -- + + +=== 6/ Article proposals to clarify / approve + + #topic 6/ Article proposals to clarify / approve + #info Review the the article proposals and decide about what's next — a new article spec? more discussion? + #link Article proposals: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues + + +=== 7/ Open floor + + #topic 7/ Open floor + + +=== Meeting ends + + #endmeeting + + +=== After the meeting + +Send the minutes to the list +Subject: Editorial board meeting recap YYYY-Mmm-DD + == Exceptions From a51d2153f2fb6ae849dd7a41d8b575d16d2a413b Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 20 2019 11:15:52 +0000 Subject: [PATCH 14/148] update new workflow banner --- diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc index 1234111..187e50b 100644 --- a/modules/ROOT/partials/workflow-change-banner.adoc +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -1 +1 @@ -NOTE: **Process change in progress.** The Fedora Magazine is currently moving to a xref:workflow.adoc[new editorial workflow]. Some inconsistencies might occur for a few days, starting 16 Sep 2019. Please follow the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list] for further updates. All changes are expected be finalized by the end of the week. \ No newline at end of file +NOTE: The Fedora Magazine has moved to a xref:workflow.adoc[new editorial workflow] - please see the page for more details. From 483a5c2e0265288e9f4d28c61058f7f0d44b038f Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 25 2019 08:39:09 +0000 Subject: [PATCH 15/148] move article proposals to pagure issues --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 68436ae..c5ea4e1 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -6,11 +6,11 @@ image::fedora-magazine-workflow-1.jpg[,100%,] Anyone is welcome to propose an article! -The proposal can be either just an idea, or a specific pitch (an example is below). Proposing an article doesn't automatically mean the same person needs to write it — although they're definitely welcome to do that! +The proposal can be either just an idea, or a specific pitch (an example is below). Proposing an article doesn't automatically mean the same person needs to write it. Having a good set of ideas helps writers to just write what they know is relevant for the Magazine, without necessarily thinking about new content just so they can write something. == Submitting an idea -If you have a https://admin.fedoraproject.org/accounts/[Fedora account], the preferred way is to https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[open an issue in the Fedora Magazine Taiga]. +If you have a https://admin.fedoraproject.org/accounts/[Fedora account], the preferred way is to https://pagure.io/fedora-magazine-proposals/issues[open an issue in the Fedora Magazine Proposals issue tracker]. If you don't have a https://admin.fedoraproject.org/accounts/[Fedora account], you can email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 88ff17e..db68dc1 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -6,14 +6,18 @@ image::fedora-magazine-workflow-2.jpg[,100%,] The Editorial Board reviews each proposal and creates a specific article description. -Proposals might be discussed with the person who proposed them, with subject matter experts, and anyone who wants (or has the technical ability to) give an input. +Proposals might be discussed with the person who proposed them, with subject matter experts, and anyone who wants (or has the technical ability to) give an input. We encourage anyone in the community to provide feedback to the proposals! == Where to discuss The discussion happens in the respective issue or email thread. -Issues are submitted in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[issue tracker in Fedora Magazine Taiga], and emails are sent to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list]. +Issues are submitted in the https://pagure.io/fedora-magazine-proposals/issues[Fedora Magazine Proposals issue tracker], and emails are sent to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list]. + +Opinions and additional relevant information is welcome from anyone. == Writing an article spec -When the review is complete, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. \ No newline at end of file +When the review is complete, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. + +This card now represent a specific articles and goes through all the other steps of the workflow. \ No newline at end of file diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index cef711d..5fec756 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -13,10 +13,10 @@ Content on the Fedora Magazine is created using a 6-step workflow: 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors 6. xref:workflow-publishing.adoc[Publishing] by Editors -During that process, the article goes through 7 states: __idea__, __article spec__, __in progress__, __review__, __to edit__, __queued__, and __published__. Each step in the workflow has its own page in this documentation that provides guidance. +An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __queued__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance. == Tracking -Proposals in the **__idea__** state are represented as an issue in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues[Issues section of the Fedora Magazine Taiga]. +Proposals in the **__idea__** state are represented issues in our https://pagure.io/fedora-magazine-proposals/issues[Fedora Magazine Proposals issue tracker]. Everyone is welcome to submit one! -Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. \ No newline at end of file +Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! \ No newline at end of file From f4397136a8995ea4c7e7d57f17d4a36469986629 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 25 2019 08:54:35 +0000 Subject: [PATCH 16/148] update the new workflow banner --- diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc index 187e50b..ef733ce 100644 --- a/modules/ROOT/partials/workflow-change-banner.adoc +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -1 +1 @@ -NOTE: The Fedora Magazine has moved to a xref:workflow.adoc[new editorial workflow] - please see the page for more details. +NOTE: Starting September 20 2019, the Fedora Magazine is testing a xref:workflow.adoc[new editorial workflow] — see the page to learn how to propose new articles or write some. \ No newline at end of file From 442f324ab6c723a04510fbcfbbc86e074164aee0 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 25 2019 08:55:53 +0000 Subject: [PATCH 17/148] update the new workflow banner --- diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc index ef733ce..ed579fc 100644 --- a/modules/ROOT/partials/workflow-change-banner.adoc +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -1 +1 @@ -NOTE: Starting September 20 2019, the Fedora Magazine is testing a xref:workflow.adoc[new editorial workflow] — see the page to learn how to propose new articles or write some. \ No newline at end of file +NOTE: Starting 20 September 2019, the Fedora Magazine is testing a xref:workflow.adoc[new editorial workflow] — see the page to learn how to propose new articles or write some. \ No newline at end of file From 0cd27b9f2c26f8ee781a664bd37af22522c9d7fc Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 25 2019 08:57:42 +0000 Subject: [PATCH 18/148] add 'about' to the menu for better navigation --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index b130d8f..c1867d1 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,3 +1,4 @@ +* xref:index.adoc[About Fedora Magazine] * xref:workflow.adoc[Editorial Workflow] ** xref:workflow-article-proposal.adoc[1 Article Proposal] ** xref:workflow-clarification.adoc[2 Clarification] From 92a6f2eedb7c03ac18196a6ac2d609f501ee05ed Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 25 2019 10:10:10 +0000 Subject: [PATCH 19/148] update wording on contribute pages --- diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index 7b92122..774020b 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -1,9 +1,11 @@ -= Contributing to the Fedora Magazine as a writer += Contributing as a Fedora Magazine Writer include::partial$workflow-change-banner.adoc[] -Anyone with good writing skills is welcome to write an article for the Fedora Magazine! +Fedora Magazine welcomes new writers to contribute their skill by writing an article or two! or five! -See the xref:writing-an-article.adoc[Writing page] to learn how to do that. +We have a list of specific topics you can write about — so you don't need to come up with new ideas to write. Although you can definitely xref:writing-a-pitch.adoc[propose an article] if you have ideas. Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week! -If this is your first contribution, you will need to xref:getting-access.adoc[get access] first. \ No newline at end of file +**See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.** + +Also, if this is your first contribution, you will need to xref:getting-access.adoc[get access] first. \ No newline at end of file diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc index b707a07..5116ca0 100644 --- a/modules/ROOT/pages/editorial.adoc +++ b/modules/ROOT/pages/editorial.adoc @@ -1,4 +1,4 @@ -= Contributing as a Magazine editor += Contributing as a Fedora Magazine Editor include::partial$workflow-change-banner.adoc[] diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc index 43e589f..3e76cbc 100644 --- a/modules/ROOT/pages/writing-a-pitch.adoc +++ b/modules/ROOT/pages/writing-a-pitch.adoc @@ -1,7 +1,9 @@ -= Proposing Articles for the Fedora Magazine += Proposing Articles for Fedora Magazine include::partial$workflow-change-banner.adoc[] -Anyone is welcome to propose an article to the https://fedoramagazine.org[Fedora Magazine]. +Fedora Magazine welcomes anyone to submit ideas for articles. -See the xref:workflow-article-proposal.adoc[Article Proposal] page for how to do that. \ No newline at end of file +We on purpose separate the process of proposing articles and writing — because those are two different skills. By proposing a topic, you are helping writers to have relevant topics they can write about. + +**See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for guidance.** \ No newline at end of file diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index bb906bf..1550db9 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -6,7 +6,7 @@ image::fedora-magazine-workflow-3.jpg[,100%,] Anyone with good writing skills is welcome to write an article for the Fedora Magazine! -Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the [Becoming a Writer] page for more information. +__Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the xref:getting-access.adoc[Getting Access] page for more information.__ == Writing an article From 2b023d7ac1d6d270524f47bede8ff5f46e19339e Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Sep 25 2019 13:05:02 +0000 Subject: [PATCH 20/148] Make the instructions flow in better order. --- diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index 774020b..aeea037 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -2,10 +2,13 @@ include::partial$workflow-change-banner.adoc[] -Fedora Magazine welcomes new writers to contribute their skill by writing an article or two! or five! +Fedora Magazine welcomes new writers to contribute their skill by writing an article or two... or five! There are several ways you can find something to write about: -We have a list of specific topics you can write about — so you don't need to come up with new ideas to write. Although you can definitely xref:writing-a-pitch.adoc[propose an article] if you have ideas. Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week! + * We have a list of specific topics to start with — so you don't need to come up with new ideas to write. + * You can also xref:writing-a-pitch.adoc[propose an article] if you have your own idea. + +Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week! -**See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.** +If this is your first contribution, you will need to xref:getting-access.adoc[get access] first. -Also, if this is your first contribution, you will need to xref:getting-access.adoc[get access] first. \ No newline at end of file +**Need help on how to write better? See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.** \ No newline at end of file From c569ccac6fcdc35fed15a5de936591743beb4911 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Oct 10 2019 13:28:49 +0000 Subject: [PATCH 21/148] Use implicit numbering which makes diffs better --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index c670414..1e64574 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -8,12 +8,12 @@ These tips will help your article sail through editing. Be kind to your editor(s Primary rule: don’t get too fancy. Legibility is important. -1. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write `dnf install foo` in the middle of a sentence, write __dnf install foo__. -2. **Use italics for system objects you mention in a sentence:** +. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write `dnf install foo` in the middle of a sentence, write __dnf install foo__. +. **Use italics for system objects you mention in a sentence:** ** GUI or CLI elements like button text or menu entries ** other prompts the reader must find on the screen ** commands or package names -3. **Use the Preformatted style in the WordPress editor for command line input or output.** Use a shell prompt ($ or #) only where it genuinely affects the meaning, or to set the input apart from output. It also helps to use boldface for the input itself: +. **Use the Preformatted style in the WordPress editor for command line input or output.** Use a shell prompt ($ or #) only where it genuinely affects the meaning, or to set the input apart from output. It also helps to use boldface for the input itself: + [subs=quotes] ---- @@ -23,46 +23,46 @@ output line 2 ---- -4. **Use boldface only for an extremely important phrase or statement.** +. **Use boldface only for an extremely important phrase or statement.** == Grammar and style tips -1. **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. +. **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. ** Incorrect heading: __Use Sentence Case for Post Titles in Fedora Magazine__ ** Correct heading: __Use sentence case for post titles in Fedora Magazine__ -2. **Check spelling and grammar.** Nobody likes nitpicky comments about this. Check your work before you send it to an editor. Editors: double-check all the work, that’s your job! -3. **Write clearly and use shorter sentences.** Brevity is good. Clarity is better. Don’t be excessively wordy when avoidable. If a longer sentence is easier to read, use the extra words. -4. **Avoid passive voice.** Passive voice is the use of the object of a sentence as the subject. For example: +. **Check spelling and grammar.** Nobody likes nitpicky comments about this. Check your work before you send it to an editor. Editors: double-check all the work, that’s your job! +. **Write clearly and use shorter sentences.** Brevity is good. Clarity is better. Don’t be excessively wordy when avoidable. If a longer sentence is easier to read, use the extra words. +. **Avoid passive voice.** Passive voice is the use of the object of a sentence as the subject. For example: ** __Active voice__: The troops defeated the enemy. ** __Passive voice__: The enemy was defeated by the troops. -5. **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: +. **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: ** __Weak, passive voice__: Setting the foobar configuration option will make the application listen on all interfaces. ** __Strong, active voice__: Set the foobar configuration option to make the application listen on all interfaces. -6. **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. +. **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. ** __Weak__: Zambone is an app used for managing your private documents on a server. ** __Strong__: Zambone manages your private documents on a server. Or: Use Zambone to manage your private documents on a server. ** __Weak__: When setting up a file server, it is important to plan the directory structure carefully. ** __Strong__: Plan the directory structure of the file server carefully before you set it up. -7. **Use standard US English for spelling and other international differences.** US English is the lingua franca for the Fedora Project overall. -8. **Have a smooth flow from general information to specific instructions.** If you’re not sure how to structure your article like this, check out our starter template. +. **Use standard US English for spelling and other international differences.** US English is the lingua franca for the Fedora Project overall. +. **Have a smooth flow from general information to specific instructions.** If you’re not sure how to structure your article like this, check out our starter template. == Content tips These tips are about things to do — and avoid — in what you tell users to do. Remember that thousands of readers trust Fedora Magazine to tell them how to carry out tasks. Be responsible and helpful, advocate best practices, and respect the user’s security and choice. -1. **Leave packaged files alone.** Processes should not involve editing files under system folders like __/usr__ or __/lib*__. Edit __/etc__ or a user-specific configuration in the home directory. -2. **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. -3. **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. -4. **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). -5. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: +. **Leave packaged files alone.** Processes should not involve editing files under system folders like __/usr__ or __/lib*__. Edit __/etc__ or a user-specific configuration in the home directory. +. **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. +. **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. +. **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). +. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: ** __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ -6. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. +. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. == WordPress tips -1. **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. -2. **Provide a featured image.** Look at https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[the information here] for tips on featured images. You can also feel free to ask the editors to assign this for you. If you make your own image, try to match the style of other images. Use the assets provided https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[in the featured image guide]. Don’t add your own fonts or deviate from the guide. -3. **Use good SEO practices.** Use the SEO plugin provided to maximize the search ranking of the article. Aim for a “green” rating in the __Publish__ box at top right of your article’s edit screen. Follow these guidelines: +. **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. +. **Provide a featured image.** Look at https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[the information here] for tips on featured images. You can also feel free to ask the editors to assign this for you. If you make your own image, try to match the style of other images. Use the assets provided https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[in the featured image guide]. Don’t add your own fonts or deviate from the guide. +. **Use good SEO practices.** Use the SEO plugin provided to maximize the search ranking of the article. Aim for a “green” rating in the __Publish__ box at top right of your article’s edit screen. Follow these guidelines: ** Enter a meaningful keyword in the SEO box under your article. (Most articles shouldn’t use __Fedora__.) ** If the Snippet doesn’t give an effective introduction or summary in the sample search result, rewrite it. ** Don’t feel like you have to eliminate every warning. A “green” rating overall is the only goal. From 26adda8423266252fa1b4c89a01ef0e80b204311 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Oct 10 2019 13:32:03 +0000 Subject: [PATCH 22/148] Add tip on unnecessary future tense --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 1e64574..52eb616 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -38,6 +38,9 @@ output line 2 . **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: ** __Weak, passive voice__: Setting the foobar configuration option will make the application listen on all interfaces. ** __Strong, active voice__: Set the foobar configuration option to make the application listen on all interfaces. +. **Avoid unnecessary future tense.** Unless you're actually talking about future plans or publications, present tense is best. +** __Unnecessary future tense__: When you select **Run**, your program will start. +** __Present tense__: When you select **Run**, your program starts. . **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. ** __Weak__: Zambone is an app used for managing your private documents on a server. ** __Strong__: Zambone manages your private documents on a server. Or: Use Zambone to manage your private documents on a server. From 33e07e55407aeee9e9a42d9f4a39a6dcdbd6618b Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Oct 18 2019 12:45:34 +0000 Subject: [PATCH 23/148] mention details about the eitorial meeting --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 5502fda..63ad11d 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -2,6 +2,10 @@ The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine. +:hash: # + +Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. + == Agenda @@ -95,4 +99,4 @@ Subject: Editorial board meeting recap YYYY-Mmm-DD The following types of articles generally can route around the weekly meetings. This helps us get critical information out to the audience without waiting for the next board meeting. -* **Security updates:** Critical security updates that affect a broad user audience are pre-authorized. Generally an editor will write the update article. If possible, one other editor does a quick spot check. If that would affect the timing, however, the posting editor simply publishes the article and notifies the magazine list. An example is a Firefox security issue. \ No newline at end of file +* **Security updates:** Critical security updates that affect a broad user audience are pre-authorized. Generally an editor will write the update article. If possible, one other editor does a quick spot check. If that would affect the timing, however, the posting editor simply publishes the article and notifies the magazine list. An example is a Firefox security issue. From 912e55fa873fc43f78f9cb8b60496c911c7e9290 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Oct 31 2019 13:03:19 +0000 Subject: [PATCH 24/148] remove the new workflow banner --- diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc index ed579fc..e69de29 100644 --- a/modules/ROOT/partials/workflow-change-banner.adoc +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -1 +0,0 @@ -NOTE: Starting 20 September 2019, the Fedora Magazine is testing a xref:workflow.adoc[new editorial workflow] — see the page to learn how to propose new articles or write some. \ No newline at end of file From 92ad1483ce679b72bf166ebe477648ebf644788c Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Oct 31 2019 13:06:47 +0000 Subject: [PATCH 25/148] add the 'sign in to Taiga' step --- diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index 096790d..a47e89f 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -7,5 +7,7 @@ include::partial$workflow-change-banner.adoc[] **2. Sign in to the Fedora Magazine**: Now, using your FAS Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here]. +**3. Sign in to the Taiga board**: Again, using your FAS Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board] using the __OpenID Connect__ button. + **3. Join the Magazine list and introduce yourself**: Next up, subscribe to the https://lists.fedoraproject.org/admin/lists/magazine@lists.fedoraproject.org[Fedora Magazine mailing list]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review. From 36928d568d5b4f05a97077a25d4d0f96d0e50b48 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Nov 11 2019 19:16:35 +0000 Subject: [PATCH 26/148] Add instructions for adding writers --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index c1867d1..face98f 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -14,4 +14,4 @@ ** xref:editorial-meetings.adoc[Editorial Meetings] ** xref:approving-comments.adoc[Approving Comments] ** xref:creating-an-image.adoc[Creating a Featured Image] - +** xref:adding-a-writer.adoc[Adding a Writer] diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc new file mode 100644 index 0000000..a8e6859 --- /dev/null +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -0,0 +1,7 @@ += Adding a Writer + +When a new writer joins the Magazine, they usually want to track their work in our kanban. Whether they take an existing article or suggest their own, an editor needs to add them to the kanban's list of permissions. + +. Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already. +. Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. +. In the kanban instance, select _Admin_ on the left navigation bar, and then select _Members_. Select _New Member_ and add the contributor as a _Writer_ via their FAS email address (this is not their _@fedoraproject.org_ alias). This puts them on the team. From 05c06399ac9233ac52921ba32327b3bf11668d9d Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Nov 12 2019 20:09:01 +0000 Subject: [PATCH 27/148] Update font listing for images --- diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc index ac2577b..12e8c93 100644 --- a/modules/ROOT/pages/creating-an-image.adoc +++ b/modules/ROOT/pages/creating-an-image.adoc @@ -38,10 +38,15 @@ You can use the assets inside this file to start with the right-sized document, There are a few fonts that are commonly used in featured images. You are encouraged to use these fonts in your images to help featured images fit into the general “theme” that other images follow. They are all freely available at the links provided. The fonts we commonly use on the Fedora Magazine are listed below. -http://www.fontsquirrel.com/fonts/montserrat[Montserrat] (friendly and Sans-like) -http://fontsquirrel.com/fonts/roboto-slab[Roboto Slab] (friendly with serifs) -http://www.fontsquirrel.com/fonts/molot[Molot] (heavier font, feels technical) -http://www.fontsquirrel.com/fonts/grand-hotel[Grand Hotel] (for a fancy script-y feel) +. https://www.fontsquirrel.com/fonts/open-sans[Open Sans] (especially the "Light" variant) +. https://www.fontsquirrel.com/fonts/bungee[Bungee] (for a slightly technical but fun feel) +. https://www.fontsquirrel.com/fonts/oswald[Oswald] (for a more technical feel) +. https://www.fontsquirrel.com/fonts/josefin-slab[Josefin Slab] (friendly with serifs) +. https://www.fontsquirrel.com/fonts/zilla-slab[Zilla Slab] (friendly with serifs) +. https://www.fontsquirrel.com/fonts/grand-hotel[Grand Hotel] (for a fancy script-y feel) +. https://www.fontsquirrel.com/fonts/montserrat[Montserrat] (friendly and Sans-like) +. https://www.fontsquirrel.com/fonts/roboto-slab[Roboto Slab] (friendly with serifs) +. https://www.fontsquirrel.com/fonts/molot[Molot] (heavier font, feels technical) To use these fonts on your Fedora system, download the font and unpack the OTF or TTF file (if required) into your ~/.fonts folder. Then update your font cache: From 37b09e4022783e7bd8252488a9eb65bb9db9fbe5 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Dec 04 2019 12:49:00 +0000 Subject: [PATCH 28/148] Fix link to proposals --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 63ad11d..9deb159 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -76,7 +76,7 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #topic 6/ Article proposals to clarify / approve #info Review the the article proposals and decide about what's next — a new article spec? more discussion? - #link Article proposals: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/issues + #link Article proposals: https://pagure.io/fedora-magazine-proposals/issues === 7/ Open floor From 9809008bb294454fb648d8487060f4b38d265b29 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Dec 04 2019 12:53:03 +0000 Subject: [PATCH 29/148] Update modules/ROOT/pages/editorial-meetings.adoc --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 9deb159..7f8ddc9 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -14,15 +14,13 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #startmeeting Magazine editorial board #meetingname magazine #topic Roll call - #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc + #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc rwaltr === Agenda #topic Agenda - #info Fedora Magazine has moved to a new Editorial Workflow #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ - #info Following is the meeting agenda that is a slightly different than before: #info -- 1/ Last week's stats -- #info -- 2/ In progress followup -- #info -- 3/ Finished articles to review -- From a87f9ee2de88872fcefe9eec7c29e8b28f1533ce Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Dec 05 2019 16:52:35 +0000 Subject: [PATCH 30/148] Add some nagivation to the bottom of each page --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index c5ea4e1..b88dd96 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -26,3 +26,6 @@ __The following article serves as an example outline for proposing a new pitch f * Introducing ZNC * Download, installing, and configuring ZNC on a Fedora machine * Configuring IRC client to use your ZNC bouncer + +== Workflow +**Next step:** xref:workflow-clarification.adoc[Clarification] diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index db68dc1..4fa5353 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -20,4 +20,9 @@ Opinions and additional relevant information is welcome from anyone. When the review is complete, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. -This card now represent a specific articles and goes through all the other steps of the workflow. \ No newline at end of file +This card now represent a specific articles and goes through all the other steps of the workflow. + +== Workflow +**Previous step:** xref:workflow-article-proposal.adoc[Article Proposal] + +**Next step:** xref:writing-an-article.adoc[Writing] diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index adcf91c..2de9cf9 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -31,4 +31,9 @@ Since multiple people will be potentially completing this step, they need to coo When done, indicate that in the comments. -If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. \ No newline at end of file +If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +== Workflow +**Previous step:** xref:workflow-review.adoc[Review] + +**Next step:** xref:workflow-publishing.adoc[Publishing] diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index 8411800..c1bab49 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -12,4 +12,7 @@ Articles that are ready to be published are in the __Queued__ column in the ht After publishing or scheduling them in Wordpress, move the card to the __Published__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. -That's it! \ No newline at end of file +That's it! + +== Workflow +**Previous step:** xref:workflow-edit-image.adoc[Edit & Image] diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index da7e1e5..c93b8c2 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -17,4 +17,9 @@ If the article is good to go, a member of the Editorial Board simply moves it to === When article needs changes -If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __In Progress__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. \ No newline at end of file +If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __In Progress__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. + +== Workflow +**Previous step:** xref:writing-an-article.adoc[Writing] + +**Next step:** xref:workflow-edit-image.adoc[Edit & Image] diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 1550db9..7bc4253 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -32,4 +32,9 @@ As you write your draft, try to understand and follow the xref:tips-for-writers. And that's it! -Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. \ No newline at end of file +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. + +== Workflow +**Previous step:** xref:workflow-clarification.adoc[Clarification] + +**Next step:** xref:workflow-review.adoc[Review] From dde3d38a6ad8f9085930a560b716d7a95921fe5e Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Dec 12 2019 09:34:47 +0000 Subject: [PATCH 31/148] ask people to log in to taiga when proposing an idea --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index b88dd96..d8af30e 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -12,7 +12,9 @@ The proposal can be either just an idea, or a specific pitch (an example is belo If you have a https://admin.fedoraproject.org/accounts/[Fedora account], the preferred way is to https://pagure.io/fedora-magazine-proposals/issues[open an issue in the Fedora Magazine Proposals issue tracker]. -If you don't have a https://admin.fedoraproject.org/accounts/[Fedora account], you can email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. +Alternatively, if you don't have a https://admin.fedoraproject.org/accounts/[Fedora account], you can email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. + +TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] — click on the "OpenID Connect" button on the login form to log in with your Fedora Account. That is required before you can be added to the board as a writer. == A specific pitch example From 19c017a6b797449450d267d82418536023aed275 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jan 08 2020 08:55:56 +0000 Subject: [PATCH 32/148] Add link to the Magazine Wordpress --- diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 7bc4253..46a305f 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -20,7 +20,7 @@ __Writing an article requires write access to our https://teams.fedoraproject.or === 2. Write it -**Write** your article either in Wordpress (create a new article there) or anywhere you prefer. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. +**Write** your article either https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there) or anywhere you prefer. Wordpress, however, will be the easiest for the editors to review and publish later. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. From 238c1e80a5332837f97d6d8eaf991769cbab01ea Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Feb 19 2020 13:46:26 +0000 Subject: [PATCH 33/148] Adjust heading for readability --- diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index fb3d7a1..556038f 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[] http://fedoramagazine.org[Fedora Magazine] is a WordPress-based site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.) -== What is the content of the Magazine +== What does the Magazine publish? The content of the magazine varies, but mostly includes: From 080d3b60dfb68b90ae781a0a5912793d4d686c96 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Mar 11 2020 21:03:36 +0000 Subject: [PATCH 34/148] Add background image information. --- diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc index 12e8c93..3d2a527 100644 --- a/modules/ROOT/pages/creating-an-image.adoc +++ b/modules/ROOT/pages/creating-an-image.adoc @@ -34,6 +34,12 @@ Save this as a new file with a different name. You can use the assets inside this file to start with the right-sized document, with some pre-configured backgrounds. Feel free to look at other SVGs for guidance. If you don’t have experience with these images, try to stick with fonts and motifs that you see in recent banners. But also feel free to experiment! For instance, use photographs (freely licensed, such as CC-BY or CC-BY-SA) with a text overlay for a nice look. https://unsplash.com/[Unsplash.com] has a large library of images in the public domain you can use to get started. +=== Background images + +You can find compatibly licensed images at https://unsplash.com[Unsplash], or you can try other image search engines. Be sure to choose only images with CC0, CC-BY, or CC-BY-SA licenses. (Commercial and derivative uses must be permissible.) + +Before you import your background to the SVG, scale and trim it using GIMP or another image editor to an 1890x800 size, and a JPG quality of about 75-80%. This keeps the SVG from being too large -- it will reduce the size from many MB to just a few hundred KB. + === Fonts There are a few fonts that are commonly used in featured images. You are encouraged to use these fonts in your images to help featured images fit into the general “theme” that other images follow. They are all freely available at the links provided. The fonts we commonly use on the Fedora Magazine are listed below. From dba0e84fa4e5aff7c3b7b7b68b440fd6f8551cbe Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: May 06 2020 12:49:16 +0000 Subject: [PATCH 35/148] Fix column name in publishing workflow --- diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index c1bab49..c474122 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -10,7 +10,7 @@ A member of the Editorial board either publishes or schedules an article for pub Articles that are ready to be published are in the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. -After publishing or scheduling them in Wordpress, move the card to the __Published__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +After publishing or scheduling them in Wordpress, move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. That's it! From efc0b6da422f58c81a59b1f9c3217375fd3169ff Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: May 13 2020 10:14:48 +0000 Subject: [PATCH 36/148] mention the magazine-schedule script and add some comments --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 7f8ddc9..8998f35 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -4,21 +4,28 @@ The goal of this meeting is to set and execute a publishing schedule of appropri :hash: # -Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. +Meetings happen every week in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. -== Agenda +== Chairing the meeting + +The meeting is powered by https://fedoraproject.org/wiki/Zodbot[zodbot]. You can use the following commands the start the meeting, to set topics, record important information and decisions, etc. === Roll call +To start the meeting, run the following set of commands. + #startmeeting Magazine editorial board #meetingname magazine #topic Roll call - #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc rwaltr + #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr +People will then join using a `.hello2` or a `.hello NICK` command. === Agenda +This is the standard agenda. Announcing it in advance helps newcomers understand the structure of the meeting. + #topic Agenda #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ #info -- 1/ Last week's stats -- @@ -33,6 +40,9 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. === 1/ Last week's stats #topic 1/ Last week's stats + +First, let's look back at the previous week in terms of pageviews. This data can be obtained in the https://fedoramagazine.org/admin[Fedora Magazine Wordpress]. On the https://fedoramagazine.org/wp-admin/index.php[Dashboard], scroll down to Stats by Jetpack. + #info Week of : K pageviews -- @@ -42,6 +52,10 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban +Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work. + +Anything that's already finished can be moved to the Finished column. + === 3/ Finished articles to review @@ -49,6 +63,8 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback. #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban +Authors mark their articles as finished by moving them to this column. Review the articles and ehtier move them to the To Edit column, or in case they need some additional work, ask the author in the card about it and move it back the In Progress. + === 4/ Articles to edit @@ -56,6 +72,8 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #info Looking at the 'to edit' column, assign an editor and a cover image creator. #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban +Assign an editor and a cover image designer to each article so it can be moved forward. + === 5/ Publishing schedule @@ -64,11 +82,32 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content. #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban +Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting. + +Decide which articles should be published when and set the dates for each card on the board. + +The next step is to vote on the publishing schedule along with other attendees of the meeting. A proposal of the schedule has the following format: + #proposed #agreed PUBLISHING SCHEDULE: DAY DATE, NAME (NICK:edit/NICK:image) --  DAY DATE, NAME (NICK:edit/NICK:image) -- DAY DATE, NAME (NICK:edit/NICK:image) -- +This can be generated by a script. Run: + + $ podman --rm -it asamalik/magazine-schedule + +The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly. + +Find more information about the script in the https://github.com/asamalik/magazine-schedule[asamalik/magazine-schedule github repository]. + +When the schedule is set and agreed upon, announce it by: + + #agreed PUBLISHING SCHEDULE: + DAY DATE, NAME (NICK:edit/NICK:image) --  + DAY DATE, NAME (NICK:edit/NICK:image) -- + DAY DATE, NAME (NICK:edit/NICK:image) -- + === 6/ Article proposals to clarify / approve @@ -76,6 +115,10 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. #info Review the the article proposals and decide about what's next — a new article spec? more discussion? #link Article proposals: https://pagure.io/fedora-magazine-proposals/issues +The final step is to review and approve proposals. This is important for our contibutors so they can start writing their articles. + +When there are two or more +1's in an issue, create a card on the board, post the link to it back to the proposal, and close it. + === 7/ Open floor @@ -89,7 +132,8 @@ Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the https://webchat. === After the meeting -Send the minutes to the list +Send the minutes to the list. That includes the three links zodbot prints out after the meeting is ended. + Subject: Editorial board meeting recap YYYY-Mmm-DD From ba89e16c1ef0275db20992caf1bbeb6cce1ed085 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 03 2020 11:57:50 +0000 Subject: [PATCH 37/148] Update modules/ROOT/pages/editorial-meetings.adoc --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 8998f35..13405e6 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -18,7 +18,7 @@ To start the meeting, run the following set of commands. #startmeeting Magazine editorial board #meetingname magazine #topic Roll call - #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr + #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr bcotton People will then join using a `.hello2` or a `.hello NICK` command. From 5e1a93b5bafbf8d5f6cc75fe5daf5c367c0545a3 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 03 2020 12:19:48 +0000 Subject: [PATCH 38/148] Update modules/ROOT/pages/editorial-meetings.adoc --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 13405e6..e847965 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -95,7 +95,7 @@ The next step is to vote on the publishing schedule along with other attendees o This can be generated by a script. Run: - $ podman --rm -it asamalik/magazine-schedule + $ podman run --rm -it asamalik/magazine-schedule The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly. From b1165ef54d1cd0ce09d62b0f479da6b6003d0803 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Jun 08 2020 20:40:33 +0000 Subject: [PATCH 39/148] Add the image tips Paul shared on the mailing list --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 52eb616..62ddb21 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -61,6 +61,17 @@ These tips are about things to do — and avoid — in what you tell users to do ** __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ . **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. +== Image and screenshot tips + +. **Use a fresh, standard Fedora Workstation**, not your personal desktop or setup. +(It's best to make a VM with a fresh Fedora Workstation install, and do the steps there.) +If you're showing something that *relies* on another desktop, do a fresh installation and use that. +. **Set screen resolution at a reasonable but not too high resolution**, such as 1280x960 or 1280x800. +. If you're only showing a browser window, make it fairly large on the screen and **screenshot only the browser**. (Hint: you can use the Screenshot app for this!) +. If you're only showing an application, **use the default size of the app to screenshot it**. +. **Upload and use that original media in your article.** +If the shot is large, like a large browser window, app, or whole screen, choose a medium size thumbnail and let WordPress handle the conversion. + == WordPress tips . **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. From 0c43a221f7bc92145251797399e7fbd273d34a8b Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Jun 23 2020 14:41:37 +0000 Subject: [PATCH 40/148] Add the Editor of the Week role --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index face98f..7014ccc 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -11,6 +11,7 @@ ** xref:getting-access.adoc[Getting Access] ** xref:tips-for-writers.adoc[Tips for Writers] * xref:editorial.adoc[Contributing as an Editor] +** xref:editor-of-the-week.adoc[Editor of the Week] ** xref:editorial-meetings.adoc[Editorial Meetings] ** xref:approving-comments.adoc[Approving Comments] ** xref:creating-an-image.adoc[Creating a Featured Image] diff --git a/modules/ROOT/pages/editor-of-the-week.adoc b/modules/ROOT/pages/editor-of-the-week.adoc new file mode 100644 index 0000000..15456d3 --- /dev/null +++ b/modules/ROOT/pages/editor-of-the-week.adoc @@ -0,0 +1,30 @@ += Fedora Magazine Editor of the Week + +In order to promote accountability and spread the workload, we have the Editor of the Week role for Fedora Magazine. + +== Selection + +The Editor of the Week will be selected by volunteer basis at each week's Magazine Editorial Board meeting. +Editors who cannot attend the meeting can volunteer by contacting the current Editor of the Week prior to the start of the meeting. +If the meeting is canceled, the current Editor of the Week should coordinate selection via the asynchronous communication channel (i.e. mailing list or Discourse). + +If multiple Editors volunteer to be the Editor of the Week, we expect they can work it out among themselves. +However, in general we should prefer the volunteer who has least recently served as Editor of the Week in order to fairly distribute the workload. + +If no one volunteers, then the current Editor of the Week should request volunteers via the asynchronous communication channel. + +== Term + +The term of the Editor of the Week is one calendar week (beginning the Sunday following the meeting where the Editor of the Week was selected and ending on Saturday). + +== Responsibilities + +The Editor of the Week is expected to: + +* Routinely moderate comments (2-3 times a day is ideal) +* Ensure the publication schedule is followed +* Welcome new contributors +* Convert approved proposals to Taiga cards +* Chair the weekly xref:editorial-meetings.adoc[Magazine Editorial Board meeting] + +Note that Editors who are not the Editor of the Week may still perform the tasks above. diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index e847965..aa0a928 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -5,6 +5,7 @@ The goal of this meeting is to set and execute a publishing schedule of appropri :hash: # Meetings happen every week in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. +Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week]. == Chairing the meeting @@ -34,7 +35,8 @@ This is the standard agenda. Announcing it in advance helps newcomers understand #info -- 4/ Articles to edit -- #info -- 5/ Publishing schedule -- #info -- 6/ Article proposals to clarify / approve -- - #info -- 7/ Open floor -- + #info -- 7/ Editor of the Week -- + #info -- 8/ Open floor -- === 1/ Last week's stats @@ -120,9 +122,15 @@ The final step is to review and approve proposals. This is important for our con When there are two or more +1's in an issue, create a card on the board, post the link to it back to the proposal, and close it. -=== 7/ Open floor +=== 7/ Editor of the Week - #topic 7/ Open floor +Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week]. + + #info XXXX will be Editor of the Week next week + +=== 8/ Open floor + + #topic 8/ Open floor === Meeting ends diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc index 5116ca0..ea9a4fe 100644 --- a/modules/ROOT/pages/editorial.adoc +++ b/modules/ROOT/pages/editorial.adoc @@ -3,6 +3,7 @@ include::partial$workflow-change-banner.adoc[] The duties of an editor are much like any blog owner. Occasionally editors also xref:contributing.adoc[contribute content] when the queue or backlog of content is running a little low. +Editors take turns serving as the xref:editor-of-the-week.adoc[Editor of the Week]. Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently. From 7a127a47f71a8b6999911d90e69768e02726e83e Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 24 2020 11:46:26 +0000 Subject: [PATCH 41/148] switching to Discourse --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index aa0a928..0645dc9 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -115,7 +115,7 @@ When the schedule is set and agreed upon, announce it by: #topic 6/ Article proposals to clarify / approve #info Review the the article proposals and decide about what's next — a new article spec? more discussion? - #link Article proposals: https://pagure.io/fedora-magazine-proposals/issues + #link Article proposals in our forum: https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine The final step is to review and approve proposals. This is important for our contibutors so they can start writing their articles. @@ -140,7 +140,7 @@ Before the end of the meeting, we need to select next week's xref:editor-of-the- === After the meeting -Send the minutes to the list. That includes the three links zodbot prints out after the meeting is ended. +Send the minutes to the forum. That includes the three links zodbot prints out after the meeting is ended. Subject: Editorial board meeting recap YYYY-Mmm-DD diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index a47e89f..6274312 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -7,7 +7,7 @@ include::partial$workflow-change-banner.adoc[] **2. Sign in to the Fedora Magazine**: Now, using your FAS Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here]. -**3. Sign in to the Taiga board**: Again, using your FAS Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board] using the __OpenID Connect__ button. +**3. Sign in to the Taiga board**: Again, using your FAS Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board]. -**3. Join the Magazine list and introduce yourself**: Next up, subscribe to the https://lists.fedoraproject.org/admin/lists/magazine@lists.fedoraproject.org[Fedora Magazine mailing list]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review. +**3. Join the Magazine forum and introduce yourself**: And finally, join the discussion in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 556038f..2c416ea 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -22,7 +22,7 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin We also have regular xref:editorial-meetings.adoc[editorial board meetings]. * IRC Channel: https://webchat.freenode.net/?channels=#fedora-magazine[#fedora-magazine] -* Mailing list: https://lists.fedoraproject.org/admin/lists/magazine@lists.fedoraproject.org/[magazine] +* Forum: https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum] diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index d8af30e..1d73de9 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -6,13 +6,11 @@ image::fedora-magazine-workflow-1.jpg[,100%,] Anyone is welcome to propose an article! -The proposal can be either just an idea, or a specific pitch (an example is below). Proposing an article doesn't automatically mean the same person needs to write it. Having a good set of ideas helps writers to just write what they know is relevant for the Magazine, without necessarily thinking about new content just so they can write something. +Proposals can be ideas or specific pitches (an example is below). Proposing an article doesn't automatically mean the same person needs to write it. Having a good set of ideas helps writers to just write what they know is relevant for the Magazine, without necessarily thinking about new content just so they can write something. == Submitting an idea -If you have a https://admin.fedoraproject.org/accounts/[Fedora account], the preferred way is to https://pagure.io/fedora-magazine-proposals/issues[open an issue in the Fedora Magazine Proposals issue tracker]. - -Alternatively, if you don't have a https://admin.fedoraproject.org/accounts/[Fedora account], you can email your proposal to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine list]. +Join the community in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic. TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] — click on the "OpenID Connect" button on the login form to log in with your Fedora Account. That is required before you can be added to the board as a writer. diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 4fa5353..7d1f463 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -8,19 +8,17 @@ The Editorial Board reviews each proposal and creates a specific article descrip Proposals might be discussed with the person who proposed them, with subject matter experts, and anyone who wants (or has the technical ability to) give an input. We encourage anyone in the community to provide feedback to the proposals! -== Where to discuss +== Discussing and approving proposals -The discussion happens in the respective issue or email thread. - -Issues are submitted in the https://pagure.io/fedora-magazine-proposals/issues[Fedora Magazine Proposals issue tracker], and emails are sent to the https://lists.fedoraproject.org/admin/lists/magazine.lists.fedoraproject.org/[Fedora Magazine mailing list]. +Proposals are submitted to the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum] as topics, and discussion happens right there. Opinions and additional relevant information is welcome from anyone. -== Writing an article spec +If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved. -When the review is complete, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. +When a proposal is approved, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. -This card now represent a specific articles and goes through all the other steps of the workflow. +This card now represents a specific article and goes through all the other steps of the workflow. == Workflow **Previous step:** xref:workflow-article-proposal.adoc[Article Proposal] diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index 5fec756..023f034 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -17,6 +17,6 @@ An initial proposal lands in the __idea__ state. After some clarification, a spe == Tracking -Proposals in the **__idea__** state are represented issues in our https://pagure.io/fedora-magazine-proposals/issues[Fedora Magazine Proposals issue tracker]. Everyone is welcome to submit one! +Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one! Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! \ No newline at end of file From 6f69f2cdf2f416849598a32cc35ac9f91f871a18 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 24 2020 11:53:26 +0000 Subject: [PATCH 42/148] add a discourse banner --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index a8e6859..829460b 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -1,5 +1,7 @@ = Adding a Writer +include::partial$workflow-change-banner.adoc[] + When a new writer joins the Magazine, they usually want to track their work in our kanban. Whether they take an existing article or suggest their own, an editor needs to add them to the kanban's list of permissions. . Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already. diff --git a/modules/ROOT/pages/editor-of-the-week.adoc b/modules/ROOT/pages/editor-of-the-week.adoc index 15456d3..d923b41 100644 --- a/modules/ROOT/pages/editor-of-the-week.adoc +++ b/modules/ROOT/pages/editor-of-the-week.adoc @@ -1,5 +1,7 @@ = Fedora Magazine Editor of the Week +include::partial$workflow-change-banner.adoc[] + In order to promote accountability and spread the workload, we have the Editor of the Week role for Fedora Magazine. == Selection diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 0645dc9..9b40a10 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -1,5 +1,7 @@ = Fedora Magazine editorial meetings +include::partial$workflow-change-banner.adoc[] + The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine. :hash: # diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc index e69de29..c58f501 100644 --- a/modules/ROOT/partials/workflow-change-banner.adoc +++ b/modules/ROOT/partials/workflow-change-banner.adoc @@ -0,0 +1 @@ +NOTE: Starting 25 June 2020, Magazine-related **discussions have moved** to a new place: the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. New article proposals are also being submitted there. \ No newline at end of file From 56264722193bdebc384e9fcc0381548e70b225bf Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 24 2020 15:25:45 +0000 Subject: [PATCH 43/148] First stab at a checklist --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 7014ccc..ef0c834 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -12,6 +12,7 @@ ** xref:tips-for-writers.adoc[Tips for Writers] * xref:editorial.adoc[Contributing as an Editor] ** xref:editor-of-the-week.adoc[Editor of the Week] +** xref:editorial-checklist.adoc[Editorial Checklist] ** xref:editorial-meetings.adoc[Editorial Meetings] ** xref:approving-comments.adoc[Approving Comments] ** xref:creating-an-image.adoc[Creating a Featured Image] diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc new file mode 100644 index 0000000..b56fe77 --- /dev/null +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -0,0 +1,28 @@ += Checklist for editors + +Editors should follow this checklist to help articles meet standards before being published. + +== Formatting + +* [ ] After the introductory paragraph, include the __--- Read More ---__ element. This causes RSS readers to visit the site to view the article. +* [ ] Remove any monospace text mixed into paragraphs, such as elements. Either convert these to italics, or move them into Preformatted blocks in WordPress, fixing surrounding text as necessary. + +== Style + +* [ ] Check the article for adherence to the xref:tips-for-writers.adoc[guidelines and tips for writers]. **This may take a while, so leave yourself sufficient time for this step.** +* [ ] Set all article and section titles to sentence case. + +== Usage + +* [ ] Eliminate use of __I, we, us,__ and __our__ in the article, rewriting where necessary. Articles should not refer to the author if avoidable. + +== SEO and metadata + +* [ ] Set an appropriate https://yoast.com/focus-keyword/[focus keyword]. +* [ ] Address any article shortcomings that affect readability. (It may not be possible to turn the readability score to "green" in all cases.) +* [ ] Categorize the article. The default "Fedora Project community" category should rarely be used. +* [ ] Add tags for article subject matter. Use as many as possible. + +== Publishing + +* [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise. diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc index ea9a4fe..e2f8718 100644 --- a/modules/ROOT/pages/editorial.adoc +++ b/modules/ROOT/pages/editorial.adoc @@ -5,6 +5,8 @@ include::partial$workflow-change-banner.adoc[] The duties of an editor are much like any blog owner. Occasionally editors also xref:contributing.adoc[contribute content] when the queue or backlog of content is running a little low. Editors take turns serving as the xref:editor-of-the-week.adoc[Editor of the Week]. +Editors follow an xref:editorial-checklist.adoc[editorial checklist] to help articles meet a quality and content bar, and to ensure they're well searchable. + Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently. Like most blogs and news sites, the Magazine receives feedback and comments from the public. Editors xref:approving-comments.adoc[moderate comments based on common guidelines]. They ensure that discussions stay constructive and discourage trolls and other bad actors. From 4a824014e629a0da0562aebc38010d1f507effdc Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jun 25 2020 09:12:11 +0000 Subject: [PATCH 44/148] reword a sentence in article proposals --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 1d73de9..3203286 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -6,7 +6,7 @@ image::fedora-magazine-workflow-1.jpg[,100%,] Anyone is welcome to propose an article! -Proposals can be ideas or specific pitches (an example is below). Proposing an article doesn't automatically mean the same person needs to write it. Having a good set of ideas helps writers to just write what they know is relevant for the Magazine, without necessarily thinking about new content just so they can write something. +Proposals can be ideas or specific pitches (an example is below). Proposing an article doesn't automatically mean the same person needs to write it. Having a good set of ideas helps writers to write what they know is relevant for the Magazine. == Submitting an idea From 1a1cd5baa4738c803b19b52b3810b905d9339143 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 26 2020 20:11:09 +0000 Subject: [PATCH 45/148] Note on tag creation --- diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc index b56fe77..b864727 100644 --- a/modules/ROOT/pages/editorial-checklist.adoc +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -21,7 +21,7 @@ Editors should follow this checklist to help articles meet standards before bein * [ ] Set an appropriate https://yoast.com/focus-keyword/[focus keyword]. * [ ] Address any article shortcomings that affect readability. (It may not be possible to turn the readability score to "green" in all cases.) * [ ] Categorize the article. The default "Fedora Project community" category should rarely be used. -* [ ] Add tags for article subject matter. Use as many as possible. +* [ ] Add tags for article subject matter. Use as many as possible. As you type a new tag, observe the popup help. Try to choose relevant tags, and avoid creating new ones with trivial differences. == Publishing From e140555fae5a78b73950e086191fd8fa1a69881b Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 26 2020 20:23:25 +0000 Subject: [PATCH 46/148] Add section on featured images to editorial checklist --- diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc index b864727..1767d35 100644 --- a/modules/ROOT/pages/editorial-checklist.adoc +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -23,6 +23,11 @@ Editors should follow this checklist to help articles meet standards before bein * [ ] Categorize the article. The default "Fedora Project community" category should rarely be used. * [ ] Add tags for article subject matter. Use as many as possible. As you type a new tag, observe the popup help. Try to choose relevant tags, and avoid creating new ones with trivial differences. +== Featured images + +* [ ] Make sure the article has an appropriate xref:creating-an-image.adoc[featured image]. This is **not** the same as an image in the article text itself, and should not appear there. Use the Featured Image box in the document details in WordPress. +* [ ] Featured images should be included or submitted to the https://pagure.io/fedoramagazine-images[featured images repo on Pagure]. Refer to the xref:creating-an-image.adoc[documentation on featured images] for more information. + == Publishing * [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise. From 0338007e274ba9c4ecae13f3bfcca4b764cf0074 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 26 2020 20:26:07 +0000 Subject: [PATCH 47/148] Editorial checklist: add tip on Excerpt --- diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc index 1767d35..d868480 100644 --- a/modules/ROOT/pages/editorial-checklist.adoc +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -22,6 +22,7 @@ Editors should follow this checklist to help articles meet standards before bein * [ ] Address any article shortcomings that affect readability. (It may not be possible to turn the readability score to "green" in all cases.) * [ ] Categorize the article. The default "Fedora Project community" category should rarely be used. * [ ] Add tags for article subject matter. Use as many as possible. As you type a new tag, observe the popup help. Try to choose relevant tags, and avoid creating new ones with trivial differences. +* [ ] Add an Excerpt in the document details in WordPress. This shows up in the https://en.wikipedia.org/wiki/RSS[RSS] feed shown in https://start.fedoraproject.org[start page in Fedora's web browser defaults]. == Featured images From 36aa0d3483d15296e2db990b422ec7b16dfc8912 Mon Sep 17 00:00:00 2001 From: Stephen Snow Date: Jun 28 2020 04:00:31 +0000 Subject: [PATCH 48/148] Merge #11 `First stab at a checklist` --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 7014ccc..ef0c834 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -12,6 +12,7 @@ ** xref:tips-for-writers.adoc[Tips for Writers] * xref:editorial.adoc[Contributing as an Editor] ** xref:editor-of-the-week.adoc[Editor of the Week] +** xref:editorial-checklist.adoc[Editorial Checklist] ** xref:editorial-meetings.adoc[Editorial Meetings] ** xref:approving-comments.adoc[Approving Comments] ** xref:creating-an-image.adoc[Creating a Featured Image] diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc new file mode 100644 index 0000000..d868480 --- /dev/null +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -0,0 +1,34 @@ += Checklist for editors + +Editors should follow this checklist to help articles meet standards before being published. + +== Formatting + +* [ ] After the introductory paragraph, include the __--- Read More ---__ element. This causes RSS readers to visit the site to view the article. +* [ ] Remove any monospace text mixed into paragraphs, such as elements. Either convert these to italics, or move them into Preformatted blocks in WordPress, fixing surrounding text as necessary. + +== Style + +* [ ] Check the article for adherence to the xref:tips-for-writers.adoc[guidelines and tips for writers]. **This may take a while, so leave yourself sufficient time for this step.** +* [ ] Set all article and section titles to sentence case. + +== Usage + +* [ ] Eliminate use of __I, we, us,__ and __our__ in the article, rewriting where necessary. Articles should not refer to the author if avoidable. + +== SEO and metadata + +* [ ] Set an appropriate https://yoast.com/focus-keyword/[focus keyword]. +* [ ] Address any article shortcomings that affect readability. (It may not be possible to turn the readability score to "green" in all cases.) +* [ ] Categorize the article. The default "Fedora Project community" category should rarely be used. +* [ ] Add tags for article subject matter. Use as many as possible. As you type a new tag, observe the popup help. Try to choose relevant tags, and avoid creating new ones with trivial differences. +* [ ] Add an Excerpt in the document details in WordPress. This shows up in the https://en.wikipedia.org/wiki/RSS[RSS] feed shown in https://start.fedoraproject.org[start page in Fedora's web browser defaults]. + +== Featured images + +* [ ] Make sure the article has an appropriate xref:creating-an-image.adoc[featured image]. This is **not** the same as an image in the article text itself, and should not appear there. Use the Featured Image box in the document details in WordPress. +* [ ] Featured images should be included or submitted to the https://pagure.io/fedoramagazine-images[featured images repo on Pagure]. Refer to the xref:creating-an-image.adoc[documentation on featured images] for more information. + +== Publishing + +* [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise. diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc index ea9a4fe..e2f8718 100644 --- a/modules/ROOT/pages/editorial.adoc +++ b/modules/ROOT/pages/editorial.adoc @@ -5,6 +5,8 @@ include::partial$workflow-change-banner.adoc[] The duties of an editor are much like any blog owner. Occasionally editors also xref:contributing.adoc[contribute content] when the queue or backlog of content is running a little low. Editors take turns serving as the xref:editor-of-the-week.adoc[Editor of the Week]. +Editors follow an xref:editorial-checklist.adoc[editorial checklist] to help articles meet a quality and content bar, and to ensure they're well searchable. + Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently. Like most blogs and news sites, the Magazine receives feedback and comments from the public. Editors xref:approving-comments.adoc[moderate comments based on common guidelines]. They ensure that discussions stay constructive and discourage trolls and other bad actors. From 01e63d4b3974891ffe14d7c478ada64c90a52525 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 29 2020 21:54:34 +0000 Subject: [PATCH 49/148] Add a blank line for readability --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 62ddb21..5dd8fce 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -27,6 +27,7 @@ output line 2 == Grammar and style tips + . **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. ** Incorrect heading: __Use Sentence Case for Post Titles in Fedora Magazine__ ** Correct heading: __Use sentence case for post titles in Fedora Magazine__ From d588b895faed472b2cbda917665a49798628cd88 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 29 2020 22:03:54 +0000 Subject: [PATCH 50/148] Remove unnecessary itemization --- diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc index 5dd8fce..c9d0934 100644 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ b/modules/ROOT/pages/tips-for-writers.adoc @@ -58,8 +58,7 @@ These tips are about things to do — and avoid — in what you tell users to do . **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. . **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. . **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). -. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: -** __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ +. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ . **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. == Image and screenshot tips From 365006b6f0335781bb0c86d22320b10c568ea844 Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 29 2020 22:11:19 +0000 Subject: [PATCH 51/148] Rename the tips to Writing Guidelines for clarity --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index ef0c834..016687b 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -9,7 +9,7 @@ * xref:writing-a-pitch.adoc[Proposing Articles] * xref:contributing.adoc[Contributing as a Writer] ** xref:getting-access.adoc[Getting Access] -** xref:tips-for-writers.adoc[Tips for Writers] +** xref:writing-guidelines.adoc[Writing Guidelines] * xref:editorial.adoc[Contributing as an Editor] ** xref:editor-of-the-week.adoc[Editor of the Week] ** xref:editorial-checklist.adoc[Editorial Checklist] diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc index d868480..2fc2880 100644 --- a/modules/ROOT/pages/editorial-checklist.adoc +++ b/modules/ROOT/pages/editorial-checklist.adoc @@ -9,7 +9,7 @@ Editors should follow this checklist to help articles meet standards before bein == Style -* [ ] Check the article for adherence to the xref:tips-for-writers.adoc[guidelines and tips for writers]. **This may take a while, so leave yourself sufficient time for this step.** +* [ ] Check the article for adherence to the xref:writing-guidelines.adoc[guidelines for writers]. **This may take a while, so leave yourself sufficient time for this step.** * [ ] Set all article and section titles to sentence case. == Usage diff --git a/modules/ROOT/pages/tips-for-writers.adoc b/modules/ROOT/pages/tips-for-writers.adoc deleted file mode 100644 index c9d0934..0000000 --- a/modules/ROOT/pages/tips-for-writers.adoc +++ /dev/null @@ -1,86 +0,0 @@ -= Tips for article style, grammar, content, and SEO - -include::partial$workflow-change-banner.adoc[] - -These tips will help your article sail through editing. Be kind to your editor(s), and read this before you start. - -== Markup - -Primary rule: don’t get too fancy. Legibility is important. - -. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write `dnf install foo` in the middle of a sentence, write __dnf install foo__. -. **Use italics for system objects you mention in a sentence:** -** GUI or CLI elements like button text or menu entries -** other prompts the reader must find on the screen -** commands or package names -. **Use the Preformatted style in the WordPress editor for command line input or output.** Use a shell prompt ($ or #) only where it genuinely affects the meaning, or to set the input apart from output. It also helps to use boldface for the input itself: -+ -[subs=quotes] ----- -$ **command arg1 arg2** -output line 1 -output line 2 ----- - - -. **Use boldface only for an extremely important phrase or statement.** - - -== Grammar and style tips - -. **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. -** Incorrect heading: __Use Sentence Case for Post Titles in Fedora Magazine__ -** Correct heading: __Use sentence case for post titles in Fedora Magazine__ -. **Check spelling and grammar.** Nobody likes nitpicky comments about this. Check your work before you send it to an editor. Editors: double-check all the work, that’s your job! -. **Write clearly and use shorter sentences.** Brevity is good. Clarity is better. Don’t be excessively wordy when avoidable. If a longer sentence is easier to read, use the extra words. -. **Avoid passive voice.** Passive voice is the use of the object of a sentence as the subject. For example: -** __Active voice__: The troops defeated the enemy. -** __Passive voice__: The enemy was defeated by the troops. -. **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: -** __Weak, passive voice__: Setting the foobar configuration option will make the application listen on all interfaces. -** __Strong, active voice__: Set the foobar configuration option to make the application listen on all interfaces. -. **Avoid unnecessary future tense.** Unless you're actually talking about future plans or publications, present tense is best. -** __Unnecessary future tense__: When you select **Run**, your program will start. -** __Present tense__: When you select **Run**, your program starts. -. **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. -** __Weak__: Zambone is an app used for managing your private documents on a server. -** __Strong__: Zambone manages your private documents on a server. Or: Use Zambone to manage your private documents on a server. -** __Weak__: When setting up a file server, it is important to plan the directory structure carefully. -** __Strong__: Plan the directory structure of the file server carefully before you set it up. -. **Use standard US English for spelling and other international differences.** US English is the lingua franca for the Fedora Project overall. -. **Have a smooth flow from general information to specific instructions.** If you’re not sure how to structure your article like this, check out our starter template. - -== Content tips - -These tips are about things to do — and avoid — in what you tell users to do. Remember that thousands of readers trust Fedora Magazine to tell them how to carry out tasks. Be responsible and helpful, advocate best practices, and respect the user’s security and choice. - -. **Leave packaged files alone.** Processes should not involve editing files under system folders like __/usr__ or __/lib*__. Edit __/etc__ or a user-specific configuration in the home directory. -. **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. -. **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. -. **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). -. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ -. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. - -== Image and screenshot tips - -. **Use a fresh, standard Fedora Workstation**, not your personal desktop or setup. -(It's best to make a VM with a fresh Fedora Workstation install, and do the steps there.) -If you're showing something that *relies* on another desktop, do a fresh installation and use that. -. **Set screen resolution at a reasonable but not too high resolution**, such as 1280x960 or 1280x800. -. If you're only showing a browser window, make it fairly large on the screen and **screenshot only the browser**. (Hint: you can use the Screenshot app for this!) -. If you're only showing an application, **use the default size of the app to screenshot it**. -. **Upload and use that original media in your article.** -If the shot is large, like a large browser window, app, or whole screen, choose a medium size thumbnail and let WordPress handle the conversion. - -== WordPress tips - -. **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. -. **Provide a featured image.** Look at https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[the information here] for tips on featured images. You can also feel free to ask the editors to assign this for you. If you make your own image, try to match the style of other images. Use the assets provided https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[in the featured image guide]. Don’t add your own fonts or deviate from the guide. -. **Use good SEO practices.** Use the SEO plugin provided to maximize the search ranking of the article. Aim for a “green” rating in the __Publish__ box at top right of your article’s edit screen. Follow these guidelines: -** Enter a meaningful keyword in the SEO box under your article. (Most articles shouldn’t use __Fedora__.) -** If the Snippet doesn’t give an effective introduction or summary in the sample search result, rewrite it. -** Don’t feel like you have to eliminate every warning. A “green” rating overall is the only goal. - -== Other hints - -Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 46a305f..0ef289c 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -20,11 +20,11 @@ __Writing an article requires write access to our https://teams.fedoraproject.or === 2. Write it -**Write** your article either https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there) or anywhere you prefer. Wordpress, however, will be the easiest for the editors to review and publish later. Read the xref:tips-for-writers.adoc[Tips for Writers] page for specific guidance about our preferred writing style. +**Write** your article either https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there) or anywhere you prefer. Wordpress, however, will be the easiest for the editors to review and publish later. Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. -As you write your draft, try to understand and follow the xref:tips-for-writers.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner. +As you write your draft, try to understand and follow the xref:writing-guidelines.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner. === 3. Mark it as done diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc new file mode 100644 index 0000000..c9d0934 --- /dev/null +++ b/modules/ROOT/pages/writing-guidelines.adoc @@ -0,0 +1,86 @@ += Tips for article style, grammar, content, and SEO + +include::partial$workflow-change-banner.adoc[] + +These tips will help your article sail through editing. Be kind to your editor(s), and read this before you start. + +== Markup + +Primary rule: don’t get too fancy. Legibility is important. + +. **Don’t mix monospace fonts with proportional fonts in a sentence.** Use italics for the special text. For instance, don’t write `dnf install foo` in the middle of a sentence, write __dnf install foo__. +. **Use italics for system objects you mention in a sentence:** +** GUI or CLI elements like button text or menu entries +** other prompts the reader must find on the screen +** commands or package names +. **Use the Preformatted style in the WordPress editor for command line input or output.** Use a shell prompt ($ or #) only where it genuinely affects the meaning, or to set the input apart from output. It also helps to use boldface for the input itself: ++ +[subs=quotes] +---- +$ **command arg1 arg2** +output line 1 +output line 2 +---- + + +. **Use boldface only for an extremely important phrase or statement.** + + +== Grammar and style tips + +. **Use sentence case for the post title and heading titles.** Don’t capitalize words in your article title or any heading, other than proper nouns. This avoids needless arguments about title case, which differs by region. +** Incorrect heading: __Use Sentence Case for Post Titles in Fedora Magazine__ +** Correct heading: __Use sentence case for post titles in Fedora Magazine__ +. **Check spelling and grammar.** Nobody likes nitpicky comments about this. Check your work before you send it to an editor. Editors: double-check all the work, that’s your job! +. **Write clearly and use shorter sentences.** Brevity is good. Clarity is better. Don’t be excessively wordy when avoidable. If a longer sentence is easier to read, use the extra words. +. **Avoid passive voice.** Passive voice is the use of the object of a sentence as the subject. For example: +** __Active voice__: The troops defeated the enemy. +** __Passive voice__: The enemy was defeated by the troops. +. **Be careful of gerunds (-ing words).** They usually indicate passive voice. Rewrite your sentence to make it stronger. For example: +** __Weak, passive voice__: Setting the foobar configuration option will make the application listen on all interfaces. +** __Strong, active voice__: Set the foobar configuration option to make the application listen on all interfaces. +. **Avoid unnecessary future tense.** Unless you're actually talking about future plans or publications, present tense is best. +** __Unnecessary future tense__: When you select **Run**, your program will start. +** __Present tense__: When you select **Run**, your program starts. +. **Avoid too much use of the verb __to be__ in sentences.** Too much use of is, will be, or can be makes your sentences weak and flabby. Try using the verb form of words you’ve shuffled off elsewhere in the sentence. Often you can simply drop words, or use the imperative (commanding or advising) form of the sentence. +** __Weak__: Zambone is an app used for managing your private documents on a server. +** __Strong__: Zambone manages your private documents on a server. Or: Use Zambone to manage your private documents on a server. +** __Weak__: When setting up a file server, it is important to plan the directory structure carefully. +** __Strong__: Plan the directory structure of the file server carefully before you set it up. +. **Use standard US English for spelling and other international differences.** US English is the lingua franca for the Fedora Project overall. +. **Have a smooth flow from general information to specific instructions.** If you’re not sure how to structure your article like this, check out our starter template. + +== Content tips + +These tips are about things to do — and avoid — in what you tell users to do. Remember that thousands of readers trust Fedora Magazine to tell them how to carry out tasks. Be responsible and helpful, advocate best practices, and respect the user’s security and choice. + +. **Leave packaged files alone.** Processes should not involve editing files under system folders like __/usr__ or __/lib*__. Edit __/etc__ or a user-specific configuration in the home directory. +. **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. +. **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. +. **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). +. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ +. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. + +== Image and screenshot tips + +. **Use a fresh, standard Fedora Workstation**, not your personal desktop or setup. +(It's best to make a VM with a fresh Fedora Workstation install, and do the steps there.) +If you're showing something that *relies* on another desktop, do a fresh installation and use that. +. **Set screen resolution at a reasonable but not too high resolution**, such as 1280x960 or 1280x800. +. If you're only showing a browser window, make it fairly large on the screen and **screenshot only the browser**. (Hint: you can use the Screenshot app for this!) +. If you're only showing an application, **use the default size of the app to screenshot it**. +. **Upload and use that original media in your article.** +If the shot is large, like a large browser window, app, or whole screen, choose a medium size thumbnail and let WordPress handle the conversion. + +== WordPress tips + +. **Use a simple, relevant title.** Preferably this should be a call to action, like __Build a widget using GTK+__, or a list description, like __5 fun games in Fedora__. The title affects search engines, and leads to more hits and higher page ranking. That helps drive traffic to the Magazine. +. **Provide a featured image.** Look at https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[the information here] for tips on featured images. You can also feel free to ask the editors to assign this for you. If you make your own image, try to match the style of other images. Use the assets provided https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/[in the featured image guide]. Don’t add your own fonts or deviate from the guide. +. **Use good SEO practices.** Use the SEO plugin provided to maximize the search ranking of the article. Aim for a “green” rating in the __Publish__ box at top right of your article’s edit screen. Follow these guidelines: +** Enter a meaningful keyword in the SEO box under your article. (Most articles shouldn’t use __Fedora__.) +** If the Snippet doesn’t give an effective introduction or summary in the sample search result, rewrite it. +** Don’t feel like you have to eliminate every warning. A “green” rating overall is the only goal. + +== Other hints + +Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. From 325b56264b885134a5319ee73b142686478bbcae Mon Sep 17 00:00:00 2001 From: Paul W. Frields Date: Jun 29 2020 22:13:01 +0000 Subject: [PATCH 52/148] Guidelines: avoid exclusionary or problematic language --- diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc index c9d0934..1724d7f 100644 --- a/modules/ROOT/pages/writing-guidelines.adoc +++ b/modules/ROOT/pages/writing-guidelines.adoc @@ -59,6 +59,9 @@ These tips are about things to do — and avoid — in what you tell users to do . **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. . **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). . **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ +. **Avoid exclusionary or problematic language.** These are examples of terminology to avoid wherever possible in articles: +.. **blacklist/whitelist** — Use __allowlist/denylist__ instead, which is more directly descriptive of the purpose. +.. **master/slave** — Use __primary/secondary__, __primary/replica__, __active/passive__, __active/standby__, or another similar construct. . **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat. == Image and screenshot tips From 4dd544f5e40d1ddf8116bfaa47555ecd54a18254 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Jul 10 2020 16:35:25 +0000 Subject: [PATCH 53/148] Add the #topic command to the 7th agenda item --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 9b40a10..0c8d32d 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -128,6 +128,7 @@ When there are two or more +1's in an issue, create a card on the board, post th Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week]. + #topic 7/ Editor of the Week #info XXXX will be Editor of the Week next week === 8/ Open floor From 63b593138fc8c63d2ba56c5b1842195a7e47e827 Mon Sep 17 00:00:00 2001 From: Gregory Bartholomew Date: Jul 26 2020 20:46:34 +0000 Subject: [PATCH 54/148] Guidelines: Use the Edit as HTML option on preformatted blocks --- diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc index 1724d7f..bf34fed 100644 --- a/modules/ROOT/pages/writing-guidelines.adoc +++ b/modules/ROOT/pages/writing-guidelines.adoc @@ -83,6 +83,7 @@ If the shot is large, like a large browser window, app, or whole screen, choose ** Enter a meaningful keyword in the SEO box under your article. (Most articles shouldn’t use __Fedora__.) ** If the Snippet doesn’t give an effective introduction or summary in the sample search result, rewrite it. ** Don’t feel like you have to eliminate every warning. A “green” rating overall is the only goal. +. **Use the Edit as HTML option when pasting into preformatted blocks.** Current versions of WordPress are known to strip leading hash marks (#) and leading whitespace when content is pasted into preformatted blocks. Some non-alphanumeric characters may also get garbled (&, <, >, etc.). Using the __Edit as HTML__ option (listed under the vertical ellipsis) prior to pasting content into the block seems to workaround this problem. Be sure to paste your content between the 
 tags and do not overwrite them. After pasting your content, switch back to visual mode by using the __Edit visually__ option to see a better representation of what the final result will look like to the reader.
 
 == Other hints
 

From d571217b2148e6f40d2f7789620903008ca69c06 Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Jul 29 2020 12:24:42 +0000
Subject: [PATCH 55/148] How to add contributors


---

diff --git a/modules/ROOT/pages/editorial-add-contributors.adoc b/modules/ROOT/pages/editorial-add-contributors.adoc
new file mode 100644
index 0000000..bf4b42d
--- /dev/null
+++ b/modules/ROOT/pages/editorial-add-contributors.adoc
@@ -0,0 +1,19 @@
+= Adding Contributors
+
+A contributor must have a FAS account before starting. Once they do, editors should help them get necessary access to join the team.
+
+The editor needs to be a member of the "admin" group in the Taiga team to complete this step.
+
+== Adding to Taiga
+
+Ask the contributor to login to the https://teams.fedoraproject.org[Taiga instance], using the OpenID option and their FAS account username and password.
+
+Find the user's email address. If you don't have that, you can find it through their contribution in the Magazine; their username there is also their FAS username. In Freenode IRC you can use this command:
+
+`/msg zodbot fasinfo `
+
+Go to the https://teams.fedoraproject.org[Taiga instance] and in the Magazine project, go to __Admin__ > __Members__ in the navigation bar, and use the control to add a __New Member__. Enter the new contributor's FAS email address.
+
+Once added, provide the appropriate role, which is usually __Writer__ for a new contributor.
+
+Now you can assign the new user to Taiga cards as well, and they'll receive notifications as appropriate.
\ No newline at end of file
diff --git a/modules/ROOT/pages/editorial.adoc b/modules/ROOT/pages/editorial.adoc
index e2f8718..691ee68 100644
--- a/modules/ROOT/pages/editorial.adoc
+++ b/modules/ROOT/pages/editorial.adoc
@@ -9,4 +9,6 @@ Editors follow an xref:editorial-checklist.adoc[editorial checklist] to help art
 
 Editors hold a xref:editorial-meetings.adoc[weekly editorial meeting] to discuss and approve content, help guide authors, and figure out ways to improve the Magazine and further its mission. The best way to become an editor is to join the weekly meeting, and demonstrate your ability to contribute consistently.
 
+Editors also xref:editorial-add-contributors.adoc[extend access to new contributors] so they can help with writing, art, and sometimes even editing itself.
+
 Like most blogs and news sites, the Magazine receives feedback and comments from the public. Editors xref:approving-comments.adoc[moderate comments based on common guidelines]. They ensure that discussions stay constructive and discourage trolls and other bad actors.

From bebaf365fa0287e2154eec89d40c3e822727e2e7 Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Aug 19 2020 13:40:13 +0000
Subject: [PATCH 56/148] Add information on updating the theme


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 016687b..35d1bf0 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -17,3 +17,5 @@
 ** xref:approving-comments.adoc[Approving Comments]
 ** xref:creating-an-image.adoc[Creating a Featured Image]
 ** xref:adding-a-writer.adoc[Adding a Writer]
+* xref:technical.adoc[Technical Notes and Processes]
+** xref:technical-theme.adoc[Maintaining the Theme]
\ No newline at end of file
diff --git a/modules/ROOT/pages/technical-theme.adoc b/modules/ROOT/pages/technical-theme.adoc
new file mode 100644
index 0000000..96c21c1
--- /dev/null
+++ b/modules/ROOT/pages/technical-theme.adoc
@@ -0,0 +1,47 @@
+= Maintaining the Magazine Theme
+
+The Magazine theme is maintained in https://pagure.io/fedoramagazine-theme[a Pagure repository]. If you want to submit a change, start by forking and/or cloning this repository. This page does not cover git workflow; consult https://git-scm.com/doc[git documentation] for more information, or ask the Magazine staff for help.
+
+== Testing your changes
+
+The `Vagrantfile` lets you deploy a test system to try out your work before you deploy. Ensure you are in the cloned repository in the same directory as the `Vagrantfile`, and run the command `vagrant up` to create and provision the box. This will take some time.
+
+When done, you can point your local browser at http://localhost:5055 to see the theme in action on a test site. The Vagrant box accesses the contents of the repo directly, so you can edit changes in the repository and quickly see them in action. To iterate on changes, after modifying the theme, run `vagrant ssh -- systemctl reload httpd` so the Vagrant box's web caching is cleared. Then reload on your browser to see the modifications at work.
+
+When finished, run `vagrant halt` to stop the Vagrant box, or `vagrant destroy` to remove it from your system entirely.
+
+== Tagging the theme
+
+Once the theme modifications are complete, you should make a release. This means that anyone can return to this iteration of the theme in case of a problem with a future version.
+
+The last commit in your changes should be updating the `fedoramagazine/styles.css` file to update the `version` in the header:
+
+----
+Theme Name: Fedora Magazine 2018
+Text Domain: fmag2018
+Theme URI: http://pagure.org/fedoramagazine-theme/
+Version: 1.03
+Description: The theme for the Fedora Magazine. This iteration first rolled out in March 2018
+----
+
+_(For theme committers:)_ Apply a tag to this commit to mark it for release, such as `v1.03`, and push the tag to the repo using `git push --tags`.
+
+== Releasing the theme
+
+While in the repo, run these commands to make a zip file in which to deliver the theme. **Remember to use the correct, new version number in place of 1.03 below.**
+
+----
+$ ln -s fedoramagazine fedoramagazine-1.03
+$ zip -r /tmp/fedoramagazine-theme-1.03.zip fedoramagazine-1.03
+$ rm -f fedoramagazine-1.03
+----
+
+The resulting `fedoramagazine-theme-1.03.zip` is a release of the theme.
+
+== Installing the updated theme
+
+This step must be done by someone with "administrator" rights in the Fedora Magazine WordPress site.
+
+Use the built-in functions to add a new theme. Upload the resulting `fedoramagazine-theme-1.03.zip` file and activate it.
+
+If you need to switch themes and get confused about which theme is correct, the theme details will show you the version number.
diff --git a/modules/ROOT/pages/technical.adoc b/modules/ROOT/pages/technical.adoc
new file mode 100644
index 0000000..e079614
--- /dev/null
+++ b/modules/ROOT/pages/technical.adoc
@@ -0,0 +1,5 @@
+= Technical Notes and Processes
+
+The Magazine site itself is simply a https://wordpress.org[WordPress site]. Like any website, it may require maintenance from time to time.
+
+One system that sometimes requires changes or fixes is the https://pagure.io/fedoramagazine-theme[Magazine theme]. There is a process to xref:technical-theme.adoc[modify, test, and deploy theme changes].

From c1989ce5c8b03a258a1551ad5e96fde41a647d5f Mon Sep 17 00:00:00 2001
From: Adam Samalik 
Date: Sep 01 2020 09:37:35 +0000
Subject: [PATCH 57/148] Update modules/ROOT/pages/writing-a-pitch.adoc


---

diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc
index 3e76cbc..45339cf 100644
--- a/modules/ROOT/pages/writing-a-pitch.adoc
+++ b/modules/ROOT/pages/writing-a-pitch.adoc
@@ -4,6 +4,6 @@ include::partial$workflow-change-banner.adoc[]
 
 Fedora Magazine welcomes anyone to submit ideas for articles.
 
-We on purpose separate the process of proposing articles and writing — because those are two different skills. By proposing a topic, you are helping writers to have relevant topics they can write about.
+Just propose your idea in our [Fedora Magazine Discourse forum](https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine/)
 
-**See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for guidance.**
\ No newline at end of file
+See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.
\ No newline at end of file

From 3aa89b43d0f6b2313e67cc01dfe4b908acbef676 Mon Sep 17 00:00:00 2001
From: Adam Samalik 
Date: Sep 01 2020 09:38:19 +0000
Subject: [PATCH 58/148] Remove Discourse banner - it's been here for some time


---

diff --git a/modules/ROOT/partials/workflow-change-banner.adoc b/modules/ROOT/partials/workflow-change-banner.adoc
index c58f501..e69de29 100644
--- a/modules/ROOT/partials/workflow-change-banner.adoc
+++ b/modules/ROOT/partials/workflow-change-banner.adoc
@@ -1 +0,0 @@
-NOTE: Starting 25 June 2020, Magazine-related **discussions have moved** to a new place: the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. New article proposals are also being submitted there.
\ No newline at end of file

From ef8d8a41262fc98cd69dd1838658e164493bd20f Mon Sep 17 00:00:00 2001
From: Miro Hrončok 
Date: Sep 03 2020 06:54:20 +0000
Subject: [PATCH 59/148] Fix AsciiDoc link


---

diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc
index 45339cf..b98350d 100644
--- a/modules/ROOT/pages/writing-a-pitch.adoc
+++ b/modules/ROOT/pages/writing-a-pitch.adoc
@@ -4,6 +4,6 @@ include::partial$workflow-change-banner.adoc[]
 
 Fedora Magazine welcomes anyone to submit ideas for articles.
 
-Just propose your idea in our [Fedora Magazine Discourse forum](https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine/)
+Just propose your idea in our https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine/[Fedora Magazine Discourse forum]
 
 See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.
\ No newline at end of file

From b16ff1dbb08dcbbb7b6fb7bcb08676ff311b4d8e Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Sep 16 2020 20:17:35 +0000
Subject: [PATCH 60/148] Remove step six from the meetings


As agreed in today's meeting, we handle this well asynchronously, so it
usually gets skipped in meetings anyway. Might as well make it official.

---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 0c8d32d..163ee79 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -36,9 +36,8 @@ This is the standard agenda. Announcing it in advance helps newcomers understand
     #info -- 3/ Finished articles to review --
     #info -- 4/ Articles to edit --
     #info -- 5/ Publishing schedule --
-    #info -- 6/ Article proposals to clarify / approve --
-    #info -- 7/ Editor of the Week --
-    #info -- 8/ Open floor --
+    #info -- 6/ Editor of the Week --
+    #info -- 7/ Open floor --
 
 
 === 1/ Last week's stats
@@ -113,25 +112,14 @@ When the schedule is set and agreed upon, announce it by:
     DAY DATE, NAME (NICK:edit/NICK:image) -- 
 
 
-=== 6/ Article proposals to clarify / approve
-
-    #topic 6/ Article proposals to clarify / approve
-    #info Review the the article proposals and decide about what's next — a new article spec? more discussion?
-    #link Article proposals in our forum: https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine
-
-The final step is to review and approve proposals. This is important for our contibutors so they can start writing their articles.
-
-When there are two or more +1's in an issue, create a card on the board, post the link to it back to the proposal, and close it.
-
-
-=== 7/ Editor of the Week
+=== 6/ Editor of the Week
 
 Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week].
 
     #topic 7/ Editor of the Week
     #info XXXX will be Editor of the Week next week
 
-=== 8/ Open floor
+=== 7/ Open floor
 
     #topic 8/ Open floor
 

From fa0e9672a4ebd5c66d0b5d5a995661eb0206b2ff Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Sep 16 2020 20:27:24 +0000
Subject: [PATCH 61/148] Add some examples of third-party name styles


---

diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc
index bf34fed..f02b0b8 100644
--- a/modules/ROOT/pages/writing-guidelines.adoc
+++ b/modules/ROOT/pages/writing-guidelines.adoc
@@ -63,6 +63,15 @@ These tips are about things to do — and avoid — in what you tell users to do
 .. **blacklist/whitelist** — Use __allowlist/denylist__ instead, which is more directly descriptive of the purpose.
 .. **master/slave** — Use __primary/secondary__, __primary/replica__, __active/passive__, __active/standby__, or another similar construct.
 . **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat.
+. **Use the correct style for third parties.** Names of companies, projects, and technologies don't always follow the style rules of typical English words.
+Choose the styling used by authoritiative websites when you're unsure.
+If authoritaive sources use inconsistent style, use your best judgment.
+A non-exhaustive list:
+.. *Copr* instead of _COPR_
+.. *NVIDIA* instead of _Nvidia_ or _nVidia_
+.. *Perl* instead of _PERL_
+.. *Red Hat* instead of _Redhat_ or _RedHat_
+.. *ThinkPad* instead of _Thinkpad_
 
 == Image and screenshot tips
 

From 37873e4a3e7dcf1ee067115dc91854a37327f560 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Sep 16 2020 20:28:51 +0000
Subject: [PATCH 62/148] Update the style of Copr to match our rules


---

diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc
index f02b0b8..1c4352a 100644
--- a/modules/ROOT/pages/writing-guidelines.adoc
+++ b/modules/ROOT/pages/writing-guidelines.adoc
@@ -58,7 +58,7 @@ These tips are about things to do — and avoid — in what you tell users to do
 . **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software.
 . **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them.
 . **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL).
-. **COPR software must be accompanied by a caveat.** The COPR build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from COPR, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__
+. **Copr software must be accompanied by a caveat.** The Copr build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from Copr, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__
 . **Avoid exclusionary or problematic language.** These are examples of terminology to avoid wherever possible in articles:
 .. **blacklist/whitelist** — Use __allowlist/denylist__ instead, which is more directly descriptive of the purpose.
 .. **master/slave** — Use __primary/secondary__, __primary/replica__, __active/passive__, __active/standby__, or another similar construct.

From 26a0a17da5e9f94c09e5768931a88d1300471db9 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Sep 17 2020 20:17:57 +0000
Subject: [PATCH 63/148] Add some Taiga instructions


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 35d1bf0..d12db4b 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -18,4 +18,5 @@
 ** xref:creating-an-image.adoc[Creating a Featured Image]
 ** xref:adding-a-writer.adoc[Adding a Writer]
 * xref:technical.adoc[Technical Notes and Processes]
-** xref:technical-theme.adoc[Maintaining the Theme]
\ No newline at end of file
+** xref:technical-theme.adoc[Maintaining the Theme]
+** xref:technical-taiga.adoc[Taiga Operations]
diff --git a/modules/ROOT/pages/technical-taiga.adoc b/modules/ROOT/pages/technical-taiga.adoc
new file mode 100644
index 0000000..4aded50
--- /dev/null
+++ b/modules/ROOT/pages/technical-taiga.adoc
@@ -0,0 +1,47 @@
+= Taiga Operations
+
+== Adding a new user
+
+If an author has not written for us before, you will have to add them to Taiga.
+
+NOTE: Because we use OpenID authentication, the new member will have to log in to teams.fedoraproject.org with their Fedora account _before_ you can add them.
+
+To add a new user:
+
+. Click *Admin* (the gear icon) on the left-hand panel
+. Click *Members*
+. Click the *+New Member* button in the upper-right corner
+. Search by name or email address in the text box
+. Click the desired account
+. Select the *Writer* role from the *Choose a role* drop-down
+. Click the *Invite* button
+
+The user is now added to the Magazine board and can be assigned to cards.
+
+== Creating a new card (user story)
+
+When a proposal is approved, follow these steps.
+
+. From the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban page], click the *+* button in the *Article Spec* column
+. Enter the title of the article in the top text box
+. Enter details of the proposal in the bottom text box, including a link to the proposal discussion where appropriate
+. Click *Add tag* and type "needs image" and click that tag
+. If an author has been identified and has an account in Taiga, click *Assign* and assign them
+. Click *Create*
+. Click the card you just created
+. Click the *Add watchers* button
+. Type "Editor" in the search box
+. Click *Role: Editorial board member* to add all editors as watchers
+. Click the *Add* button
+
+== Adding or removing editors
+
+To add or remove an editor, in Taiga:
+
+. Click *Admin* (the gear icon) on the left-hand panel
+. Click *Members*
+. Find the member in question
+. Select the desired role in the *Role* drop-down
+. Toggle the *Admin* slider (Editors should be admins on the board, non-editors should not)
+
+NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well so that the docs and images repos have the correct permissions.

From 48bd4c20bcc74db1fe9ecd1e7c257fed7e8a89a9 Mon Sep 17 00:00:00 2001
From: Adam Samalik 
Date: Sep 23 2020 12:46:56 +0000
Subject: [PATCH 64/148] Update modules/ROOT/pages/editorial-meetings.adoc


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 163ee79..5bdb7eb 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -117,6 +117,9 @@ When the schedule is set and agreed upon, announce it by:
 Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week].
 
     #topic 7/ Editor of the Week
+
+Announce the volunteer using:
+
     #info XXXX will be Editor of the Week next week
 
 === 7/ Open floor

From 2eb44669599cf5cc9f67af61d53b940aa6c3018a Mon Sep 17 00:00:00 2001
From: Adam Samalik 
Date: Sep 23 2020 12:48:40 +0000
Subject: [PATCH 65/148] Update modules/ROOT/pages/editorial-meetings.adoc


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 5bdb7eb..0b7ff73 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -116,7 +116,7 @@ When the schedule is set and agreed upon, announce it by:
 
 Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week].
 
-    #topic 7/ Editor of the Week
+    #topic 6/ Editor of the Week
 
 Announce the volunteer using:
 
@@ -124,7 +124,7 @@ Announce the volunteer using:
 
 === 7/ Open floor
 
-    #topic 8/ Open floor
+    #topic 7/ Open floor
 
 
 === Meeting ends

From 8a7533da10ff91421e5bf92def88b8a2cbcd4380 Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Sep 24 2020 20:30:17 +0000
Subject: [PATCH 66/148] Add some logo and picture guidelines


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 3d2a527..b6d6c47 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -6,7 +6,11 @@ Each article in the Fedora Magazine must have a featured image. The image gives 
 
 These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. 
 
+== Important guidelines
 
+* Only use the Fedora logo occasionally, such as for important announcements, or to indicate a project affinity.
+* Do not use logos from other projects. Most require permission for use, and it is difficult to assign a recipient for permission in a group-owned project like the Magazine.
+* Only use acceptably licensed pictures, photos, or screenshots, or ones that you have made yourself and thus can contribute with such a license. __(More on this below.)__
 
 == Getting the image repository
 

From ad2b63bf4a246fbde5e251e1f2e81723b5bd8034 Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Sep 30 2020 12:30:15 +0000
Subject: [PATCH 67/148] Add a note on making editors Watchers of new cards


---

diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index 7d1f463..be1b8ba 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -18,6 +18,8 @@ If an editor is happy with the proposal, all they need to do is to reply "+1". P
 
 When a proposal is approved, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column.
 
+When the card is created, add the __Role: Editorial board member__ group to the Watchers. This ensures editors are emailed when the card status changes, so someone can react.
+
 This card now represents a specific article and goes through all the other steps of the workflow.
 
 == Workflow

From 7f7a36d7341ead824e4079348fe7964c57db2fa3 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Oct 02 2020 20:25:07 +0000
Subject: [PATCH 68/148] Add some instructions on managing WordPress


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index d12db4b..f9ea8d6 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -20,3 +20,4 @@
 * xref:technical.adoc[Technical Notes and Processes]
 ** xref:technical-theme.adoc[Maintaining the Theme]
 ** xref:technical-taiga.adoc[Taiga Operations]
+** xref:technical-wordpress.adoc[WordPress Operations]
diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
new file mode 100644
index 0000000..2620c85
--- /dev/null
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -0,0 +1,26 @@
+= WordPress Operations
+
+== Adding a new user
+
+Do *not* add new users manually.
+User accounts are created on login with Fedora Account System credentials.
+
+== User permissions
+
+We use the _User Role Editor_ plugin to manage user permissions at a fine-grained level.
+There are five roles in our WordPress instance:
+
+* **Administrator**
+This role has the ability to make settings changes and conduct other administrative tasks.
+* **Author**
+This role has the ability to create and edit (unpublished) posts, moderate comments, and upload files.
+Authors may be granted this role, and should be if they are repeat contributors.
+* **Contributor**
+This is the default role.
+This role has the ability to create and edit (unpublished) posts.
+* **Editor**
+This role has many abilites, including the ability ot edit published posts and posts by other authors.
+Magazine editors should have this role.
+* **Subscriber**
+This role only allows for reading posts.
+We probably don't need to add anyone to this role in general.

From fdf51f4b2d1b4141e1afc45352f85d1dae319522 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Oct 02 2020 20:34:33 +0000
Subject: [PATCH 69/148] Add instructions for promoting users to Author


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index 829460b..e0f88b9 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -6,4 +6,5 @@ When a new writer joins the Magazine, they usually want to track their work in o
 
 . Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already.
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
-. In the kanban instance, select _Admin_ on the left navigation bar, and then select _Members_. Select _New Member_ and add the contributor as a _Writer_ via their FAS email address (this is not their _@fedoraproject.org_ alias). This puts them on the team.
+. Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions
+. Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress
diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
index 2620c85..ab6bc58 100644
--- a/modules/ROOT/pages/technical-wordpress.adoc
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -24,3 +24,13 @@ Magazine editors should have this role.
 * **Subscriber**
 This role only allows for reading posts.
 We probably don't need to add anyone to this role in general.
+
+=== Changing a user's role
+
+In the https://fedoramagazine.org/wp-admin/[WordPress dashboard]:
+
+. Select *Users* on the left-hand menu
+. Search or browse for the desired user
+. Hover over the desired user's row and click "Edit"
+. Change the *Role* dropdown to the desired role
+. Click the *Update User* button

From 72c5593c0d1699cbf4cdff04914379a7376d50fa Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Oct 21 2020 12:07:40 +0000
Subject: [PATCH 70/148] Add note on reusing images and installing fonts


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index b6d6c47..97abfde 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -38,6 +38,16 @@ Save this as a new file with a different name.
 
 You can use the assets inside this file to start with the right-sized document, with some pre-configured backgrounds. Feel free to look at other SVGs for guidance. If you don’t have experience with these images, try to stick with fonts and motifs that you see in recent banners. But also feel free to experiment! For instance, use photographs (freely licensed, such as CC-BY or CC-BY-SA) with a text overlay for a nice look. https://unsplash.com/[Unsplash.com] has a large library of images in the public domain you can use to get started.
 
+== Reusing an old image
+
+It makes sense to reuse an old image if there is a thematic link from the previous article to the new one. Try to vary something about the image, such as the text. If the background is abstract (not a photo), consider rebalancing the color.
+
+When you reuse an old image, be careful that you have all the correct fonts installed. To see a list, you can run this command:
+
+    grep font  | sed 's/^.*font-family:\([^;]*\).*$/\1/'
+
+You can ignore font names "serif" and "sans-serif." Be sure to install any fonts that you don't have on your system already, so the image is rendered correctly both on your screen and when you build a JPG later.
+
 === Background images
 
 You can find compatibly licensed images at https://unsplash.com[Unsplash], or you can try other image search engines. Be sure to choose only images with CC0, CC-BY, or CC-BY-SA licenses. (Commercial and derivative uses must be permissible.)

From 5dcd4d485854d4e3fd70be8d990a5a9d408e3f3f Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Nov 05 2020 22:05:57 +0000
Subject: [PATCH 71/148] Add instructions for adding a post to a series


We don't use this functionality very much, but that's all the more
reason to have it well-documented

---

diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
index ab6bc58..313c80d 100644
--- a/modules/ROOT/pages/technical-wordpress.adoc
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -34,3 +34,19 @@ In the https://fedoramagazine.org/wp-admin/[WordPress dashboard]:
 . Hover over the desired user's row and click "Edit"
 . Change the *Role* dropdown to the desired role
 . Click the *Update User* button
+
+== Adding an article to a series
+
+Fedora Magazine uses "series" in WordPress to display related articles in a sidebar.
+This is often used for Copr articles.
+However, adding an article to a series is not straightforward.
+In the https://fedoramagazine.org/wp-admin/[WordPress dashboard]:
+
+. Select *Posts* on the left-hand menu
+. Search or browse for the desired posts
+. Click *Quick Edit*
+. In the *Post Series* box, type the name of the desired series
+. Click *Update*
+
+If you do not know what the name of the series is, you can look in the https://fedoramagazine.org/wp-admin/edit-tags.php?taxonomy=post_series[Post Series] screen.
+This is located under the *Posts* section of the left-hand menu.

From 84cc04d62e8cc8f25cbc2537e7629665be43537b Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Nov 05 2020 22:10:08 +0000
Subject: [PATCH 72/148] Add a check of upcoming test days to the meeting


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 0b7ff73..96832ce 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -59,6 +59,12 @@ Review anything that's in progress. If an article is stuck in progress for a lon
 
 Anything that's already finished can be moved to the Finished column.
 
+You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission.
+These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish.
+
+    #info Are there any upcoming test days?
+    #link https://apps.fedoraproject.org/calendar/QA/
+
 
 === 3/ Finished articles to review
 

From edc4e4483f4f6cb4d84c99e2bdca67a936b69af9 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Nov 11 2020 13:56:46 +0000
Subject: [PATCH 73/148] note when/why to upload an image to the git repo


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 97abfde..7a75451 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -86,4 +86,6 @@ Now use the helpful make target we’ve provided. This creates the correct sized
 
     $ make using-inkscape.jpg
 
-Now you can post this file, using-inkscape.jpg, online, and then provide that URL to the mailing list for review. Remember, don’t attach your JPG to a mailing list post. URLs are the correct way to have your file reviewed.
\ No newline at end of file
+Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Taiga card for review.
+
+If the image is approved, and if it might be reused for later articles, then consider creating a pull request against the upstream repository to have your work archived for reuse.

From 40e338a9c12d2222d26f2ceb72311d70f4082706 Mon Sep 17 00:00:00 2001
From: Till Maas 
Date: Nov 12 2020 08:13:31 +0000
Subject: [PATCH 74/148] Use recommended Copr notation


The content tips recommend to use Coprr instead of COPR. Use this notation in the guidelines, too, for consistency.
---

diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc
index 1c4352a..84a4aee 100644
--- a/modules/ROOT/pages/writing-guidelines.adoc
+++ b/modules/ROOT/pages/writing-guidelines.adoc
@@ -58,7 +58,7 @@ These tips are about things to do — and avoid — in what you tell users to do
 . **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software.
 . **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them.
 . **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL).
-. **Copr software must be accompanied by a caveat.** The Copr build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from Copr, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__
+. **Copr software must be accompanied by a caveat.** The Copr build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from Copr, ensure there’s no official build. If not, include a statement like this: __Copr is not officially supported by Fedora infrastructure. Use packages at your own risk.__
 . **Avoid exclusionary or problematic language.** These are examples of terminology to avoid wherever possible in articles:
 .. **blacklist/whitelist** — Use __allowlist/denylist__ instead, which is more directly descriptive of the purpose.
 .. **master/slave** — Use __primary/secondary__, __primary/replica__, __active/passive__, __active/standby__, or another similar construct.

From 0c5b993abd68203de032c61a0c48e7ab6fb489e1 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Nov 18 2020 15:06:33 +0000
Subject: [PATCH 75/148] Add the image demo video


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 97abfde..7c6b4ba 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -6,6 +6,8 @@ Each article in the Fedora Magazine must have a featured image. The image gives 
 
 These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. 
 
+Watch the https://youtu.be/F6Nf1gsR9S4[Creating Featured Images Workshop video] on our YouTube channel for a visual demo of the guidelines and instructions below, plus some additional Inkscape tips.
+
 == Important guidelines
 
 * Only use the Fedora logo occasionally, such as for important announcements, or to indicate a project affinity.
@@ -86,4 +88,4 @@ Now use the helpful make target we’ve provided. This creates the correct sized
 
     $ make using-inkscape.jpg
 
-Now you can post this file, using-inkscape.jpg, online, and then provide that URL to the mailing list for review. Remember, don’t attach your JPG to a mailing list post. URLs are the correct way to have your file reviewed.
\ No newline at end of file
+Now you can post this file, using-inkscape.jpg, online, and then provide that URL to the mailing list for review. Remember, don’t attach your JPG to a mailing list post. URLs are the correct way to have your file reviewed.

From 9e7f04ef35a773182908b7da06a5f34fd042f51f Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Jan 08 2021 18:42:06 +0000
Subject: [PATCH 76/148] Update the slug for the Discussion category


---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index 6274312..6dc9d77 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -9,5 +9,5 @@ include::partial$workflow-change-banner.adoc[]
 
 **3. Sign in to the Taiga board**: Again, using your FAS Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board].
 
-**3. Join the Magazine forum and introduce yourself**: And finally, join the discussion in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
+**3. Join the Magazine forum and introduce yourself**: And finally, join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
 
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index 2c416ea..b38f10a 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -22,7 +22,7 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin
 We also have regular xref:editorial-meetings.adoc[editorial board meetings].
 
 * IRC Channel: https://webchat.freenode.net/?channels=#fedora-magazine[#fedora-magazine]
-* Forum: https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]
+* Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]
 
 
 
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index 3203286..0e2dd51 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -10,7 +10,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 == Submitting an idea
 
-Join the community in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
+Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
 TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] — click on the "OpenID Connect" button on the login form to log in with your Fedora Account. That is required before you can be added to the board as a writer.
 
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index be1b8ba..531c065 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -10,7 +10,7 @@ Proposals might be discussed with the person who proposed them, with subject mat
 
 == Discussing and approving proposals
 
-Proposals are submitted to the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum] as topics, and discussion happens right there.
+Proposals are submitted to the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] as topics, and discussion happens right there.
 
 Opinions and additional relevant information is welcome from anyone.
 
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index 023f034..baaeed8 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -17,6 +17,6 @@ An initial proposal lands in the __idea__ state. After some clarification, a spe
 
 == Tracking
 
-Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
+Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
 
-Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
\ No newline at end of file
+Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc
index b98350d..d16ddc2 100644
--- a/modules/ROOT/pages/writing-a-pitch.adoc
+++ b/modules/ROOT/pages/writing-a-pitch.adoc
@@ -4,6 +4,6 @@ include::partial$workflow-change-banner.adoc[]
 
 Fedora Magazine welcomes anyone to submit ideas for articles.
 
-Just propose your idea in our https://discussion.fedoraproject.org/c/project/Discussion-related-to-Fedora-Magazine/[Fedora Magazine Discourse forum]
+Just propose your idea in our https://discussion.fedoraproject.org/c/project/magazine/[Fedora Magazine Discourse forum]
 
-See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.
\ No newline at end of file
+See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.

From 25126773b6f80630156f2b2a6d09ffb33903fbe0 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Jan 09 2021 17:54:11 +0000
Subject: [PATCH 77/148] Add details about dimensions and margins


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 7c6b4ba..1dc19e3 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -54,8 +54,12 @@ You can ignore font names "serif" and "sans-serif." Be sure to install any fonts
 
 You can find compatibly licensed images at https://unsplash.com[Unsplash], or you can try other image search engines. Be sure to choose only images with CC0, CC-BY, or CC-BY-SA licenses. (Commercial and derivative uses must be permissible.)
 
+=== Dimensions
+
 Before you import your background to the SVG, scale and trim it using GIMP or another image editor to an 1890x800 size, and a JPG quality of about 75-80%. This keeps the SVG from being too large -- it will reduce the size from many MB to just a few hundred KB.
 
+The SVG template contains guidelines to indicate what portion of the cover image's edge might get clipped when the article is shared on various social media sites. The portion that might get clipped is about 10% of the left and right sides of the image and about 13% of the top and bottom. In the SVG template, the guidelines provide margins of exactly 183 pixels on the left and right and 107 pixels on the top and bottom for an image that is sized to 1890x800 pixels. This leaves an interior region of 1524x586 pixels within which it is safe to place text without concern that it will get clipped when the article is shared out to other social media sites.
+
 === Fonts
 
 There are a few fonts that are commonly used in featured images. You are encouraged to use these fonts in your images to help featured images fit into the general “theme” that other images follow. They are all freely available at the links provided. The fonts we commonly use on the Fedora Magazine are listed below.

From 97c87a2c2e26a1bc79909deafe15a3bb84f795e3 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Jan 09 2021 18:16:11 +0000
Subject: [PATCH 78/148] note when/why to upload an image to the git repo


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 1dc19e3..974537b 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -92,4 +92,6 @@ Now use the helpful make target we’ve provided. This creates the correct sized
 
     $ make using-inkscape.jpg
 
-Now you can post this file, using-inkscape.jpg, online, and then provide that URL to the mailing list for review. Remember, don’t attach your JPG to a mailing list post. URLs are the correct way to have your file reviewed.
+Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Taiga card for review.
+
+If the image is approved, and if it might be reused for later articles, then consider creating a pull request against the upstream repository to have your work archived for reuse.

From bbf1fd2629a040fc5a5e7b4f97ee217675340b98 Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Jan 14 2021 13:12:20 +0000
Subject: [PATCH 80/148] Add note on real names


---

diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
index 313c80d..a34072c 100644
--- a/modules/ROOT/pages/technical-wordpress.adoc
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -5,6 +5,14 @@
 Do *not* add new users manually.
 User accounts are created on login with Fedora Account System credentials.
 
+== User details
+
+We use real names on the Magazine for authors.
+This reflects accountability for posts on a more official Fedora outlet.
+
+Locate the user in the _Users_ control panel, and select _Edit_.
+Switch the default display of the user name to first and last name.
+
 == User permissions
 
 We use the _User Role Editor_ plugin to manage user permissions at a fine-grained level.

From d9c15b1d7c2ad1971947f636934679f9cbd1431d Mon Sep 17 00:00:00 2001
From: Paul W. Frields 
Date: Jan 14 2021 13:19:20 +0000
Subject: [PATCH 81/148] Add note to editorial checklist for author names


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index 2fc2880..cc87d44 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -4,6 +4,7 @@ Editors should follow this checklist to help articles meet standards before bein
 
 == Formatting
 
+* [ ] Ensure the author's first and last name appears in the preview. If not, follow the instructions xref:technical-wordpress.adoc[here].
 * [ ] After the introductory paragraph, include the __--- Read More ---__ element. This causes RSS readers to visit the site to view the article.
 * [ ] Remove any monospace text mixed into paragraphs, such as  elements. Either convert these to italics, or move them into Preformatted blocks in WordPress, fixing surrounding text as necessary.
 

From 3d2667ecaf3ed19fd516db9c1e8e6a8ae68b1619 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Jan 25 2021 14:03:14 +0000
Subject: [PATCH 82/148] Give image creation its own section


This makes it easier to find. Since image creation is not necessarily an
editorial role (it just has ended up that way historically), making the
docs easier to find will help others who want to contribute images but
not take on other editorial responsibilities.

---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index f9ea8d6..359432f 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -10,12 +10,12 @@
 * xref:contributing.adoc[Contributing as a Writer]
 ** xref:getting-access.adoc[Getting Access]
 ** xref:writing-guidelines.adoc[Writing Guidelines]
+* xref:creating-an-image.adoc[Creating a Featured Image]
 * xref:editorial.adoc[Contributing as an Editor]
 ** xref:editor-of-the-week.adoc[Editor of the Week]
 ** xref:editorial-checklist.adoc[Editorial Checklist]
 ** xref:editorial-meetings.adoc[Editorial Meetings]
 ** xref:approving-comments.adoc[Approving Comments]
-** xref:creating-an-image.adoc[Creating a Featured Image]
 ** xref:adding-a-writer.adoc[Adding a Writer]
 * xref:technical.adoc[Technical Notes and Processes]
 ** xref:technical-theme.adoc[Maintaining the Theme]

From 2e83cc462120178add3311f4c662492f0d99a336 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Jan 25 2021 14:17:53 +0000
Subject: [PATCH 83/148] Use the "git for docs writers" instructions


This page reduces the duplication in this doc and is (if I may humbly
say so), more instructive for novice git users.

---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 974537b..bb20367 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -24,13 +24,7 @@ Install the git and inkscape packages if you don’t have them installed already
     $ sudo dnf install git inkscape
 
 
-If desired, change directory into the folder where you like to store your project work. This example uses the folder name projects, but you should use a folder you have on your system. This step is optional:
-
-    cd projects
-
-Now clone the git repository of Fedora Magazine images:
-
-    $ git clone https://pagure.io/fedoramagazine-images.git
+Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the repository.
 
 == Creating a new image using the template
 

From 02002d7e8307b397054c3d859dbf7eb28eb0636d Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Mar 23 2021 19:53:18 +0000
Subject: [PATCH 84/148] Add notes for handling release announcements


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index cc87d44..f73418d 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -2,6 +2,13 @@
 
 Editors should follow this checklist to help articles meet standards before being published.
 
+== Special notes for release announcements
+
+* [ ] Set the article slug to match the pattern `announcing-fedora-` for final releases and `announcing-fedora--beta` for beta releases.
+This pattern is expected for things like the CommonBugs templates in the wiki.
+* [ ] Do *not* schedule the post.
+Release announcements should be published manually after confirming the website is up to date, etc.
+
 == Formatting
 
 * [ ] Ensure the author's first and last name appears in the preview. If not, follow the instructions xref:technical-wordpress.adoc[here].

From 14e98a5beb9f8ce101c62b4f36a01e6d8912fb6b Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Mar 23 2021 19:54:59 +0000
Subject: [PATCH 85/148] Add information about setting the slug


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index f73418d..d845273 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -31,6 +31,10 @@ Release announcements should be published manually after confirming the website 
 * [ ] Categorize the article. The default "Fedora Project community" category should rarely be used.
 * [ ] Add tags for article subject matter. Use as many as possible. As you type a new tag, observe the popup help. Try to choose relevant tags, and avoid creating new ones with trivial differences.
 * [ ] Add an Excerpt in the document details in WordPress. This shows up in the https://en.wikipedia.org/wiki/RSS[RSS] feed shown in https://start.fedoraproject.org[start page in Fedora's web browser defaults].
+* [ ] Set the article slug.
+This should exclude common short words like "of", "and", and "the".
+The slug should give a sense of what the article is about but be succicnt.
+Putting the focus keyword at the beginning of the slug will make the SEO plugin happy.
 
 == Featured images
 

From 63a1164730f51786c3ffb535ed220a5c3a213890 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Apr 12 2021 17:09:56 +0000
Subject: [PATCH 86/148] Update the link for getting a new Fedora Account


---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index 6dc9d77..7b9a5bd 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -3,11 +3,11 @@
 include::partial$workflow-change-banner.adoc[]
 
 
-**1. Get a Fedora FAS Account**: If you don’t already have one, sign up for a https://admin.fedoraproject.org/accounts/user/new[Fedora Account System (FAS) account here].
+**1. Get a Fedora Account**: If you don’t already have one, https://accounts.fedoraproject.org/#register[sign up here]. Note that contributors are required to sign the Fedora Project Contributor Agreement (FPCA) to protect both the Contributor and the Fedora Project. It makes certain that Fedora can remain forever free & open source.
 
-**2. Sign in to the Fedora Magazine**: Now, using your FAS Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here].
+**2. Sign in to the Fedora Magazine**: Now, using your Fedora Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here].
 
-**3. Sign in to the Taiga board**: Again, using your FAS Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board].
+**3. Sign in to the Taiga board**: Again, using your Fedora Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board].
 
 **3. Join the Magazine forum and introduce yourself**: And finally, join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
 

From 269c003adb74b208022bf0e0e6b2f240158ed6b6 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Apr 12 2021 17:50:22 +0000
Subject: [PATCH 87/148] Revamp the wording, links and style on the Getting Access page


---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index 7b9a5bd..c9b75d8 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -3,11 +3,19 @@
 include::partial$workflow-change-banner.adoc[]
 
 
-**1. Get a Fedora Account**: If you don’t already have one, https://accounts.fedoraproject.org/#register[sign up here]. Note that contributors are required to sign the Fedora Project Contributor Agreement (FPCA) to protect both the Contributor and the Fedora Project. It makes certain that Fedora can remain forever free & open source.
+**1. Get a Fedora Account**:
+If you don’t already have one, https://accounts.fedoraproject.org/#register[sign up here].
+Note that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 
-**2. Sign in to the Fedora Magazine**: Now, using your Fedora Account, https://fedoramagazine.org/wp-admin/[sign in to the Fedora Magazine here].
+**2. Sign in to the Fedora Magazine**:
+https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress dashboard] using your Fedora Account.
 
-**3. Sign in to the Taiga board**: Again, using your Fedora Account, https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[sign in to the Taiga Board].
+**3. Sign in to the Taiga board**:
+https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account.
 
-**3. Join the Magazine forum and introduce yourself**: And finally, join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
+**3. Join the Magazine forum and introduce yourself**:
+Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].
+This is where we discuss everything to do with the Fedora Magazine.
+Introduce yourself and tell us that you wish to contribute to the Fedora Magazine.
+A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
 

From 4ff7c89d85907a61f0b997b5318ee8e249d6fd18 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Apr 12 2021 17:56:40 +0000
Subject: [PATCH 88/148] Change "Taiga" to "Kanban"


---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index c9b75d8..cf8e6db 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -10,7 +10,7 @@ Note that contributors are required to sign the Fedora Project Contributor Agree
 **2. Sign in to the Fedora Magazine**:
 https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress dashboard] using your Fedora Account.
 
-**3. Sign in to the Taiga board**:
+**3. Sign in to the Kanban board**:
 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account.
 
 **3. Join the Magazine forum and introduce yourself**:

From 3015ebc50825ca0319e5612440411483e4662852 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Apr 12 2021 18:20:22 +0000
Subject: [PATCH 89/148] Fix the numbering on the Getting Access page


---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index cf8e6db..fa21e78 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -13,7 +13,7 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da
 **3. Sign in to the Kanban board**:
 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account.
 
-**3. Join the Magazine forum and introduce yourself**:
+**4. Join the Magazine forum and introduce yourself**:
 Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].
 This is where we discuss everything to do with the Fedora Magazine.
 Introduce yourself and tell us that you wish to contribute to the Fedora Magazine.

From 06a153fc6f9ca332b0fd3bb5094718d18e252610 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Apr 12 2021 18:37:37 +0000
Subject: [PATCH 90/148] Update the editorial board members


Stickster has stepped back and rlengland has stepped up.

---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 96832ce..821ef00 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -21,7 +21,7 @@ To start the meeting, run the following set of commands.
     #startmeeting Magazine editorial board
     #meetingname magazine
     #topic Roll call
-    #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr bcotton
+    #chair ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr bcotton rlengland
 
 People will then join using a `.hello2` or a `.hello NICK` command.
 

From ac2754395029d4180fcd1606cd7011194a74195f Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Apr 14 2021 20:49:48 +0000
Subject: [PATCH 91/148] Add a note to update the meeting link if the schedule changes


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 821ef00..5e3cfea 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -8,6 +8,7 @@ The goal of this meeting is to set and execute a publishing schedule of appropri
 
 Meetings happen every week in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
 Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week].
+If the meeting time changes, be sure to update the link in this paragraph.
 
 == Chairing the meeting
 

From d5fefebb9b305ef2c788e342d495027ca5222b99 Mon Sep 17 00:00:00 2001
From: Sun Wukong 
Date: Apr 22 2021 07:58:51 +0000
Subject: [PATCH 92/148] Update modules/ROOT/pages/getting-access.adoc


Added an aside for step 3 to explain why it's required to precede step 4, even if it seemlingly doesn't do anything by itself.
Also make it more apparent, that step 4 is not as optional as it may look like given how login seems to just work in step 3.
---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index fa21e78..da19b6d 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -12,6 +12,7 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da
 
 **3. Sign in to the Kanban board**:
 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account.
+This does NOT grant write access. It is, so the account is known to the system and can be manually granted privileges by an administrator after step 4.
 
 **4. Join the Magazine forum and introduce yourself**:
 Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].

From b5234b96546f8e10be2c077cf16d801d6f7565e6 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: Apr 29 2021 16:45:47 +0000
Subject: [PATCH 93/148] Add a reminder to check the release schedule


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 5e3cfea..9167fbb 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -66,6 +66,13 @@ These tend to come in with very short notice, so the Editor of the Week should u
     #info Are there any upcoming test days?
     #link https://apps.fedoraproject.org/calendar/QA/
 
+Also check the release schedule for upcoming tasks.
+This is generally only important a few weeks before the Beta and Final releases, but it doesn't hurt to check just to keep it in mind.
+
+    #info Review release schedule
+    #link https://fedorapeople.org/groups/schedule/f-/f--magazine-tasks.html
+
+(where  is the release being developed)
 
 === 3/ Finished articles to review
 

From bb88ba2b39beffc493f4e499750785df68ca46c5 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: May 11 2021 23:07:25 +0000
Subject: [PATCH 94/148] Document how to fix an out-of-order invite


---

diff --git a/modules/ROOT/pages/technical-taiga.adoc b/modules/ROOT/pages/technical-taiga.adoc
index 4aded50..18d5023 100644
--- a/modules/ROOT/pages/technical-taiga.adoc
+++ b/modules/ROOT/pages/technical-taiga.adoc
@@ -18,6 +18,14 @@ To add a new user:
 
 The user is now added to the Magazine board and can be assigned to cards.
 
+If the invite was mistakenly issued before the user had logged in to teams.fedoraproject.org, use the following steps to get Taiga to reconnect the invite with the user's OpenID.
+
+. Click *Admin* (the gear icon) on the left-hand panel
+. Click *Members*
+. Find the *Pending* invite at the end of the Members list
+. Click the big red button at the end of the row (the trash can icon)
+. Redo the "To add a new user" steps above _after_ the user has logged in
+
 == Creating a new card (user story)
 
 When a proposal is approved, follow these steps.

From 818a9e6b7b3a0d5c0619bae98349d08b0b209809 Mon Sep 17 00:00:00 2001
From: Ben Cotton 
Date: May 20 2021 18:59:25 +0000
Subject: [PATCH 95/148] Hang up my pen


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 9167fbb..cb91801 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -22,7 +22,7 @@ To start the meeting, run the following set of commands.
     #startmeeting Magazine editorial board
     #meetingname magazine
     #topic Roll call
-    #chair ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr bcotton rlengland
+    #chair ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr rlengland
 
 People will then join using a `.hello2` or a `.hello NICK` command.
 

From 44d72aaaca633c6d0866ccc5c358946c27aad993 Mon Sep 17 00:00:00 2001
From: Michael S 
Date: Jul 02 2021 11:19:19 +0000
Subject: [PATCH 96/148] Remove mention of Freenode


---

diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index b38f10a..52792e6 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -21,7 +21,7 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin
 
 We also have regular xref:editorial-meetings.adoc[editorial board meetings].
 
-* IRC Channel: https://webchat.freenode.net/?channels=#fedora-magazine[#fedora-magazine]
+* IRC Channel: https://web.libera.chat/?channels=#fedora-magazine[#fedora-magazine]
 * Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]
 
 

From d4f618df282b9eea5810d35eb9f41e655ebcfa1b Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Jul 29 2021 14:15:50 +0000
Subject: [PATCH 97/148] update the list of weekly chairs


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index cb91801..fd26639 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -22,7 +22,7 @@ To start the meeting, run the following set of commands.
     #startmeeting Magazine editorial board
     #meetingname magazine
     #topic Roll call
-    #chair ryanlerch cverna asamalik sub_pop gregbartholomew jakfrost misc rwaltr rlengland
+    #chair glb rlengland theevilskeleton cverna asamalik
 
 People will then join using a `.hello2` or a `.hello NICK` command.
 

From 8124e7e0dd92da01ad2f75b8309b43c85e3397c1 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Jul 29 2021 14:19:25 +0000
Subject: [PATCH 98/148] update test days link


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index fd26639..4aabb24 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -64,7 +64,7 @@ You may also want to check the QA calendar for upcoming test days so that we can
 These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish.
 
     #info Are there any upcoming test days?
-    #link https://apps.fedoraproject.org/calendar/QA/
+    #link https://calendar.fedoraproject.org/QA/
 
 Also check the release schedule for upcoming tasks.
 This is generally only important a few weeks before the Beta and Final releases, but it doesn't hurt to check just to keep it in mind.

From c15349a4e818e989fd7bd1eda8eff193c08527cd Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Oct 24 2021 22:03:26 +0000
Subject: [PATCH 99/148] Kanban column renamed from 'Queued' to 'Scheduled'


---

diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg
index 8de741c..5c35467 100644
--- a/graphics-sources/fedora-magazine-workflow.svg
+++ b/graphics-sources/fedora-magazine-workflow.svg
@@ -2,20 +2,20 @@
 
 
 
+   inkscape:version="1.1 (c68e22c387, 2021-05-23)"
+   sodipodi:docname="fedora-magazine-workflow.svg"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+   xmlns:cc="http://creativecommons.org/ns#"
+   xmlns:dc="http://purl.org/dc/elements/1.1/">
   
     
     
     
-      
-    
-    
-      
-    
-    
     
     
-      
-    
-    
     
-    
-      
-    
-    
-      
-    
-    
-      
-    
   
   
+     inkscape:window-width="1920"
+     inkscape:window-height="1015"
+     inkscape:window-x="0"
+     inkscape:window-y="0"
+     inkscape:window-maximized="1"
+     showguides="false"
+     inkscape:pagecheckerboard="0" />
   
     
@@ -262,7 +179,6 @@
         image/svg+xml
         
-        
       
     
   
@@ -271,7 +187,8 @@
      inkscape:groupmode="layer"
      id="layer1">
     
       
-      
-        
-        
+      
+      Edit & Image
-        Edit & Image
+      by editors
-        
-        by editors
+      
+      Publishing
-        Publishing
+      by editors
-        
-        by editors
+      
+      Review
-        Review
+      by editors
-        
-        by editors
+      
+      Writing
-        Writing
+      by a writer
-        
-        by a writer
+      
+      Article proposal
-        Article proposal
+      by anyone
-        
-        
-        by anyone
+      
+      
+      idea
-        
-        idea
+      
+      article spec
-        
-        article spec
+      
+      in progress
-        
-        in progress
+      
+      review
-        
-        review
+      
+      to edit
-        
-        to edit
+      
+      queued
-        
-        scheduled
+      
+      published
-        
-        
-        
-        
-        
-        
-        
-        published
+      
+      
+      
+      
+      
+      
+      
+      Clarification
-        Clarification
+      by editors
-        
-        
-        
-        
-        
-        
-        
-        by editors
+      
+      
+      
+      
+      
+      
+      
+      1
-        1
+      3
-        3
+      5
-        5
+      2
-        2
+      4
-        4
+      6
-      
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6
     
     
       
       
       Article proposal
+           y="222.92404"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal
       by anyone
       
       idea
+           x="454.72266"
+           y="227.47343"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea
       
       
       1
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Clarification
       by editors
+           y="298.3587"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors
       
+         d="m 421.09827,283.46118 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" />
       
       2
       
       idea
+           x="454.72266"
+           y="283.9823"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea
       
       article spec
     
     
       
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Writing
       by a writer
+           y="381.66806"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by a writer
       
       article spec
       
       in progress
+           x="445.28943"
+           y="377.6868"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       review
       
+         d="m 421.09827,356.69357 c -5.35781,2.13738 -6.67873,5.87881 -6.68073,8.72281 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10762)" />
       
       
+         style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       3
+           x="337.68964"
+           y="380.58008"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">3
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
       Review
+           y="467.84222"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Review
       by editors
       
@@ -1200,317 +1072,303 @@
          sodipodi:nodetypes="csc"
          inkscape:connector-curvature="0"
          id="path14866"
-         d="m 421.09827,466.04696 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
-         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.2650001;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" />
+         d="m 421.09827,472.38915 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" />
       
       4
       
       in progress
+           x="445.28943"
+           y="450.90689"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       review
       
       to edit
+           x="451.69232"
+           y="493.92084"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
       Publishing
+           y="625.21753"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Publishing
       by editors
       
       
+         style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       6
+           x="337.4921"
+           y="632.14539"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6
       
       queued
+           sodipodi:role="line">scheduled
       
       published
+           x="446.92627"
+           y="639.73077"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">published
     
     
       
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Edit & Image
       by editors
+           y="560.36456"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors
       
       to edit
+           x="451.69232"
+           y="545.97424"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit
       
       queued
+           sodipodi:role="line">scheduled
       
+         d="m 421.09827,545.46705 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" />
       
       5
     
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg
index 03c83a1..14eb83f 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg
index a4f401d..68fa2fd 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg
index 73a1bd6..86b2436 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg
index 9e30879..cdca23b 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg
index f6d457f..7426150 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg
index d01f880..d544b10 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg
index eafd865..866655a 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ
diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index cb91801..e94c812 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -95,7 +95,7 @@ Assign an editor and a cover image designer to each article so it can be moved f
 === 5/ Publishing schedule
 
     #topic 5/ Publishing schedule
-    #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period.
+    #info Looking at the 'to edit' column, decide the publishing schedule for the next week.
     #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content.
     #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
 
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index 2de9cf9..dacdca8 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -18,7 +18,7 @@ Since multiple people will be potentially completing this step, they need to coo
 
 When done, indicate that in the comments.
 
-If the cover image has been also done (that would be indicated in the comments), move the card to  the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+If the cover image has also been done (that would be indicated by the absence of the __needs image__ tag), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
 
 == Creating a cover image
@@ -29,9 +29,9 @@ Since multiple people will be potentially completing this step, they need to coo
 
 **Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions.
 
-When done, indicate that in the comments.
+When done, indicate that by removing the __needs image__ tag.
 
-If the cover image has been also done (that would be indicated in the comments), move the card to  the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+If the editing has also been done (that would be indicated in the comments), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc
index c474122..51b0782 100644
--- a/modules/ROOT/pages/workflow-publishing.adoc
+++ b/modules/ROOT/pages/workflow-publishing.adoc
@@ -8,9 +8,10 @@ A member of the Editorial board either publishes or schedules an article for pub
 
 == Publishing an article
 
-Articles that are ready to be published are in the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that are ready to be published are in the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
-After publishing or scheduling them in Wordpress, move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+In preperation for the weekly editorial board meeting, the editor of the week will move cards for articles that have been published for at least one week from the __Scheduled__ column to the __Published (Archived)__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+The cards are left in the __Scheduled__ column for at least one week so the author can use it to request post-publication revisions if necessary.
 
 That's it!
 
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index baaeed8..a901677 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -13,7 +13,7 @@ Content on the Fedora Magazine is created using a 6-step workflow:
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 6. xref:workflow-publishing.adoc[Publishing] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __queued__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __scheduled__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 

From ccf863990f7dfdfb0e165bde5922e30c4a5d3014 Mon Sep 17 00:00:00 2001
From: Gregory Lee Bartholomew 
Date: Oct 29 2021 03:40:21 +0000
Subject: [PATCH 100/148] Merge #26 `Kanban column renamed from 'Queued' to 'Scheduled'`


---

diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg
index 8de741c..5c35467 100644
--- a/graphics-sources/fedora-magazine-workflow.svg
+++ b/graphics-sources/fedora-magazine-workflow.svg
@@ -2,20 +2,20 @@
 
 
 
+   inkscape:version="1.1 (c68e22c387, 2021-05-23)"
+   sodipodi:docname="fedora-magazine-workflow.svg"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+   xmlns:cc="http://creativecommons.org/ns#"
+   xmlns:dc="http://purl.org/dc/elements/1.1/">
   
     
     
     
-      
-    
-    
-      
-    
-    
     
     
-      
-    
-    
     
-    
-      
-    
-    
-      
-    
-    
-      
-    
   
   
+     inkscape:window-width="1920"
+     inkscape:window-height="1015"
+     inkscape:window-x="0"
+     inkscape:window-y="0"
+     inkscape:window-maximized="1"
+     showguides="false"
+     inkscape:pagecheckerboard="0" />
   
     
@@ -262,7 +179,6 @@
         image/svg+xml
         
-        
       
     
   
@@ -271,7 +187,8 @@
      inkscape:groupmode="layer"
      id="layer1">
     
       
-      
-        
-        
+      
+      Edit & Image
-        Edit & Image
+      by editors
-        
-        by editors
+      
+      Publishing
-        Publishing
+      by editors
-        
-        by editors
+      
+      Review
-        Review
+      by editors
-        
-        by editors
+      
+      Writing
-        Writing
+      by a writer
-        
-        by a writer
+      
+      Article proposal
-        Article proposal
+      by anyone
-        
-        
-        by anyone
+      
+      
+      idea
-        
-        idea
+      
+      article spec
-        
-        article spec
+      
+      in progress
-        
-        in progress
+      
+      review
-        
-        review
+      
+      to edit
-        
-        to edit
+      
+      queued
-        
-        scheduled
+      
+      published
-        
-        
-        
-        
-        
-        
-        
-        published
+      
+      
+      
+      
+      
+      
+      
+      Clarification
-        Clarification
+      by editors
-        
-        
-        
-        
-        
-        
-        
-        by editors
+      
+      
+      
+      
+      
+      
+      
+      1
-        1
+      3
-        3
+      5
-        5
+      2
-        2
+      4
-        4
+      6
-      
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6
     
     
       
       
       Article proposal
+           y="222.92404"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal
       by anyone
       
       idea
+           x="454.72266"
+           y="227.47343"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea
       
       
       1
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Clarification
       by editors
+           y="298.3587"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors
       
+         d="m 421.09827,283.46118 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" />
       
       2
       
       idea
+           x="454.72266"
+           y="283.9823"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea
       
       article spec
     
     
       
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Writing
       by a writer
+           y="381.66806"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by a writer
       
       article spec
       
       in progress
+           x="445.28943"
+           y="377.6868"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       review
       
+         d="m 421.09827,356.69357 c -5.35781,2.13738 -6.67873,5.87881 -6.68073,8.72281 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10762)" />
       
       
+         style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       3
+           x="337.68964"
+           y="380.58008"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">3
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
       Review
+           y="467.84222"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Review
       by editors
       
@@ -1200,317 +1072,303 @@
          sodipodi:nodetypes="csc"
          inkscape:connector-curvature="0"
          id="path14866"
-         d="m 421.09827,466.04696 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
-         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.2650001;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" />
+         d="m 421.09827,472.38915 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" />
       
       4
       
       in progress
+           x="445.28943"
+           y="450.90689"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       review
       
       to edit
+           x="451.69232"
+           y="493.92084"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit
     
     
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
       Publishing
+           y="625.21753"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Publishing
       by editors
       
       
+         style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       6
+           x="337.4921"
+           y="632.14539"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6
       
       queued
+           sodipodi:role="line">scheduled
       
       published
+           x="446.92627"
+           y="639.73077"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">published
     
     
       
       
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Edit & Image
       by editors
+           y="560.36456"
+           style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors
       
       to edit
+           x="451.69232"
+           y="545.97424"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit
       
       queued
+           sodipodi:role="line">scheduled
       
+         d="m 421.09827,545.46705 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" />
       
       5
     
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg
index 03c83a1..14eb83f 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg
index a4f401d..68fa2fd 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg
index 73a1bd6..86b2436 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg
index 9e30879..cdca23b 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg
index f6d457f..7426150 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg
index d01f880..d544b10 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg
index eafd865..866655a 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ
diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 4aabb24..a979741 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -95,7 +95,7 @@ Assign an editor and a cover image designer to each article so it can be moved f
 === 5/ Publishing schedule
 
     #topic 5/ Publishing schedule
-    #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period.
+    #info Looking at the 'to edit' column, decide the publishing schedule for the next week.
     #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content.
     #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
 
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index 2de9cf9..dacdca8 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -18,7 +18,7 @@ Since multiple people will be potentially completing this step, they need to coo
 
 When done, indicate that in the comments.
 
-If the cover image has been also done (that would be indicated in the comments), move the card to  the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+If the cover image has also been done (that would be indicated by the absence of the __needs image__ tag), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
 
 == Creating a cover image
@@ -29,9 +29,9 @@ Since multiple people will be potentially completing this step, they need to coo
 
 **Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions.
 
-When done, indicate that in the comments.
+When done, indicate that by removing the __needs image__ tag.
 
-If the cover image has been also done (that would be indicated in the comments), move the card to  the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+If the editing has also been done (that would be indicated in the comments), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc
index c474122..51b0782 100644
--- a/modules/ROOT/pages/workflow-publishing.adoc
+++ b/modules/ROOT/pages/workflow-publishing.adoc
@@ -8,9 +8,10 @@ A member of the Editorial board either publishes or schedules an article for pub
 
 == Publishing an article
 
-Articles that are ready to be published are in the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that are ready to be published are in the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
 
-After publishing or scheduling them in Wordpress, move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+In preperation for the weekly editorial board meeting, the editor of the week will move cards for articles that have been published for at least one week from the __Scheduled__ column to the __Published (Archived)__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+The cards are left in the __Scheduled__ column for at least one week so the author can use it to request post-publication revisions if necessary.
 
 That's it!
 
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index baaeed8..a901677 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -13,7 +13,7 @@ Content on the Fedora Magazine is created using a 6-step workflow:
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 6. xref:workflow-publishing.adoc[Publishing] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __queued__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __scheduled__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 

From d9489d0b8a8f623d6205f2b0db461e6e7b0d7997 Mon Sep 17 00:00:00 2001
From: Alessio 
Date: Nov 24 2021 19:18:51 +0000
Subject: [PATCH 101/148] libera.chat instead of freenode


Link to libera.chat instead of freenode
---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index a979741..f59361b 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -6,7 +6,7 @@ The goal of this meeting is to set and execute a publishing schedule of appropri
 
 :hash: #
 
-Meetings happen every week in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
+Meetings happen every week in the https://web.libera.chat/#fedora-meeting[{hash}fedora-meeting] channel on libera.chat. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
 Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week].
 If the meeting time changes, be sure to update the link in this paragraph.
 

From eae23f7a940c76cc2b87896f23ad58eece86333e Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 08 2021 18:56:35 +0000
Subject: [PATCH 102/148] Change Taiga references to Pagure. Modified process steps.


---

diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index 0e2dd51..7d38869 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] — click on the "OpenID Connect" button on the login form to log in with your Fedora Account. That is required before you can be added to the board as a writer.
+TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign and article to you.
 
 == A specific pitch example
 
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index 531c065..199583e 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -16,9 +16,11 @@ Opinions and additional relevant information is welcome from anyone.
 
 If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved.
 
-When a proposal is approved, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column.
+When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
 
-When the card is created, add the __Role: Editorial board member__ group to the Watchers. This ensures editors are emailed when the card status changes, so someone can react.
+When the card is created, add the __Assigne__, under the METADATA column.  This ensures the author is emailed when the card status changes.
+
+Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created.
 
 This card now represents a specific article and goes through all the other steps of the workflow.
 
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index dacdca8..03f8688 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -10,7 +10,7 @@ Members of the Editorial Board provide both of those.
 
 == Editing
 
-Articles that require editing are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
 Since multiple people will be potentially completing this step, they need to coordinate in comments in the card.
 
@@ -18,20 +18,17 @@ Since multiple people will be potentially completing this step, they need to coo
 
 When done, indicate that in the comments.
 
-If the cover image has also been done (that would be indicated by the absence of the __needs image__ tag), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
-
+If the cover image has also been done indicate that in the comments as well and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. 
 
 == Creating a cover image
 
-Articles that require a cover image are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
 Since multiple people will be potentially completing this step, they need to coordinate in comments in the card.
 
 **Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions.
 
-When done, indicate that by removing the __needs image__ tag.
-
-If the editing has also been done (that would be indicated in the comments), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+When done, indicate that the image is complete in the comments and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag.
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc
index 51b0782..ad07578 100644
--- a/modules/ROOT/pages/workflow-publishing.adoc
+++ b/modules/ROOT/pages/workflow-publishing.adoc
@@ -8,10 +8,9 @@ A member of the Editorial board either publishes or schedules an article for pub
 
 == Publishing an article
 
-Articles that are ready to be published are in the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that are ready to be published are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
-In preperation for the weekly editorial board meeting, the editor of the week will move cards for articles that have been published for at least one week from the __Scheduled__ column to the __Published (Archived)__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
-The cards are left in the __Scheduled__ column for at least one week so the author can use it to request post-publication revisions if necessary.
+After publishing or scheduling them in Wordpress, move the card to the __SCHEDULED__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].  This essentially archives the card.
 
 That's it!
 
diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc
index c93b8c2..0fe5876 100644
--- a/modules/ROOT/pages/workflow-review.adoc
+++ b/modules/ROOT/pages/workflow-review.adoc
@@ -8,16 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go.
 
 == Reviewing an article
 
-Articles that are ready for review are in the __Review__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
 === When article is good to go
 
-If the article is good to go, a member of the Editorial Board simply moves it to the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
-
+If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
 === When article needs changes
 
-If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __In Progress__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
 
 == Workflow
 **Previous step:** xref:writing-an-article.adoc[Writing]
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index a901677..a9c80fe 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -13,10 +13,10 @@ Content on the Fedora Magazine is created using a 6-step workflow:
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 6. xref:workflow-publishing.adoc[Publishing] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __scheduled__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 
 Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
 
-Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
+Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!

From 41d083ea923d0d0f9e1efd81d4ad2f9f364282ef Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 09 2021 00:43:10 +0000
Subject: [PATCH 103/148] Updated Taiga references to Pagure and ammended process steps


---

diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index 0ef289c..86b1f32 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -6,21 +6,22 @@ image::fedora-magazine-workflow-3.jpg[,100%,]
 
 Anyone with good writing skills is welcome to write an article for the Fedora Magazine!
 
-__Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the xref:getting-access.adoc[Getting Access] page for more information.__
+__Writing an article requires write access to our 
+https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__
 
 == Writing an article
 
 === 1. Choose what to write
 
-**Choose** any article you like in the __Article Spec__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga].
+**Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
-**Assign** the card you've chosen to yourself by opening the card and clicking on __Assign to myself__ on the right hand side.
+**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA c olumn on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
 
-**Move it to __In Progress__** by simply dragging the card to the appropriate column.
+**Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column.
 
 === 2. Write it 
 
-**Write** your article either https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there) or anywhere you prefer. Wordpress, however, will be the easiest for the editors to review and publish later. Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
+**Write** your article in https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
 
 https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval.
 
@@ -28,11 +29,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline
 
 === 3. Mark it as done
 
-**Move it to __Review__** when done with writing. Please include a link to Wordpress or to the text in the card before moving it to the __Review__ column so the Editors can access it.
+**Move it to __REVIEW__** when done with writing. Please include a link to the Wordpress Preview for your article in the comments on the card before moving it to the __REVIEW__ column so the Editors can access it.
 
 And that's it!
 
-Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done.
+Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and move it back to __REVIEW__ when you are done.
 
 == Workflow
 **Previous step:** xref:workflow-clarification.adoc[Clarification]

From 802ae86fb6fdbbddc61c94445ba564a9f154a790 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 09 2021 04:55:08 +0000
Subject: [PATCH 104/148] More Taiga to Pagure updates and necessary process changes.


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index bb20367..f3c5e07 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -86,6 +86,6 @@ Now use the helpful make target we’ve provided. This creates the correct sized
 
     $ make using-inkscape.jpg
 
-Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Taiga card for review.
+Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Pagure card for review.
 
 If the image is approved, and if it might be reused for later articles, then consider creating a pull request against the upstream repository to have your work archived for reuse.
diff --git a/modules/ROOT/pages/editor-of-the-week.adoc b/modules/ROOT/pages/editor-of-the-week.adoc
index d923b41..cbe339d 100644
--- a/modules/ROOT/pages/editor-of-the-week.adoc
+++ b/modules/ROOT/pages/editor-of-the-week.adoc
@@ -26,7 +26,7 @@ The Editor of the Week is expected to:
 * Routinely moderate comments (2-3 times a day is ideal)
 * Ensure the publication schedule is followed
 * Welcome new contributors
-* Convert approved proposals to Taiga cards
+* Convert approved proposals to Pagure cards
 * Chair the weekly xref:editorial-meetings.adoc[Magazine Editorial Board meeting]
 
 Note that Editors who are not the Editor of the Week may still perform the tasks above.
diff --git a/modules/ROOT/pages/editorial-add-contributors.adoc b/modules/ROOT/pages/editorial-add-contributors.adoc
index bf4b42d..ce241a3 100644
--- a/modules/ROOT/pages/editorial-add-contributors.adoc
+++ b/modules/ROOT/pages/editorial-add-contributors.adoc
@@ -2,18 +2,10 @@
 
 A contributor must have a FAS account before starting. Once they do, editors should help them get necessary access to join the team.
 
-The editor needs to be a member of the "admin" group in the Taiga team to complete this step.
+The editor needs to be an "admin" in the Fedora Magazine Pagure site to complete this step.
 
-== Adding to Taiga
+== Adding to Pagure
 
-Ask the contributor to login to the https://teams.fedoraproject.org[Taiga instance], using the OpenID option and their FAS account username and password.
+Ask the contributor to login to the https://pagure.io/fedora-magazine-newsroom/boards/articles[Pagure instance], using the OpenID option and their FAS account username and password and let you know when they have done so by leaving a comment in their article card.
 
-Find the user's email address. If you don't have that, you can find it through their contribution in the Magazine; their username there is also their FAS username. In Freenode IRC you can use this command:
-
-`/msg zodbot fasinfo `
-
-Go to the https://teams.fedoraproject.org[Taiga instance] and in the Magazine project, go to __Admin__ > __Members__ in the navigation bar, and use the control to add a __New Member__. Enter the new contributor's FAS email address.
-
-Once added, provide the appropriate role, which is usually __Writer__ for a new contributor.
-
-Now you can assign the new user to Taiga cards as well, and they'll receive notifications as appropriate.
\ No newline at end of file
+Now you can assign the new user to Pagure cards, and they'll receive notifications as appropriate.
diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index da19b6d..6785a1c 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -11,8 +11,8 @@ Note that contributors are required to sign the Fedora Project Contributor Agree
 https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress dashboard] using your Fedora Account.
 
 **3. Sign in to the Kanban board**:
-https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account.
-This does NOT grant write access. It is, so the account is known to the system and can be manually granted privileges by an administrator after step 4.
+https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account.
+This does NOT grant write access. It is so the account is known to the system, cards can be assigned to you, and you can be manually granted privileges by an administrator after step 4.
 
 **4. Join the Magazine forum and introduce yourself**:
 Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].

From 0e3358a29c41c3313a94c2b7d6b2e703dd047593 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Dec 09 2021 21:28:47 +0000
Subject: [PATCH 105/148] Remove step six (publish) from the workflow


---

diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg
index 14eb83f..488d742 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg
index 68fa2fd..84ce00f 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg
index 86b2436..ab31d68 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg
index 866655a..85c88f4 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 359432f..bf295c4 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -5,7 +5,6 @@
 ** xref:writing-an-article.adoc[3 Writing]
 ** xref:workflow-review.adoc[4 Review]
 ** xref:workflow-edit-image.adoc[5 Edit & Image]
-** xref:workflow-publishing.adoc[6 Publishing]
 * xref:writing-a-pitch.adoc[Proposing Articles]
 * xref:contributing.adoc[Contributing as a Writer]
 ** xref:getting-access.adoc[Getting Access]
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index 03f8688..f8b5aeb 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -32,5 +32,3 @@ When done, indicate that the image is complete in the comments and remove the __
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
-
-**Next step:** xref:workflow-publishing.adoc[Publishing]
diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc
deleted file mode 100644
index ad07578..0000000
--- a/modules/ROOT/pages/workflow-publishing.adoc
+++ /dev/null
@@ -1,18 +0,0 @@
-= Publishing Articles
-
-include::partial$workflow-change-banner.adoc[]
-
-image::fedora-magazine-workflow-6.jpg[,100%,]
-
-A member of the Editorial board either publishes or schedules an article for publishing.
-
-== Publishing an article
-
-Articles that are ready to be published are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
-
-After publishing or scheduling them in Wordpress, move the card to the __SCHEDULED__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].  This essentially archives the card.
-
-That's it!
-
-== Workflow
-**Previous step:** xref:workflow-edit-image.adoc[Edit & Image]
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index a9c80fe..13b4896 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -4,14 +4,13 @@ include::partial$workflow-change-banner.adoc[]
 
 image::fedora-magazine-workflow.jpg[,100%,]
 
-Content on the Fedora Magazine is created using a 6-step workflow:
+Content on the Fedora Magazine is created using a 5-step workflow:
 
 1. xref:workflow-article-proposal.adoc[Article Proposal] by Anyone
 2. xref:workflow-clarification.adoc[Clarification] by Editors
 3. xref:writing-an-article.adoc[Writing] by a Writer
 4. xref:workflow-review.adoc[Review] by Editors
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
-6. xref:workflow-publishing.adoc[Publishing] by Editors
 
 An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance.
 

From 5ff600ba8c85b7dd9776309d1554507c70d5f218 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Dec 09 2021 21:38:50 +0000
Subject: [PATCH 106/148] Update the template svg


---

diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg
index 5c35467..34cbcb9 100644
--- a/graphics-sources/fedora-magazine-workflow.svg
+++ b/graphics-sources/fedora-magazine-workflow.svg
@@ -7,7 +7,7 @@
    viewBox="0 0 210 297"
    id="svg2"
    version="1.1"
-   inkscape:version="1.1 (c68e22c387, 2021-05-23)"
+   inkscape:version="1.1.1 (3bf5ae0d25, 2021-09-20)"
    sodipodi:docname="fedora-magazine-workflow.svg"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
    xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
@@ -94,20 +94,6 @@
     
-      
-    
-    
     
+       id="g12442"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.661068;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Edit & Image
       by editors
-      
-      Publishing
-      by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
       Writing
       by a writer
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer
       
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       article spec
+           sodipodi:role="line">idea (approved)
       scheduled
-      
-      published
       
-      
@@ -562,7 +491,7 @@
            sodipodi:role="line">Clarification
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">by editors
       
-      
       4
-      6
     
     
+       id="g12572"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-1.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       1
     
     
+       id="g14372"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-2.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       Clarification
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       article spec
+           sodipodi:role="line">idea (approved)
     
     
+       id="g15528"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-3.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       Writing
       by a writer
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer
       article spec
+           sodipodi:role="line">idea (approved)
       to edit
     
     
-      
-      
-      Publishing
-      by editors
-      
-      
-      6
-      
-      scheduled
-      
-      published
-    
-    
Date: Dec 09 2021 23:27:40 +0000
Subject: [PATCH 107/148] Update the chat links to point to the new Matrix chat server


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index f59361b..4fe40fa 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -6,7 +6,8 @@ The goal of this meeting is to set and execute a publishing schedule of appropri
 
 :hash: #
 
-Meetings happen every week in the https://web.libera.chat/#fedora-meeting[{hash}fedora-meeting] channel on libera.chat. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
+Meetings happen every week in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org.
+See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
 Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week].
 If the meeting time changes, be sure to update the link in this paragraph.
 
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index 52792e6..c1e6c56 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -21,8 +21,10 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin
 
 We also have regular xref:editorial-meetings.adoc[editorial board meetings].
 
-* IRC Channel: https://web.libera.chat/?channels=#fedora-magazine[#fedora-magazine]
+:hash: #
+
 * Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]
+* Matrix Channel: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org]
 
 
 
diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc
index 84a4aee..aabad66 100644
--- a/modules/ROOT/pages/writing-guidelines.adoc
+++ b/modules/ROOT/pages/writing-guidelines.adoc
@@ -96,4 +96,6 @@ If the shot is large, like a large browser window, app, or whole screen, choose 
 
 == Other hints
 
-Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel.
+:hash: #
+
+Got an idea for better writing? Discuss with the editors in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org.

From 97f3d3956746965ae3f54c6f824505c29e9e6f36 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 11 2021 05:24:47 +0000
Subject: [PATCH 108/148] Typos corrected and Taiga URL changed to Pagure on one page


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index e0f88b9..62404f0 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -2,9 +2,9 @@
 
 include::partial$workflow-change-banner.adoc[]
 
-When a new writer joins the Magazine, they usually want to track their work in our kanban. Whether they take an existing article or suggest their own, an editor needs to add them to the kanban's list of permissions.
+When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
-. Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already.
+. Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
 . Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions
 . Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index 199583e..037d34f 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -18,7 +18,7 @@ If an editor is happy with the proposal, all they need to do is to reply "+1". P
 
 When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
 
-When the card is created, add the __Assigne__, under the METADATA column.  This ensures the author is emailed when the card status changes.
+When the card is created, add the __Assignee__, under the METADATA column.  This ensures the author is emailed when the card status changes.
 
 Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created.
 
diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index 86b1f32..d2591f4 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -15,7 +15,7 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the F
 
 **Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
-**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA c olumn on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
+**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA column on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
 
 **Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column.
 

From 30a4cff094e061d22b5d63c6792c4fc4b7b05293 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 11 2021 06:02:51 +0000
Subject: [PATCH 109/148] Merge #34 `Update the template svg`


---

diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg
index 5c35467..34cbcb9 100644
--- a/graphics-sources/fedora-magazine-workflow.svg
+++ b/graphics-sources/fedora-magazine-workflow.svg
@@ -7,7 +7,7 @@
    viewBox="0 0 210 297"
    id="svg2"
    version="1.1"
-   inkscape:version="1.1 (c68e22c387, 2021-05-23)"
+   inkscape:version="1.1.1 (3bf5ae0d25, 2021-09-20)"
    sodipodi:docname="fedora-magazine-workflow.svg"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
    xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
@@ -94,20 +94,6 @@
     
-      
-    
-    
     
+       id="g12442"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.661068;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       Edit & Image
       by editors
-      
-      Publishing
-      by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
       Writing
       by a writer
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer
       
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       article spec
+           sodipodi:role="line">idea (approved)
       scheduled
-      
-      published
       
-      
@@ -562,7 +491,7 @@
            sodipodi:role="line">Clarification
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">by editors
       
-      
       4
-      6
     
     
+       id="g12572"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-1.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       1
     
     
+       id="g14372"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-2.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       Clarification
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
       idea
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
       article spec
+           sodipodi:role="line">idea (approved)
     
     
+       id="g15528"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow-3.png"
+       inkscape:export-xdpi="96"
+       inkscape:export-ydpi="96">
       Writing
       by a writer
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer
       article spec
+           sodipodi:role="line">idea (approved)
       to edit
     
     
-      
-      
-      Publishing
-      by editors
-      
-      
-      6
-      
-      scheduled
-      
-      published
-    
-    
Date: Dec 11 2021 06:04:32 +0000
Subject: [PATCH 110/148] Merge #35 `Update the chat links to point to the new Matrix chat server`


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index f59361b..4fe40fa 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -6,7 +6,8 @@ The goal of this meeting is to set and execute a publishing schedule of appropri
 
 :hash: #
 
-Meetings happen every week in the https://web.libera.chat/#fedora-meeting[{hash}fedora-meeting] channel on libera.chat. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
+Meetings happen every week in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org.
+See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
 Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week].
 If the meeting time changes, be sure to update the link in this paragraph.
 
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index 52792e6..c1e6c56 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -21,8 +21,10 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin
 
 We also have regular xref:editorial-meetings.adoc[editorial board meetings].
 
-* IRC Channel: https://web.libera.chat/?channels=#fedora-magazine[#fedora-magazine]
+:hash: #
+
 * Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]
+* Matrix Channel: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org]
 
 
 
diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc
index 84a4aee..aabad66 100644
--- a/modules/ROOT/pages/writing-guidelines.adoc
+++ b/modules/ROOT/pages/writing-guidelines.adoc
@@ -96,4 +96,6 @@ If the shot is large, like a large browser window, app, or whole screen, choose 
 
 == Other hints
 
-Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel.
+:hash: #
+
+Got an idea for better writing? Discuss with the editors in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org.

From 800cb16192f9bafcb6acdcdfc86ca7a2a5053591 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 11 2021 06:18:36 +0000
Subject: [PATCH 111/148] Merge #37 `Typos corrected and Taiga URL changed to Pagure on one page`


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index e0f88b9..62404f0 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -2,9 +2,9 @@
 
 include::partial$workflow-change-banner.adoc[]
 
-When a new writer joins the Magazine, they usually want to track their work in our kanban. Whether they take an existing article or suggest their own, an editor needs to add them to the kanban's list of permissions.
+When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
-. Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already.
+. Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
 . Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions
 . Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index 199583e..037d34f 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -18,7 +18,7 @@ If an editor is happy with the proposal, all they need to do is to reply "+1". P
 
 When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
 
-When the card is created, add the __Assigne__, under the METADATA column.  This ensures the author is emailed when the card status changes.
+When the card is created, add the __Assignee__, under the METADATA column.  This ensures the author is emailed when the card status changes.
 
 Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created.
 
diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index 86b1f32..d2591f4 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -15,7 +15,7 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the F
 
 **Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
-**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA c olumn on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
+**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA column on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
 
 **Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column.
 

From a33bf7c9c62a24fd0eb91bda182e8588ecc89bb8 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Dec 14 2021 03:26:29 +0000
Subject: [PATCH 112/148] Show in workflow diagram that WordPress publishes the article


---

diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg
index 34cbcb9..292b273 100644
--- a/graphics-sources/fedora-magazine-workflow.svg
+++ b/graphics-sources/fedora-magazine-workflow.svg
@@ -11,6 +11,7 @@
    sodipodi:docname="fedora-magazine-workflow.svg"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
    xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns:xlink="http://www.w3.org/1999/xlink"
    xmlns="http://www.w3.org/2000/svg"
    xmlns:svg="http://www.w3.org/2000/svg"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
@@ -145,15 +146,15 @@
      inkscape:pageopacity="0.0"
      inkscape:pageshadow="2"
      inkscape:zoom="0.65388608"
-     inkscape:cx="1631.7827"
-     inkscape:cy="1192.8683"
+     inkscape:cx="1726.6005"
+     inkscape:cy="2459.9086"
      inkscape:document-units="mm"
      inkscape:current-layer="layer1"
      showgrid="false"
      inkscape:window-width="1920"
-     inkscape:window-height="1015"
+     inkscape:window-height="1020"
      inkscape:window-x="0"
-     inkscape:window-y="0"
+     inkscape:window-y="32"
      inkscape:window-maximized="1"
      showguides="false"
      inkscape:pagecheckerboard="0" />
@@ -173,446 +174,362 @@
      inkscape:groupmode="layer"
      id="layer1">
     
       
+         height="48.11499"
+         x="308.18182"
+         y="201.04749"
+         rx="4.99999"
+         ry="4.99999" />
       
+         height="21.155079"
+         x="-434.09418"
+         y="214.58308"
+         rx="5"
+         ry="5"
+         transform="scale(-1,1)" />
       Edit & Image
+           y="222.92404"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal
       by editors
+           id="tspan14622"
+           sodipodi:role="line">by anyone
       
       Review
+           id="tspan14628"
+           x="438.82303"
+           y="227.47343"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed)
+      
+      
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px"
+           y="229.85188"
+           x="337.47092"
+           id="tspan14636"
+           sodipodi:role="line">1
+    
+    
+      
       
       Writing
+           id="tspan14748"
+           sodipodi:role="line">Clarification
       by a writer
-      
-      Article proposal
+           y="298.3587"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
+      
+      
       by anyone
-      
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px"
+           y="296.93176"
+           x="337.47092"
+           id="tspan14772"
+           sodipodi:role="line">2
       
       idea (proposed)
       
       idea (approved)
+    
+    
       
+      
+         y="354.36618"
+         x="-434.09418"
+         height="42.857365"
+         width="103.00813"
+         id="rect14668"
+         style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
+      Writing
       in progress
+           id="tspan14676"
+           x="396.99249"
+           y="381.66806"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer
       
       review
+           y="356.56238"
+           x="438.87241"
+           id="tspan14682"
+           sodipodi:role="line">idea (approved)
       
       to edit
+           id="tspan14688"
+           x="445.28943"
+           y="377.6868"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       scheduled
-      
-      
-      
+           y="399.52756"
+           x="451.36777"
+           id="tspan14694"
+           sodipodi:role="line">review
       
       
-      
-      Clarification
-      by editors
-      
-      
       
-      
-      
-      
-      1
       3
-      5
-      2
-      4
     
     
+       id="g28831"
+       inkscape:export-filename="/home/gregory/Repositories/fedora-magazine/modules/ROOT/assets/images/fedora-magazine-workflow-4.png"
+       inkscape:export-xdpi="170.37"
+       inkscape:export-ydpi="170.37">
       
+         y="429.69043"
+         x="308.18182"
+         height="81.465591"
+         width="305.3287"
+         id="rect15153"
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
@@ -620,453 +537,2186 @@
          xml:space="preserve"
          style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:0%;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;letter-spacing:0px;word-spacing:0px;text-anchor:end;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
          x="396.90152"
-         y="222.92404"
-         id="text14616">Article proposal
+           y="467.84222"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Review
       by anyone
+           id="tspan14862"
+           sodipodi:role="line">by editors
+      
+      
+      
+      4
       
       idea (proposed)
-      
-      
+           id="tspan14720"
+           x="445.28943"
+           y="450.90689"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
+      
       1
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px"
+           y="472.74765"
+           x="451.36777"
+           id="tspan14726"
+           sodipodi:role="line">review
+      
+      to edit
     
+    
     
+       id="g186097"
+       inkscape:export-filename="/home/gregory/fedora-magazine-workflow.png"
+       inkscape:export-xdpi="170.37"
+       inkscape:export-ydpi="170.37">
       
+         id="rect15064"
+         style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.661068;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
       
       Clarification
+           id="tspan13098"
+           sodipodi:role="line">Edit & Image
+      by editors
+      
+      Review
+      by editors
+      
+      Writing
+      by a writer
+      
       by editors
-      
-      
+           id="tspan12890"
+           x="396.90152"
+           y="36.90889"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal
       2
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px"
+           y="45.26368"
+           x="396.99249"
+           id="tspan12894"
+           sodipodi:role="line">by anyone
+      
       
       idea (proposed)
       
       idea (approved)
-    
-    
-      
       
-      Writing
+         ry="5" />
       by a writer
+           id="tspan8101"
+           x="444.76117"
+           y="83.10939"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress
       
       idea (approved)
+           y="104.95016"
+           x="450.83951"
+           id="tspan8111"
+           sodipodi:role="line">review
       
       in progress
+           id="tspan8121"
+           x="451.16406"
+           y="126.12334"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit
       
+      
       scheduled
+      
+      
+      
+      
+      
+      
+      Clarification
+      review
+         x="523.56708"
+         y="55.740646"
+         id="text12882">by editors
       
-      
+         id="path13198"
+         d="m 421.09827,125.61616 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855"
+         style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" />
+      
       
+      
+      
+      
+      1
       3
-    
-    
-      
-      
+      5
       Review
-      by editors
-      
-      
-      
+           id="tspan13616"
+           x="591.20636"
+           y="54.407677"
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">2
       4
-      
+      
       in progress
-      
+           id="tspan1119"
+           x="558.07574"
+           y="142.45032"
+           style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman,  Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Publication
       review
-      
-      to edit
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px"
+           y="150.80511"
+           x="562.35132"
+           id="tspan1123"
+           sodipodi:role="line">by WordPress
+      
+      
     
     
       Edit & Image
       by editors
+           style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors
       to edit
       
+      5
+      
+      Publication
+      by WordPress
+      
+      
     
   
 
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg
index 7426150..b43c7c4 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ
diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg
index 85c88f4..4deea88 100644
Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ

From d46aab7903dc6e437381e3303416e548280b430e Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 14 2021 04:58:33 +0000
Subject: [PATCH 113/148] More fixes for types etc.


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index 62404f0..94814e9 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[]
 When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
 . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
+. Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
-. Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions
-. Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress
+. Follow these ihstructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index 7d38869..d445e9b 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign and article to you.
+TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign an article to you.
 
 == A specific pitch example
 

From 9eb385b6569b00d92c646e5ec8ee3f4d5b3a6174 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 14 2021 07:06:12 +0000
Subject: [PATCH 114/148] typos and clarifications


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index 94814e9..cfcae05 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -7,4 +7,4 @@ When a new writer joins the Magazine, they usually want to track their work in o
 . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
 . Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
-. Follow these ihstructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.
+. Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index d445e9b..31f2c88 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign an article to you.
+TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assign to you.
 
 == A specific pitch example
 

From 3d111ba6ac4c6588ff8b3c97a16903db15524ff5 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 14 2021 16:14:34 +0000
Subject: [PATCH 115/148] another typo


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index cfcae05..47b3593 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[]
 When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
 . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
-. Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
+. Have the writer setup a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
 . Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.

From 71b54f7497630da169597666f139b84821833fad Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 14 2021 16:20:43 +0000
Subject: [PATCH 116/148] Typo's (I really am not seeing what I type :-/ )


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index 47b3593..b1a95e4 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[]
 When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
 . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
-. Have the writer setup a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
+. Have the writer set up a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
 . Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.

From 620d3810e72bba4b969f6271ae27b85b4824945b Mon Sep 17 00:00:00 2001
From: Gregory Lee Bartholomew 
Date: Dec 14 2021 16:37:22 +0000
Subject: [PATCH 117/148] Merge #41 `typos again`


---

diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc
index 62404f0..b1a95e4 100644
--- a/modules/ROOT/pages/adding-a-writer.adoc
+++ b/modules/ROOT/pages/adding-a-writer.adoc
@@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[]
 When a new writer joins the Magazine, they usually want to track their work in our kanban.
 
 . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login.
+. Have the writer set up a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA).
 . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `.
-. Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions
-. Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress
+. Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress.
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index 7d38869..31f2c88 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign and article to you.
+TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assign to you.
 
 == A specific pitch example
 

From 3f285612a9ba552bebd8fa9183e7784b946d9767 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 15 2021 21:32:15 +0000
Subject: [PATCH 118/148] Reconciled process with Pagure. Added new Pagure tech page


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index bf295c4..c59e2d2 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -18,5 +18,5 @@
 ** xref:adding-a-writer.adoc[Adding a Writer]
 * xref:technical.adoc[Technical Notes and Processes]
 ** xref:technical-theme.adoc[Maintaining the Theme]
-** xref:technical-taiga.adoc[Taiga Operations]
+** xref:technical-pagure.adoc[Pagure Operations]
 ** xref:technical-wordpress.adoc[WordPress Operations]
diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc
index aeea037..4353704 100644
--- a/modules/ROOT/pages/contributing.adoc
+++ b/modules/ROOT/pages/contributing.adoc
@@ -5,10 +5,11 @@ include::partial$workflow-change-banner.adoc[]
 Fedora Magazine welcomes new writers to contribute their skill by writing an article or two... or five! There are several ways you can find something to write about:
 
  * We have a list of specific topics to start with — so you don't need to come up with new ideas to write.
+See the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
  * You can also xref:writing-a-pitch.adoc[propose an article] if you have your own idea.
  
 Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week!
 
 If this is your first contribution, you will need to xref:getting-access.adoc[get access] first.
 
-**Need help on how to write better? See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.**
\ No newline at end of file
+**Need help on how to write better? See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.**
diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 4fe40fa..bfb4d3b 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -55,11 +55,11 @@ First, let's look back at the previous week in terms of pageviews. This data can
 
     #topic 2/ In progress followup
     #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author?
-    #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
+    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work.
 
-Anything that's already finished can be moved to the Finished column.
+Anything that's already finished and commented so by the author can be moved to the "REVIEW" column.
 
 You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission.
 These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish.
@@ -78,17 +78,19 @@ This is generally only important a few weeks before the Beta and Final releases,
 === 3/ Finished articles to review
 
     #topic 3/ Finished articles to review
-    #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback.
-    #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
+    #info Looking at the 'REVIEW' column, let's decide which articles are good to go. Move each either to the 'TO-EDIT' or to the 'IN-PROGRESS' (needs more work) and provide feedback.
+    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
-Authors mark their articles as finished by moving them to this column. Review the articles and ehtier move them to the To Edit column, or in case they need some additional work, ask the author in the card about it and move it back the In Progress.
+Authors mark their articles as finished by adding a comment announcing that fact. Review the articles
+and ethier move them to the 'TO-EDIT' column, or in case they need some additional work, ask the
+author in the card about it and move it back to 'IN-PROGRESS'.
 
 
 === 4/ Articles to edit
 
     #topic 4/ Articles to edit
-    #info Looking at the 'to edit' column, assign an editor and a cover image creator.
-    #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
+    #info Looking at the 'TO-EDIT' column, assign an editor and a cover image creator.
+    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Assign an editor and a cover image designer to each article so it can be moved forward.
 
@@ -96,9 +98,9 @@ Assign an editor and a cover image designer to each article so it can be moved f
 === 5/ Publishing schedule
 
     #topic 5/ Publishing schedule
-    #info Looking at the 'to edit' column, decide the publishing schedule for the next week.
-    #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content.
-    #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
+    #info Looking at the 'TO-EDIT' column, decide the publishing schedule for the next week.
+    #info If there is not enough content, we might also need to look at the 'IN-PROGRESS' or even the 'IDEAS' columns to come up with additional content.
+    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting.
 
@@ -115,7 +117,7 @@ This can be generated by a script. Run:
 
     $ podman run --rm -it asamalik/magazine-schedule
 
-The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly.
+The script consumes data from the individual cards, so please make sure the date, and the editorrial assignees are set properly.
 
 Find more information about the script in the https://github.com/asamalik/magazine-schedule[asamalik/magazine-schedule github repository].
 
diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index 6785a1c..0bd1cb6 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -12,11 +12,12 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da
 
 **3. Sign in to the Kanban board**:
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account.
-This does NOT grant write access. It is so the account is known to the system, cards can be assigned to you, and you can be manually granted privileges by an administrator after step 4.
+This does NOT grant write access. It is so the account is known to the system and cards can be assigned to you.
 
 **4. Join the Magazine forum and introduce yourself**:
 Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].
 This is where we discuss everything to do with the Fedora Magazine.
 Introduce yourself and tell us that you wish to contribute to the Fedora Magazine.
-A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review.
+The Fedora Magazine editors monitor this Discourse forum and will be able to help you and answer any Fedora
+Magazine related questions.
 
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index c1e6c56..e93236b 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -2,7 +2,7 @@
 
 include::partial$workflow-change-banner.adoc[]
 
-http://fedoramagazine.org[Fedora Magazine] is a WordPress-based site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.)
+http://fedoramagazine.org[Fedora Magazine] is a __WordPress-based__ site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.)
 
 == What does the Magazine publish?
 
diff --git a/modules/ROOT/pages/technical-pagure.adoc b/modules/ROOT/pages/technical-pagure.adoc
new file mode 100644
index 0000000..fe99339
--- /dev/null
+++ b/modules/ROOT/pages/technical-pagure.adoc
@@ -0,0 +1,76 @@
+= Pagure Operations
+
+== Adding a new user
+
+If an author has not accessed Pagure before, they must login
+with their https://accounts.fedoraproject.org/#register[FAS account].
+The https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine site is here].
+They will need to select the *Log in* button in the upper right corner of the page. 
+This will allow the editors to assign cards to them.
+
+There is nothing more to do administratively.
+
+== Creating a new card (user story)
+
+When a proposal is approved, follow these steps.
+
+. From the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban page], 
+select the *New issues* button (upper right corner).
+. Enter the title of the article in the top text box
+. Enter details of the proposal in the bottom text box. __Include a link to the proposal 
+discussion__, where appropriate
+. If an author has been identified and has logged in to Pagure, select the *Assignee* 
+text box in the METADATA column at the right and locate their name
+. Select *Create Issue* at the bottom of the page
+
+When the new issue has been created, continue with these steps.
+
+. Select the "pencil icon" at the top of the METADATA column at the right
+. In the *Tags* selection field select "article" and "needs-image"
+. Select *Update* at the bottom of the METADATA column.
+
+The new card should appear at the bottom of the Kanban *IDEAS* column. If it does
+not you can add it by selecting the *+* at the top of the *IDEAS* column and entering the
+new "Issue" number.
+
+If you do not know the "Issue" number, select *Issues* at the top of the Kanban
+page and locate it in the list of issues.
+
+== Changing the state of the cards
+
+Authors must indicate, in the comments of each card, when they feel the state needs
+to change from __IDEAS__ to __IN-PROGRESS__ to __REVIEW__.
+
+The editors will change the state by "dragging" the cards on the Kanban page as needed.
+
+The editors will determine when the articles are ready to move to __TO EDIT__, drag
+the cards on the Kanban board, and add a comment to that effect to inform the author.
+
+== Adding editors
+
+Editors should be admins on the board. You must be an Administrator to add an editor.
+
+Use the following steps.
+
+. On the Kanban page, select the *Settings* tab at the top of the Pagure page
+. Select *Users & Groups* from the list in the left column on this page
+. Select *add user*
+. Type in the FAS "Username" in the first text field, to search. Note that the user must
+have logged into Pagure prior to this operation for the name to be available
+. Set the next field (a selection field) to *Admin*
+. Select *Add*
+
+== Removing editors
+
+You must be an Administrator to remove an editor.
+
+Use the following steps.
+
+. On the Kanban page, select the *Settings* tab at the top of the Pagure page.
+. Select *Users & Groups* from the list in the left column on this page.
+. Locate the name of the admin to remove and select the red "trash can" icon at the right
+of the name
+
+
+NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well 
+so that the docs and images repos have the correct permissions.
diff --git a/modules/ROOT/pages/technical.adoc b/modules/ROOT/pages/technical.adoc
index e079614..53d1341 100644
--- a/modules/ROOT/pages/technical.adoc
+++ b/modules/ROOT/pages/technical.adoc
@@ -2,4 +2,6 @@
 
 The Magazine site itself is simply a https://wordpress.org[WordPress site]. Like any website, it may require maintenance from time to time.
 
+Pagure is the system used to track the status of cards ("Issues") for the articles.
+
 One system that sometimes requires changes or fixes is the https://pagure.io/fedoramagazine-theme[Magazine theme]. There is a process to xref:technical-theme.adoc[modify, test, and deploy theme changes].
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index 31f2c88..f8acab7 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assign to you.
+TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assigned to you.
 
 == A specific pitch example
 
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index 037d34f..bea2929 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -16,11 +16,9 @@ Opinions and additional relevant information is welcome from anyone.
 
 If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved.
 
-When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
+When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
 
-When the card is created, add the __Assignee__, under the METADATA column.  This ensures the author is emailed when the card status changes.
-
-Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created.
+When the card is created, and the author is known, the owner is assigned in the __Assignee__ field, under the METADATA column.  This ensures the author is emailed when the card status changes. This operation is performed by the editor.
 
 This card now represents a specific article and goes through all the other steps of the workflow.
 
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index f8b5aeb..82d2b63 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -10,25 +10,26 @@ Members of the Editorial Board provide both of those.
 
 == Editing
 
-Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
-Since multiple people will be potentially completing this step, they need to coordinate in comments in the card.
+Since multiple people will be potentially completing this step, they need to coordinate with comments on the card.
 
-**Edit** the article for potential grammatical and spelling errors.
+The editors will **Edit** the article for potential grammatical and spelling errors. 
+When done, they indicate that in the comments.
 
-When done, indicate that in the comments.
-
-If the cover image has also been done indicate that in the comments as well and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. 
+If the cover image has also been done that will be indicated in the comments as well and the __needs-image__ tag will be removed from the METADATA column.
 
 == Creating a cover image
 
-Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
-Since multiple people will be potentially completing this step, they need to coordinate in comments in the card.
+Since multiple people will potentially be completing this step, they need to coordinate with comments on the card.
 
-**Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions.
+To **Create a cover image** for the article, see the xref:creating-an-image.adoc[Creating a featured image] 
+page for instructions. This function is usually done by an editor but the author may take on this task if 
+they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restriction on form and source for any image used.
 
-When done, indicate that the image is complete in the comments and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag.
+When the image is done this will be indicated in the comments and the __needs-image__ tag will be remove from the METADATA column by an editor.
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc
index 0fe5876..934dab5 100644
--- a/modules/ROOT/pages/workflow-review.adoc
+++ b/modules/ROOT/pages/workflow-review.adoc
@@ -8,15 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go.
 
 == Reviewing an article
 
-Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
 === When article is good to go
 
-If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
 
 === When article needs changes
 
-If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
 
 == Workflow
 **Previous step:** xref:writing-an-article.adoc[Writing]
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index 13b4896..656720d 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -12,10 +12,12 @@ Content on the Fedora Magazine is created using a 5-step workflow:
 4. xref:workflow-review.adoc[Review] by Editors
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 
 Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
 
-Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
+Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title.
+
+Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index d2591f4..bfe5405 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -7,21 +7,25 @@ image::fedora-magazine-workflow-3.jpg[,100%,]
 Anyone with good writing skills is welcome to write an article for the Fedora Magazine!
 
 __Writing an article requires write access to our 
-https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__
+https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__
 
 == Writing an article
 
 === 1. Choose what to write
 
-**Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
+**Choose** any article you like in the __IDEAS__ column in the 
+https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. 
+Or, https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/[propose your own].
 
-**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA column on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you.
+**Assign** Open a topic, if necessary in the the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum], and let the editors know you would like to be the author of an article. 
+Make certain you tell them the number. If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation.
 
-**Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column.
+The editors will assign the article to you and move it to **__IN-PROGRESS__** in the 
+https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
 
 === 2. Write it 
 
-**Write** your article in https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
+**Write** your article https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
 
 https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval.
 
@@ -29,11 +33,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline
 
 === 3. Mark it as done
 
-**Move it to __REVIEW__** when done with writing. Please include a link to the Wordpress Preview for your article in the comments on the card before moving it to the __REVIEW__ column so the Editors can access it.
+When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will **Move it to __REVIEW__**. Please make certain you include a link to the Wordpress Preview for your article in the comments on the card so the Editors can access it.
 
 And that's it!
 
-Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and move it back to __REVIEW__ when you are done.
+Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and let the editors know in the comments. They will move it back to __REVIEW__.
 
 == Workflow
 **Previous step:** xref:workflow-clarification.adoc[Clarification]

From 4f13d87c39a9c78f75e81ae97d0b5230ea645431 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 16 2021 00:06:04 +0000
Subject: [PATCH 119/148] Process changes updated due to Pagure transition. Pagure page added.


---

diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc
index 4353704..215ef9f 100644
--- a/modules/ROOT/pages/contributing.adoc
+++ b/modules/ROOT/pages/contributing.adoc
@@ -5,7 +5,7 @@ include::partial$workflow-change-banner.adoc[]
 Fedora Magazine welcomes new writers to contribute their skill by writing an article or two... or five! There are several ways you can find something to write about:
 
  * We have a list of specific topics to start with — so you don't need to come up with new ideas to write.
-See the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
+See the _ideas_ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
  * You can also xref:writing-a-pitch.adoc[propose an article] if you have your own idea.
  
 Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week!
diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index bfb4d3b..4f92a8a 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -59,7 +59,7 @@ First, let's look back at the previous week in terms of pageviews. This data can
 
 Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work.
 
-Anything that's already finished and commented so by the author can be moved to the "REVIEW" column.
+Anything that's already finished and commented so by the author can be moved to the "review" column.
 
 You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission.
 These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish.
@@ -78,18 +78,18 @@ This is generally only important a few weeks before the Beta and Final releases,
 === 3/ Finished articles to review
 
     #topic 3/ Finished articles to review
-    #info Looking at the 'REVIEW' column, let's decide which articles are good to go. Move each either to the 'TO-EDIT' or to the 'IN-PROGRESS' (needs more work) and provide feedback.
+    #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' or to the 'in-progress' (needs more work) and provide feedback.
     #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Authors mark their articles as finished by adding a comment announcing that fact. Review the articles
-and ethier move them to the 'TO-EDIT' column, or in case they need some additional work, ask the
-author in the card about it and move it back to 'IN-PROGRESS'.
+and ether move them to the _to-edit_ column, or in case they need some additional work, ask the
+author in the card about it and move it back to _in-progress_.
 
 
 === 4/ Articles to edit
 
     #topic 4/ Articles to edit
-    #info Looking at the 'TO-EDIT' column, assign an editor and a cover image creator.
+    #info Looking at the 'to-edit' column, assign an editor and a cover image creator.
     #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Assign an editor and a cover image designer to each article so it can be moved forward.
@@ -98,8 +98,8 @@ Assign an editor and a cover image designer to each article so it can be moved f
 === 5/ Publishing schedule
 
     #topic 5/ Publishing schedule
-    #info Looking at the 'TO-EDIT' column, decide the publishing schedule for the next week.
-    #info If there is not enough content, we might also need to look at the 'IN-PROGRESS' or even the 'IDEAS' columns to come up with additional content.
+    #info Looking at the 'to-edit' column, decide the publishing schedule for the next week.
+    #info If there is not enough content, we might also need to look at the 'in-progress' or even the 'ideas' columns to come up with additional content.
     #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting.
diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index 0bd1cb6..f0e1fcf 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -12,7 +12,11 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da
 
 **3. Sign in to the Kanban board**:
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account.
-This does NOT grant write access. It is so the account is known to the system and cards can be assigned to you.
+
+This is so the account is known to the system and you can edit card meta-data. If an editor has already 
+created a card for your idea, you should be able to assign the card to yourself. You will have to request 
+that the card's overall status (i.e. the column that it is in on the board) be changed by leaving a comment 
+in the card's comment section. Only the editors can update the card's status/column.
 
 **4. Join the Magazine forum and introduce yourself**:
 Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].
diff --git a/modules/ROOT/pages/technical-pagure.adoc b/modules/ROOT/pages/technical-pagure.adoc
index fe99339..0c008ce 100644
--- a/modules/ROOT/pages/technical-pagure.adoc
+++ b/modules/ROOT/pages/technical-pagure.adoc
@@ -5,7 +5,7 @@
 If an author has not accessed Pagure before, they must login
 with their https://accounts.fedoraproject.org/#register[FAS account].
 The https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine site is here].
-They will need to select the *Log in* button in the upper right corner of the page. 
+They will need to select the _Log in_ button in the upper right corner of the page. 
 This will allow the editors to assign cards to them.
 
 There is nothing more to do administratively.
@@ -15,35 +15,35 @@ There is nothing more to do administratively.
 When a proposal is approved, follow these steps.
 
 . From the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban page], 
-select the *New issues* button (upper right corner).
-. Enter the title of the article in the top text box
+select the _New issues_ button (upper right corner).
+. Enter the title of the article in the top text box.
 . Enter details of the proposal in the bottom text box. __Include a link to the proposal 
-discussion__, where appropriate
-. If an author has been identified and has logged in to Pagure, select the *Assignee* 
-text box in the METADATA column at the right and locate their name
-. Select *Create Issue* at the bottom of the page
+discussion__, where appropriate.
+. If an author has been identified and has logged in to Pagure, select the _Assignee_ 
+text box in the METADATA column at the right and locate their name.
+. Select _Create Issue_ at the bottom of the page.
 
 When the new issue has been created, continue with these steps.
 
-. Select the "pencil icon" at the top of the METADATA column at the right
-. In the *Tags* selection field select "article" and "needs-image"
-. Select *Update* at the bottom of the METADATA column.
+. Select the _pencil icon_ at the top of the METADATA column at the right.
+. In the _Tags_ selection field select _article_ and _needs-image_.
+. Select _Update_ at the bottom of the METADATA column.
 
-The new card should appear at the bottom of the Kanban *IDEAS* column. If it does
-not you can add it by selecting the *+* at the top of the *IDEAS* column and entering the
-new "Issue" number.
+The new card should appear at the bottom of the Kanban _ideas_ column. If it does
+not you can add it by selecting the *+* at the top of the _ideas_ column and entering the
+new Issue number.
 
-If you do not know the "Issue" number, select *Issues* at the top of the Kanban
+If you do not know the Issue number, select _Issues_ at the top of the Kanban
 page and locate it in the list of issues.
 
 == Changing the state of the cards
 
 Authors must indicate, in the comments of each card, when they feel the state needs
-to change from __IDEAS__ to __IN-PROGRESS__ to __REVIEW__.
+to change from _ideas_ to _in-progress_ to _review_.
 
 The editors will change the state by "dragging" the cards on the Kanban page as needed.
 
-The editors will determine when the articles are ready to move to __TO EDIT__, drag
+The editors will determine when the articles are ready to move to _to-edit_, drag
 the cards on the Kanban board, and add a comment to that effect to inform the author.
 
 == Adding editors
@@ -52,13 +52,13 @@ Editors should be admins on the board. You must be an Administrator to add an ed
 
 Use the following steps.
 
-. On the Kanban page, select the *Settings* tab at the top of the Pagure page
-. Select *Users & Groups* from the list in the left column on this page
-. Select *add user*
-. Type in the FAS "Username" in the first text field, to search. Note that the user must
-have logged into Pagure prior to this operation for the name to be available
-. Set the next field (a selection field) to *Admin*
-. Select *Add*
+. On the Kanban page, select the _Settings_ tab at the top of the Pagure page.
+. Select _Users & Groups_ from the list in the left column on this page.
+. Select _add user_.
+. Type in the FAS Username in the first text field, to search. Note that the user must
+have logged into Pagure prior to this operation for the name to be available.
+. Set the next field (a selection field) to _Admin_.
+. Select _Add_.
 
 == Removing editors
 
@@ -66,10 +66,10 @@ You must be an Administrator to remove an editor.
 
 Use the following steps.
 
-. On the Kanban page, select the *Settings* tab at the top of the Pagure page.
-. Select *Users & Groups* from the list in the left column on this page.
-. Locate the name of the admin to remove and select the red "trash can" icon at the right
-of the name
+. On the Kanban page, select the _Settings_ tab at the top of the Pagure page.
+. Select _Users & Groups_ from the list in the left column on this page.
+. Locate the name of the admin to remove and select the red trash can icon at the right
+of the name.
 
 
 NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well 
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index bea2929..ed3a5d9 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -16,7 +16,7 @@ Opinions and additional relevant information is welcome from anyone.
 
 If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved.
 
-When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column.
+When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __ideas__ column.
 
 When the card is created, and the author is known, the owner is assigned in the __Assignee__ field, under the METADATA column.  This ensures the author is emailed when the card status changes. This operation is performed by the editor.
 
diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc
index 82d2b63..68e430e 100644
--- a/modules/ROOT/pages/workflow-edit-image.adoc
+++ b/modules/ROOT/pages/workflow-edit-image.adoc
@@ -10,7 +10,7 @@ Members of the Editorial Board provide both of those.
 
 == Editing
 
-Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
+Articles that require editing are in the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
 Since multiple people will be potentially completing this step, they need to coordinate with comments on the card.
 
@@ -21,15 +21,15 @@ If the cover image has also been done that will be indicated in the comments as 
 
 == Creating a cover image
 
-Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
+Articles that require a cover image are in the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
 Since multiple people will potentially be completing this step, they need to coordinate with comments on the card.
 
 To **Create a cover image** for the article, see the xref:creating-an-image.adoc[Creating a featured image] 
 page for instructions. This function is usually done by an editor but the author may take on this task if 
-they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restriction on form and source for any image used.
+they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restrictions on form and source for any image used.
 
-When the image is done this will be indicated in the comments and the __needs-image__ tag will be remove from the METADATA column by an editor.
+When the image is done this will be indicated in the comments and the __needs-image__ tag will be removed from the METADATA column by an editor.
 
 == Workflow
 **Previous step:** xref:workflow-review.adoc[Review]
diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc
index 934dab5..b980412 100644
--- a/modules/ROOT/pages/workflow-review.adoc
+++ b/modules/ROOT/pages/workflow-review.adoc
@@ -8,15 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go.
 
 == Reviewing an article
 
-Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
+Articles that are ready for review are in the __review__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure].
 
 === When article is good to go
 
-If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
+If the article is good to go, a member of the Editorial Board simply moves it to the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
 
 === When article needs changes
 
-If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
+If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __in-progress__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board].
 
 == Workflow
 **Previous step:** xref:writing-an-article.adoc[Writing]
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index 656720d..76540b0 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[]
 
 image::fedora-magazine-workflow.jpg[,100%,]
 
-Content on the Fedora Magazine is created using a 5-step workflow:
+Content on the Fedora Magazine is created using a five-step workflow:
 
 1. xref:workflow-article-proposal.adoc[Article Proposal] by Anyone
 2. xref:workflow-clarification.adoc[Clarification] by Editors
@@ -12,12 +12,12 @@ Content on the Fedora Magazine is created using a 5-step workflow:
 4. xref:workflow-review.adoc[Review] by Editors
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through five states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 
-Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
+Proposals in the _idea_ state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
 
-Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title.
+Articles in all other states are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title.
 
 Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index bfe5405..42da94a 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -13,14 +13,14 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagur
 
 === 1. Choose what to write
 
-**Choose** any article you like in the __IDEAS__ column in the 
+**Choose** any article you like in the __ideas__ column in the 
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. 
 Or, https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/[propose your own].
 
 **Assign** Open a topic, if necessary in the the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum], and let the editors know you would like to be the author of an article. 
 Make certain you tell them the number. If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation.
 
-The editors will assign the article to you and move it to **__IN-PROGRESS__** in the 
+The editors will assign the article to you and move it to _in-progress_ in the 
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
 
 === 2. Write it 
@@ -33,11 +33,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline
 
 === 3. Mark it as done
 
-When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will **Move it to __REVIEW__**. Please make certain you include a link to the Wordpress Preview for your article in the comments on the card so the Editors can access it.
+When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will move it to _review_ in the Kanban board. Please make certain you include a link to the WordPress preview for your article in the comments on the card so the Editors can access it.
 
 And that's it!
 
-Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and let the editors know in the comments. They will move it back to __REVIEW__.
+Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the _in-progress_ column. Please make the requested change and let the editors know in the comments. They will move it back to _review_.
 
 == Workflow
 **Previous step:** xref:workflow-clarification.adoc[Clarification]

From 232d17d8a88fd14bb4c787db9ff5bff71382cbaf Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 16 2021 05:33:47 +0000
Subject: [PATCH 120/148] Removing the Taiga setup/admin page


---

diff --git a/modules/ROOT/pages/technical-taiga.adoc b/modules/ROOT/pages/technical-taiga.adoc
deleted file mode 100644
index 18d5023..0000000
--- a/modules/ROOT/pages/technical-taiga.adoc
+++ /dev/null
@@ -1,55 +0,0 @@
-= Taiga Operations
-
-== Adding a new user
-
-If an author has not written for us before, you will have to add them to Taiga.
-
-NOTE: Because we use OpenID authentication, the new member will have to log in to teams.fedoraproject.org with their Fedora account _before_ you can add them.
-
-To add a new user:
-
-. Click *Admin* (the gear icon) on the left-hand panel
-. Click *Members*
-. Click the *+New Member* button in the upper-right corner
-. Search by name or email address in the text box
-. Click the desired account
-. Select the *Writer* role from the *Choose a role* drop-down
-. Click the *Invite* button
-
-The user is now added to the Magazine board and can be assigned to cards.
-
-If the invite was mistakenly issued before the user had logged in to teams.fedoraproject.org, use the following steps to get Taiga to reconnect the invite with the user's OpenID.
-
-. Click *Admin* (the gear icon) on the left-hand panel
-. Click *Members*
-. Find the *Pending* invite at the end of the Members list
-. Click the big red button at the end of the row (the trash can icon)
-. Redo the "To add a new user" steps above _after_ the user has logged in
-
-== Creating a new card (user story)
-
-When a proposal is approved, follow these steps.
-
-. From the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban page], click the *+* button in the *Article Spec* column
-. Enter the title of the article in the top text box
-. Enter details of the proposal in the bottom text box, including a link to the proposal discussion where appropriate
-. Click *Add tag* and type "needs image" and click that tag
-. If an author has been identified and has an account in Taiga, click *Assign* and assign them
-. Click *Create*
-. Click the card you just created
-. Click the *Add watchers* button
-. Type "Editor" in the search box
-. Click *Role: Editorial board member* to add all editors as watchers
-. Click the *Add* button
-
-== Adding or removing editors
-
-To add or remove an editor, in Taiga:
-
-. Click *Admin* (the gear icon) on the left-hand panel
-. Click *Members*
-. Find the member in question
-. Select the desired role in the *Role* drop-down
-. Toggle the *Admin* slider (Editors should be admins on the board, non-editors should not)
-
-NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well so that the docs and images repos have the correct permissions.

From 75213e26a04d3723ffb9b4ba1af7e4bd495bf76c Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew 
Date: Dec 21 2021 16:34:24 +0000
Subject: [PATCH 121/148] Add Zinebot Operations page


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index c59e2d2..d5897f7 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -20,3 +20,4 @@
 ** xref:technical-theme.adoc[Maintaining the Theme]
 ** xref:technical-pagure.adoc[Pagure Operations]
 ** xref:technical-wordpress.adoc[WordPress Operations]
+** xref:technical-zinebot.adoc[Zinebot Operations]
diff --git a/modules/ROOT/pages/technical-zinebot.adoc b/modules/ROOT/pages/technical-zinebot.adoc
new file mode 100644
index 0000000..2e2e45e
--- /dev/null
+++ b/modules/ROOT/pages/technical-zinebot.adoc
@@ -0,0 +1,206 @@
+= Zinebot Operations
+
+Zinebot is a chatbot designed to help the xref:editor-of-the-week.adoc[editor of the week] run the xref:editorial-meetings.adoc[weekly meetings].
+Importantly, Zinebot is just an aid.
+It is not required to run the meetings.
+Its main purpose is to fetch information from various sources
+to save the meeting chair from having to jump between several browser tabs or applications
+and copy-paste information to or from the meeting chatroom.
+The meetings can still be run in the traditional way if Zinebot crashes or otherwise fails to function.
+
+== Installation
+
+See https://pagure.io/fedora-magazine-chatbot[the Fedora Magazine chatbot repo] for installation instructions.
+A good way to test Zinebot outside of meeting times
+is to create a private room on https://chat.fedoraproject.org[the Fedora Project Matrix homeserver]
+and invite the _zinebot_ user to the room.
+You will need to assign the room a https://github.com/vector-im/element-web/issues/13077[local address].
+You can then configure Zinebot to join that room.
+
+== Commands
+
+:tilde: ~
+
+Most of the Zinebot commands operate against https://pagure.io/fedora-magazine-newsroom/boards/articles[the Fedora Magazine kanban board].
+Notable exceptions include the `show`, `post` and `eotw` commands.
+
+All of the Zinebot commands must be prefixed with Zinebot's call sign and a space character.
+Zinebot's call sign is the unicode diamond operator (⋄).
+A convenient way to enter the diamond operator
+is by using the https://help.gnome.org/misc/release-notes/40.0/#:~:text=Improved%20Settings[compose key].
+For example, if the compose key is enabled and configured to be the right-alt key,
+then tapping the **Alt**, **<** and **>** keys in sequence should yield the diamond operator.
+If so desired, Zinebot's call sign can be changed by editing its `run` script.
+
+TIP: Add the line: +
+ +
+`   : "🔹" U1F539 # SMALL BLUE DIAMOND` +
+ +
+to your {tilde}/.XCompose file to remap the normal diamond operator compose sequence
+to generate a small blue diamond instead.
+You will need to restart your X11 or Wayland session for the change to take effect.
+Zinebot will accept the small blue diamond character (🔹) as an alternative call sign.
+You can still enter the normal diamond operator by tapping **Alt**, **>**, **<**.
+
+TIP: The full list of predefined compose keys can be found in the
+/usr/share/X11/locale/en_US.UTF-8/Compose system file.
+
+TIP: You can customize the single character codes that Zinebot will respond to
+by editing the {tilde}/.local/opt/zinebot/commands/hotkeys.pm file.
+
+=== 🔹 next topic
+
+Included with Zinebot is a `topics.txt` file containing a copy of xref:editorial-meetings.adoc[the meeting script].
+The `next topic` command will iteratively read the blocks of text listed in the `topics.txt` file and write them out in the chatroom.
+The text blocks in the file are separated by blank lines.
+
+Some topics correlate with specific columns on the kanban board.
+When appropriate, Zinebot will scan the cards from the corresponding kanban board column
+and write them out to the chatroom as a summarized list.
+Included in the summary for each card will be
+an indication of whether or not the author has signed the Fedora Project Contributor Agreement (FPCA).
+The status of the author's FPCA signature is retrieved directly
+from the Fedora Account System each time a card is retrieved from the kanban board.
+
+=== 🔹 next col[umn]
+
+Internally, Zinebot keeps track of which kanban column is currently being viewed.
+This command advances to the next column on the kanban board and lists its cards.
+Normally, this command should not be needed since the `next topic` command will take care of advancing to the appropriate column.
+
+=== 🔹 next card
+
+Internally, Zinebot keeps track of which card on the current kanban column is being viewed.
+This command advances to the next card in the column and displays its summary.
+If you want to view a specific card rather than iterating through them in order,
+see the `view` command below.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _right-pointing arrow_ (→).
+The call sign should be omitted when using the shorthand.
+
+=== 🔹 skip topic 
+
+This command allows you to skip to a specific topic.
+For example, `skip topic agenda` or `skip topic 7`.
+This command will reset the internal topic counter such that the result of a subsequent `next topic` command will be changed.
+Otherwise, this command behaves exactly like the `next topic` command.
+
+=== 🔹 show proposed
+
+When the _to-edit_ column is loaded in the current internal card deck,
+this command will read the scheduled publication dates from all the cards in the deck and list them out
+along with the card titles and assigned editors as a proposed editing and publication schedule.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _because_ symbol (∵).
+The call sign should be omitted when using the shorthand.
+
+NOTE: The default compose key sequence for the _because_ symbol is ****, **.**, **:**.
+
+=== 🔹 show agreed
+
+This command generates the same output as the `proposed` command described above.
+However, instead of starting with _#proposed_, the output will begin with _#agreed_.
+
+In the background, this command will also post the agreed-upon publication schedule to Fedora Magazine's channel
+on https://discussion.fedoraproject.org[the Fedora Project Discourse forum].
+The success or failure of each attempted post is indicated
+by a respective 🔹 or 🔸 at the end of each scheduled card.
+Only articles that are scheduled for the upcoming week should post successfully.
+Anything that is scheduled for an earlier or later date should automatically fail to post.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _therefore_ symbol (∴).
+The call sign should be omitted when using the shorthand.
+
+NOTE: The default compose key sequence for the _therefore_ symbol is ****, **:**, **.**.
+
+=== 🔹 show testdays
+
+This command scans https://calendar.fedoraproject.org/QA[the Fedora Project QA calendar] for test day events
+and displays them in the chatroom.
+The scan is limited to a three-week period that begins on Sunday of the current week.
+Test day events are identified as those whose _meeting location_ is set to _fedora-test-day*_.
+
+=== 🔹 show schedule
+
+This command scans https://fedorapeople.org/groups/schedule[the Fedora Project schedule] for scheduled Fedora Magazine publications
+such as beta and final release announcements.
+The results are then listed in the chatroom.
+
+=== 🔹 list [column]
+
+This command generates a summarized list of kanban cards from either
+the current kanban column or, if specified, the requested kanban column.
+The `next topic`, `skip topic` and `next column` commands call this command automatically.
+When a specific column is requested, all subsequent Zinebot commands will consider it the _current_ column.
+
+Internally, the `next card` and `view` Zinebot commands operate against a cache of cards retrieved from the current kanban column
+rather than fetching them from Pagure each time.
+This command repopulates the internal cache whenever it is called.
+The current card is also reset to the first card in the list.
+If you modify any of the cards that are cached, you may need to rerun this command to update the internal cache.
+
+=== 🔹 view [number]
+
+This command does exactly the same thing as the `next card` command.
+However, unlike the later, it allows you to specify a specific card number to display.
+The requested card must be loaded in the current card cache from a prior run of the `list` command.
+When a specific card is requested, the current card index for the next run of the `next card` command is not advanced.
+
+=== 🔹 card   [ ...]
+
+This is a low-level command that allows you to access individual card properties.
+When provided a card number, this command operates directly against Pagure.
+This command can access cards that are not in the current column.
+The following card properties are accessible through this command.
+
+[listing,indent=1]
+🞄 id
+🞄 title
+🞄 full_url
+🞄 content
+🞄 comments[:N]
+🞄 
+
+By default, the last three comments are retrieved from the card when the `comments` property is requested.
+The number of comments to retrieve can be specified by appending **:N** to the property name where **N** is a positive integer.
+All card comments can be requested by appending **:0** to the property name.
+
+=== 🔹 move   [row]
+
+This command moves the specified card to the specified kanban column.
+Optionally, the row offset at which the card should be placed in the target column can be specified.
+By default, cards are moved to the top of the target column (row 1).
+
+As a shorthand, you can use the unicode characters ← or → in place of the column name
+to signify the previous or next column respectively.
+
+NOTE: The default compose key sequence for the _leftwards arrow_ symbol is ****, **<**, **-**.
+
+NOTE: The default compose key sequence for the _rightwards arrow_ symbol is ****, **-**, **>**.
+
+=== 🔹 ping  
+
+This command adds a one-line comment to the specified card.
+Pagure should send an email notification to the card's assignee containing the comment.
+The comment does not need to be quoted.
+Everything after the card number is considered part of the comment.
+
+=== 🔹 post  [date [time]]
+
+This command posts an event to the Fedora Magazine calendar on Fedora's Discourse forum.
+If the date is not specified, it defaults to one week from the current day.
+If the time is not specified, it defaults to the beginning of the current hour.
+Dates must be specified as YYYY-MM-DD.
+Times must be specified as HH:MM:SS.
+Times are in Coordinated Universal Time (UTC).
+The title does not need to be quoted.
+Anything that does not match a date or time pattern is considered part of the event title.
+
+This command is called automatically by the `show agreed` command
+to add the agreed-upon articles to the publication calendar.
+
+=== 🔹 eotw 
+
+This command posts the editor of the week line.
+Just for fun, `king` and `queen` are aliases for this command. They may be easier to remember.
+

From c1758c954899cd6e34c01392282827d29f1d6655 Mon Sep 17 00:00:00 2001
From: Richard England 
Date: Dec 29 2021 20:24:22 +0000
Subject: [PATCH 122/148] Merge #44 `Add Zinebot Operations page`


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index c59e2d2..d5897f7 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -20,3 +20,4 @@
 ** xref:technical-theme.adoc[Maintaining the Theme]
 ** xref:technical-pagure.adoc[Pagure Operations]
 ** xref:technical-wordpress.adoc[WordPress Operations]
+** xref:technical-zinebot.adoc[Zinebot Operations]
diff --git a/modules/ROOT/pages/technical-zinebot.adoc b/modules/ROOT/pages/technical-zinebot.adoc
new file mode 100644
index 0000000..2e2e45e
--- /dev/null
+++ b/modules/ROOT/pages/technical-zinebot.adoc
@@ -0,0 +1,206 @@
+= Zinebot Operations
+
+Zinebot is a chatbot designed to help the xref:editor-of-the-week.adoc[editor of the week] run the xref:editorial-meetings.adoc[weekly meetings].
+Importantly, Zinebot is just an aid.
+It is not required to run the meetings.
+Its main purpose is to fetch information from various sources
+to save the meeting chair from having to jump between several browser tabs or applications
+and copy-paste information to or from the meeting chatroom.
+The meetings can still be run in the traditional way if Zinebot crashes or otherwise fails to function.
+
+== Installation
+
+See https://pagure.io/fedora-magazine-chatbot[the Fedora Magazine chatbot repo] for installation instructions.
+A good way to test Zinebot outside of meeting times
+is to create a private room on https://chat.fedoraproject.org[the Fedora Project Matrix homeserver]
+and invite the _zinebot_ user to the room.
+You will need to assign the room a https://github.com/vector-im/element-web/issues/13077[local address].
+You can then configure Zinebot to join that room.
+
+== Commands
+
+:tilde: ~
+
+Most of the Zinebot commands operate against https://pagure.io/fedora-magazine-newsroom/boards/articles[the Fedora Magazine kanban board].
+Notable exceptions include the `show`, `post` and `eotw` commands.
+
+All of the Zinebot commands must be prefixed with Zinebot's call sign and a space character.
+Zinebot's call sign is the unicode diamond operator (⋄).
+A convenient way to enter the diamond operator
+is by using the https://help.gnome.org/misc/release-notes/40.0/#:~:text=Improved%20Settings[compose key].
+For example, if the compose key is enabled and configured to be the right-alt key,
+then tapping the **Alt**, **<** and **>** keys in sequence should yield the diamond operator.
+If so desired, Zinebot's call sign can be changed by editing its `run` script.
+
+TIP: Add the line: +
+ +
+`   : "🔹" U1F539 # SMALL BLUE DIAMOND` +
+ +
+to your {tilde}/.XCompose file to remap the normal diamond operator compose sequence
+to generate a small blue diamond instead.
+You will need to restart your X11 or Wayland session for the change to take effect.
+Zinebot will accept the small blue diamond character (🔹) as an alternative call sign.
+You can still enter the normal diamond operator by tapping **Alt**, **>**, **<**.
+
+TIP: The full list of predefined compose keys can be found in the
+/usr/share/X11/locale/en_US.UTF-8/Compose system file.
+
+TIP: You can customize the single character codes that Zinebot will respond to
+by editing the {tilde}/.local/opt/zinebot/commands/hotkeys.pm file.
+
+=== 🔹 next topic
+
+Included with Zinebot is a `topics.txt` file containing a copy of xref:editorial-meetings.adoc[the meeting script].
+The `next topic` command will iteratively read the blocks of text listed in the `topics.txt` file and write them out in the chatroom.
+The text blocks in the file are separated by blank lines.
+
+Some topics correlate with specific columns on the kanban board.
+When appropriate, Zinebot will scan the cards from the corresponding kanban board column
+and write them out to the chatroom as a summarized list.
+Included in the summary for each card will be
+an indication of whether or not the author has signed the Fedora Project Contributor Agreement (FPCA).
+The status of the author's FPCA signature is retrieved directly
+from the Fedora Account System each time a card is retrieved from the kanban board.
+
+=== 🔹 next col[umn]
+
+Internally, Zinebot keeps track of which kanban column is currently being viewed.
+This command advances to the next column on the kanban board and lists its cards.
+Normally, this command should not be needed since the `next topic` command will take care of advancing to the appropriate column.
+
+=== 🔹 next card
+
+Internally, Zinebot keeps track of which card on the current kanban column is being viewed.
+This command advances to the next card in the column and displays its summary.
+If you want to view a specific card rather than iterating through them in order,
+see the `view` command below.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _right-pointing arrow_ (→).
+The call sign should be omitted when using the shorthand.
+
+=== 🔹 skip topic 
+
+This command allows you to skip to a specific topic.
+For example, `skip topic agenda` or `skip topic 7`.
+This command will reset the internal topic counter such that the result of a subsequent `next topic` command will be changed.
+Otherwise, this command behaves exactly like the `next topic` command.
+
+=== 🔹 show proposed
+
+When the _to-edit_ column is loaded in the current internal card deck,
+this command will read the scheduled publication dates from all the cards in the deck and list them out
+along with the card titles and assigned editors as a proposed editing and publication schedule.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _because_ symbol (∵).
+The call sign should be omitted when using the shorthand.
+
+NOTE: The default compose key sequence for the _because_ symbol is ****, **.**, **:**.
+
+=== 🔹 show agreed
+
+This command generates the same output as the `proposed` command described above.
+However, instead of starting with _#proposed_, the output will begin with _#agreed_.
+
+In the background, this command will also post the agreed-upon publication schedule to Fedora Magazine's channel
+on https://discussion.fedoraproject.org[the Fedora Project Discourse forum].
+The success or failure of each attempted post is indicated
+by a respective 🔹 or 🔸 at the end of each scheduled card.
+Only articles that are scheduled for the upcoming week should post successfully.
+Anything that is scheduled for an earlier or later date should automatically fail to post.
+
+As a shorthand for this command, Zinebot will accept a lone unicode _therefore_ symbol (∴).
+The call sign should be omitted when using the shorthand.
+
+NOTE: The default compose key sequence for the _therefore_ symbol is ****, **:**, **.**.
+
+=== 🔹 show testdays
+
+This command scans https://calendar.fedoraproject.org/QA[the Fedora Project QA calendar] for test day events
+and displays them in the chatroom.
+The scan is limited to a three-week period that begins on Sunday of the current week.
+Test day events are identified as those whose _meeting location_ is set to _fedora-test-day*_.
+
+=== 🔹 show schedule
+
+This command scans https://fedorapeople.org/groups/schedule[the Fedora Project schedule] for scheduled Fedora Magazine publications
+such as beta and final release announcements.
+The results are then listed in the chatroom.
+
+=== 🔹 list [column]
+
+This command generates a summarized list of kanban cards from either
+the current kanban column or, if specified, the requested kanban column.
+The `next topic`, `skip topic` and `next column` commands call this command automatically.
+When a specific column is requested, all subsequent Zinebot commands will consider it the _current_ column.
+
+Internally, the `next card` and `view` Zinebot commands operate against a cache of cards retrieved from the current kanban column
+rather than fetching them from Pagure each time.
+This command repopulates the internal cache whenever it is called.
+The current card is also reset to the first card in the list.
+If you modify any of the cards that are cached, you may need to rerun this command to update the internal cache.
+
+=== 🔹 view [number]
+
+This command does exactly the same thing as the `next card` command.
+However, unlike the later, it allows you to specify a specific card number to display.
+The requested card must be loaded in the current card cache from a prior run of the `list` command.
+When a specific card is requested, the current card index for the next run of the `next card` command is not advanced.
+
+=== 🔹 card   [ ...]
+
+This is a low-level command that allows you to access individual card properties.
+When provided a card number, this command operates directly against Pagure.
+This command can access cards that are not in the current column.
+The following card properties are accessible through this command.
+
+[listing,indent=1]
+🞄 id
+🞄 title
+🞄 full_url
+🞄 content
+🞄 comments[:N]
+🞄 
+
+By default, the last three comments are retrieved from the card when the `comments` property is requested.
+The number of comments to retrieve can be specified by appending **:N** to the property name where **N** is a positive integer.
+All card comments can be requested by appending **:0** to the property name.
+
+=== 🔹 move   [row]
+
+This command moves the specified card to the specified kanban column.
+Optionally, the row offset at which the card should be placed in the target column can be specified.
+By default, cards are moved to the top of the target column (row 1).
+
+As a shorthand, you can use the unicode characters ← or → in place of the column name
+to signify the previous or next column respectively.
+
+NOTE: The default compose key sequence for the _leftwards arrow_ symbol is ****, **<**, **-**.
+
+NOTE: The default compose key sequence for the _rightwards arrow_ symbol is ****, **-**, **>**.
+
+=== 🔹 ping  
+
+This command adds a one-line comment to the specified card.
+Pagure should send an email notification to the card's assignee containing the comment.
+The comment does not need to be quoted.
+Everything after the card number is considered part of the comment.
+
+=== 🔹 post  [date [time]]
+
+This command posts an event to the Fedora Magazine calendar on Fedora's Discourse forum.
+If the date is not specified, it defaults to one week from the current day.
+If the time is not specified, it defaults to the beginning of the current hour.
+Dates must be specified as YYYY-MM-DD.
+Times must be specified as HH:MM:SS.
+Times are in Coordinated Universal Time (UTC).
+The title does not need to be quoted.
+Anything that does not match a date or time pattern is considered part of the event title.
+
+This command is called automatically by the `show agreed` command
+to add the agreed-upon articles to the publication calendar.
+
+=== 🔹 eotw <username>
+
+This command posts the editor of the week line.
+Just for fun, `king` and `queen` are aliases for this command. They may be easier to remember.
+

From c57f9a576ec10464c47d3ed39aa567859bddcaea Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Dec 29 2021 20:52:14 +0000
Subject: [PATCH 123/148] Reconciled doc with zinebot topics.txt text/capitalization


---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 4f92a8a..23c04c9 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -20,10 +20,10 @@ The meeting is powered by https://fedoraproject.org/wiki/Zodbot[zodbot]. You can
 
 To start the meeting, run the following set of commands.
 
-    #startmeeting Magazine editorial board
+    #startmeeting magazine
     #meetingname magazine
-    #topic Roll call
-    #chair glb rlengland theevilskeleton cverna asamalik
+    #topic roll call
+    #chair glb rlengland theevilskeleton 
 
 People will then join using a `.hello2` or a `.hello NICK` command.
 
@@ -31,20 +31,20 @@ People will then join using a `.hello2` or a `.hello NICK` command.
 
 This is the standard agenda. Announcing it in advance helps newcomers understand the structure of the meeting.
 
-    #topic Agenda
+    #topic agenda
     #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/
-    #info -- 1/ Last week's stats --
-    #info -- 2/ In progress followup --
-    #info -- 3/ Finished articles to review --
-    #info -- 4/ Articles to edit --
-    #info -- 5/ Publishing schedule --
-    #info -- 6/ Editor of the Week --
-    #info -- 7/ Open floor --
+    #info -- 1/ last week's stats --
+    #info -- 2/ articles in progress --
+    #info -- 3/ articles to review --
+    #info -- 4/ articles to edit --
+    #info -- 5/ publishing schedule --
+    #info -- 6/ editor of the Week --
+    #info -- 7/ open floor --
 
 
 === 1/ Last week's stats
 
-    #topic 1/ Last week's stats
+    #topic 1/ last week's stats
 
 First, let's look back at the previous week in terms of pageviews. This data can be obtained in the https://fedoramagazine.org/admin[Fedora Magazine Wordpress]. On the https://fedoramagazine.org/wp-admin/index.php[Dashboard], scroll down to Stats by Jetpack.
 
@@ -53,9 +53,9 @@ First, let's look back at the previous week in terms of pageviews. This data can
 
 === 2/ In progress followup
 
-    #topic 2/ In progress followup
+    #topic 2/ in progress followup
     #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author?
-    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
+    #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work.
 
@@ -70,16 +70,16 @@ These tend to come in with very short notice, so the Editor of the Week should u
 Also check the release schedule for upcoming tasks.
 This is generally only important a few weeks before the Beta and Final releases, but it doesn't hurt to check just to keep it in mind.
 
-    #info Review release schedule
+    #info Check the release schedule.
     #link https://fedorapeople.org/groups/schedule/f-<N>/f-<N>-magazine-tasks.html
 
 (where <N> is the release being developed)
 
 === 3/ Finished articles to review
 
-    #topic 3/ Finished articles to review
-    #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' or to the 'in-progress' (needs more work) and provide feedback.
-    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
+    #topic 3/ articles to review
+    #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' (finished) column or to the 'in-progress' (needs more work) column and provide feedback.
+    #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Authors mark their articles as finished by adding a comment announcing that fact. Review the articles
 and ether move them to the _to-edit_ column, or in case they need some additional work, ask the
@@ -88,9 +88,9 @@ author in the card about it and move it back to _in-progress_.
 
 === 4/ Articles to edit
 
-    #topic 4/ Articles to edit
+    #topic 4/ articles to edit
     #info Looking at the 'to-edit' column, assign an editor and a cover image creator.
-    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
+    #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Assign an editor and a cover image designer to each article so it can be moved forward.
 
@@ -98,9 +98,9 @@ Assign an editor and a cover image designer to each article so it can be moved f
 === 5/ Publishing schedule
 
     #topic 5/ Publishing schedule
-    #info Looking at the 'to-edit' column, decide the publishing schedule for the next week.
+    #info Looking at the 'to-edit' column, decide the publishing schedule for the upcoming week.
     #info If there is not enough content, we might also need to look at the 'in-progress' or even the 'ideas' columns to come up with additional content.
-    #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles
+    #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles
 
 Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting.
 
@@ -133,7 +133,7 @@ When the schedule is set and agreed upon, announce it by:
 
 Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week].
 
-    #topic 6/ Editor of the Week
+    #topic 6/ editor of the Week
 
 Announce the volunteer using:
 
@@ -141,7 +141,7 @@ Announce the volunteer using:
 
 === 7/ Open floor
 
-    #topic 7/ Open floor
+    #topic 7/ open floor
 
 
 === Meeting ends

From 4069d71e86ecec3a37fb3b18cd3ed9ca6d2e4cc3 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: Dec 30 2021 01:19:02 +0000
Subject: [PATCH 124/148] Fix typo


---

diff --git a/modules/ROOT/pages/technical-zinebot.adoc b/modules/ROOT/pages/technical-zinebot.adoc
index 2e2e45e..77871c5 100644
--- a/modules/ROOT/pages/technical-zinebot.adoc
+++ b/modules/ROOT/pages/technical-zinebot.adoc
@@ -142,7 +142,7 @@ If you modify any of the cards that are cached, you may need to rerun this comma
 === 🔹 view [number]
 
 This command does exactly the same thing as the `next card` command.
-However, unlike the later, it allows you to specify a specific card number to display.
+However, unlike the latter, it allows you to specify a specific card number to display.
 The requested card must be loaded in the current card cache from a prior run of the `list` command.
 When a specific card is requested, the current card index for the next run of the `next card` command is not advanced.
 

From c4039e540e5672023f97fdad494ca9c68b89a423 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: Jan 05 2022 08:15:52 +0000
Subject: [PATCH 125/148] Updated some discussion.fedoraproject.org links


Also shortened some long lines to make future diffs easier to read on
the web interface.

---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index f0e1fcf..d236c42 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -19,7 +19,7 @@ that the card's overall status (i.e. the column that it is in on the board) be c
 in the card's comment section. Only the editors can update the card's status/column.
 
 **4. Join the Magazine forum and introduce yourself**:
-Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum].
+Join the discussion on the https://discussion.fedoraproject.org/tag/magazine[Fedora Magazine Discourse forum].
 This is where we discuss everything to do with the Fedora Magazine.
 Introduce yourself and tell us that you wish to contribute to the Fedora Magazine.
 The Fedora Magazine editors monitor this Discourse forum and will be able to help you and answer any Fedora
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index e93236b..92f7dcf 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -17,14 +17,25 @@ The content of the magazine varies, but mostly includes:
 
 == Join the Magazine Team
 
-We really need your help on the Magazine. Consider xref:contributing.adoc[writing an article]. You'll also find a link for how to join the marketing mailing list at that link. There is also a detailed guide on how to make a post on the magazine.
+We really need your help on the Magazine. Consider xref:contributing.adoc[writing an article].
+There is also a detailed guide on how to make a post on the magazine.
 
-We also have regular xref:editorial-meetings.adoc[editorial board meetings].
+We also have regular xref:editorial-meetings.adoc[editorial board meetings] on chat.fedoraproject.org.
+See the https://discussion.fedoraproject.org/t/meeting-and-publication-schedule/34554[Meeting and Publication Schedule]
+for exactly when and where.
 
 :hash: #
 
-* Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]
-* Matrix Channel: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org]
-
-
+We also have two areas on the discussion.fedoraproject.org forum for Fedora Magazine topics.
+One section (under the _Team Workflows_ category) is reserved just for article proposals.
+When you start a new topic there, the post should be pre-populated with a simple outline that you can complete to make a new proposal.
+The other area is for anything else related to Fedora Magazine.
+These can be posts about the site theme, the tools and platforms being used in the workflow,
+when weekly meetings will be held (or skipped), or anything else.
+All non-article-proposal posts concerning Fedora Magazine should be tagged with the special _{hash}magazine_ tag.
+
+* Chat Room: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] (powered by https://matrix.org[Matrix])
+* Forum: https://discussion.fedoraproject.org/
+** Click https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[here] to start a new article proposal.
+** Click https://discussion.fedoraproject.org/new-topic?category=project&tags=magazine[here] to start a new conversation about anything else related to Fedora Magazine.
 
diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc
index f8acab7..2894acd 100644
--- a/modules/ROOT/pages/workflow-article-proposal.adoc
+++ b/modules/ROOT/pages/workflow-article-proposal.adoc
@@ -10,17 +10,28 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a
 
 == Submitting an idea
 
-Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic.
+Join the community on the https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[Fedora Magazine Discourse forum]
+and submit your idea as a new topic.
 
-TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assigned to you.
+TIP: If this is your first proposal, and you also plan to write an article,
+you can help us speed the process up by logging into
+our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]
+— Select the __Log In__ button to log in with your Fedora Account.
+That is required before an article can be assigned to you.
 
 == A specific pitch example
 
-__The following article serves as an example outline for proposing a new pitch for the Fedora Magazine. This example was used for the https://fedoramagazine.org/never-leave-irc-znc/[Never leave IRC again with ZNC] article.__
+__The following article serves as an example outline for proposing a new pitch for the Fedora Magazine.
+This example was used for the https://fedoramagazine.org/never-leave-irc-znc/[Never leave IRC again with ZNC] article.__
 
 **Summary**: Describe how to set up an IRC bouncer using ZNC
 
-**Description**: The purpose of this article would be to describe what an IRC bouncer is and how someone can set up their own ZNC instance to connect to IRC networks and remain persistently connected to channels. The article would aim to educate the user about two things: what and how. Since IRC is a major communication platform for Fedora (and most free and open-source project communities), this article would ideally promote using IRC as well. The flow of the article would be as follows:
+**Description**: The purpose of this article would be to describe what an IRC bouncer is
+and how someone can set up their own ZNC instance to connect to IRC networks and remain persistently connected to channels.
+The article would aim to educate the user about two things: what and how.
+Since IRC is a major communication platform for Fedora (and most free and open-source project communities),
+this article would ideally promote using IRC as well.
+The flow of the article would be as follows:
 
 * What is an IRC bouncer / proxy and how does it work?
 * Introducing ZNC
diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc
index ed3a5d9..694809c 100644
--- a/modules/ROOT/pages/workflow-clarification.adoc
+++ b/modules/ROOT/pages/workflow-clarification.adoc
@@ -6,19 +6,27 @@ image::fedora-magazine-workflow-2.jpg[,100%,]
 
 The Editorial Board reviews each proposal and creates a specific article description.
 
-Proposals might be discussed with the person who proposed them, with subject matter experts, and anyone who wants (or has the technical ability to) give an input. We encourage anyone in the community to provide feedback to the proposals!
+Proposals might be discussed with the person who proposed them, with subject matter experts,
+and anyone who wants (or has the technical ability to) give an input.
+We encourage anyone in the community to provide feedback to the proposals!
 
 == Discussing and approving proposals
 
-Proposals are submitted to the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] as topics, and discussion happens right there.
+Proposals are submitted to the https://discussion.fedoraproject.org/c/workflows/magazine/57[Fedora Magazine Discourse forum]
+as topics, and discussion happens right there.
 
 Opinions and additional relevant information is welcome from anyone.
 
-If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved.
+If an editor is happy with the proposal, all they need to do is to reply "+1".
+Proposals with two or more +1's are approved.
 
-When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __ideas__ column.
+When a proposal is approved, a new card is created by an editor
+in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]
+in the __ideas__ column.
 
-When the card is created, and the author is known, the owner is assigned in the __Assignee__ field, under the METADATA column.  This ensures the author is emailed when the card status changes. This operation is performed by the editor.
+When the card is created, and the author is known, the owner is assigned in the __Assignee__ field under the METADATA column.
+This ensures the author is emailed when the card status changes.
+This operation is performed by the editor.
 
 This card now represents a specific article and goes through all the other steps of the workflow.
 
diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc
index 76540b0..7987b77 100644
--- a/modules/ROOT/pages/workflow.adoc
+++ b/modules/ROOT/pages/workflow.adoc
@@ -12,12 +12,20 @@ Content on the Fedora Magazine is created using a five-step workflow:
 4. xref:workflow-review.adoc[Review] by Editors
 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors
 
-An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through five states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance.
+An initial proposal lands in the __idea__ state.
+After some clarification, a specific article goes through five states.
+Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__.
+Each step in the workflow has its own page in this documentation that provides guidance.
 
 == Tracking
 
-Proposals in the _idea_ state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one!
+Article proposals in are initiated and discussed under the _Team Workflows_ section
+of the https://discussion.fedoraproject.org/c/workflows/magazine/57[Fedora Magazine Discourse forum].
+Everyone is welcome to submit one!
 
-Articles in all other states are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title.
+Articles in all other states are represented as cards
+in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure].
+Each state has its own column on the board with the appropriate title.
 
-Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week!
+Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor]
+and help us make wonderful content read by tens of thousands of readers every week!
diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc
index d16ddc2..c918543 100644
--- a/modules/ROOT/pages/writing-a-pitch.adoc
+++ b/modules/ROOT/pages/writing-a-pitch.adoc
@@ -4,6 +4,6 @@ include::partial$workflow-change-banner.adoc[]
 
 Fedora Magazine welcomes anyone to submit ideas for articles.
 
-Just propose your idea in our https://discussion.fedoraproject.org/c/project/magazine/[Fedora Magazine Discourse forum]
+Just propose your idea on our https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[Fedora Magazine Discourse forum].
 
 See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.
diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc
index 42da94a..0652679 100644
--- a/modules/ROOT/pages/writing-an-article.adoc
+++ b/modules/ROOT/pages/writing-an-article.adoc
@@ -6,8 +6,12 @@ image::fedora-magazine-workflow-3.jpg[,100%,]
 
 Anyone with good writing skills is welcome to write an article for the Fedora Magazine!
 
-__Writing an article requires write access to our 
-https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__
+__Writing an article requires write access
+to our https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure]
+(so you can indicate progress and exchange information with the editors)
+and to our https://fedoramagazine.org/admin[Wordpress instance]
+(where the articles are written).
+Read the xref:getting-access.adoc[Getting Access] page for more information.__
 
 == Writing an article
 
@@ -17,27 +21,44 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagur
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. 
 Or, https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/[propose your own].
 
-**Assign** Open a topic, if necessary in the the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum], and let the editors know you would like to be the author of an article. 
-Make certain you tell them the number. If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation.
+**Assign** Open a topic,
+if necessary in the the https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[Fedora Magazine Discourse forum],
+and let the editors know you would like to be the author of an article.
+Make certain you tell them the number.
+If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation.
 
 The editors will assign the article to you and move it to _in-progress_ in the 
 https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board].
 
 === 2. Write it 
 
-**Write** your article https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
+**Write** your article https://fedoramagazine.org/admin[in the Magazine Wordpress]
+(create a new article there).
+Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style.
 
-https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval.
+https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well,
+and make it as useful as possible to readers.
+Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval.
 
-As you write your draft, try to understand and follow the xref:writing-guidelines.adoc[style, grammar, and SEO guidelines] for the Magazine. Don’t skip this step! The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines. Also, if you write a better article, the editors are more likely to publish it sooner.
+As you write your draft, try to understand and follow
+the xref:writing-guidelines.adoc[style, grammar, and SEO guidelines] for the Magazine.
+Don’t skip this step!
+The guidelines tell you how to use markup, write better sentences, and get your article ranked well in search engines.
+Also, if you write a better article, the editors are more likely to publish it sooner.
 
 === 3. Mark it as done
 
-When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will move it to _review_ in the Kanban board. Please make certain you include a link to the WordPress preview for your article in the comments on the card so the Editors can access it.
+When you feel you are done writing the article and it is ready for review,
+state that in a comment on your card in Pagure.
+The editors will move it to _review_ in the Kanban board.
+Please make certain you include a link to the WordPress preview for your article in the comments on the card so the Editors can access it.
 
 And that's it!
 
-Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the _in-progress_ column. Please make the requested change and let the editors know in the comments. They will move it back to _review_.
+Please note that in some cases the editors might require a change in your article.
+In that case, you'll receive feedback in the card, and it will be moved back to the _in-progress_ column.
+Please make the requested change and let the editors know in the comments.
+They will move it back to _review_.
 
 == Workflow
 **Previous step:** xref:workflow-clarification.adoc[Clarification]

From 322d7e5d53d9161ddb472438a61c0ed02c733bd3 Mon Sep 17 00:00:00 2001
From: Benson Muite <benson_muite@emailplus.org>
Date: Apr 15 2022 13:47:36 +0000
Subject: [PATCH 126/148] Add Inkscape and Git links


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index f3c5e07..5e87e5a 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[]
 
 Each article in the Fedora Magazine must have a featured image. The image gives the article added visual appeal. It also appears in links on social media, to attract more viewers.
 
-These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. 
+These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as https://inkscape.org[Inkscape]. You will also need the https://git-scm.com/[git] utility installed. 
 
 Watch the https://youtu.be/F6Nf1gsR9S4[Creating Featured Images Workshop video] on our YouTube channel for a visual demo of the guidelines and instructions below, plus some additional Inkscape tips.
 

From 71927457bd82510c8f58d993108254c85935ea3e Mon Sep 17 00:00:00 2001
From: Benson Muite <benson_muite@emailplus.org>
Date: Apr 15 2022 14:13:11 +0000
Subject: [PATCH 127/148] Use plain text instead of links


Simplify following reviewer suggestions.
---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 5e87e5a..234a78a 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[]
 
 Each article in the Fedora Magazine must have a featured image. The image gives the article added visual appeal. It also appears in links on social media, to attract more viewers.
 
-These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as https://inkscape.org[Inkscape]. You will also need the https://git-scm.com/[git] utility installed. 
+These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape. You will also need the git utility installed. 
 
 Watch the https://youtu.be/F6Nf1gsR9S4[Creating Featured Images Workshop video] on our YouTube channel for a visual demo of the guidelines and instructions below, plus some additional Inkscape tips.
 

From 3a62926dc0bf704bc37197d2f9d98dbf6bb4a470 Mon Sep 17 00:00:00 2001
From: Benson Muite <benson_muite@emailplus.org>
Date: Apr 15 2022 14:34:10 +0000
Subject: [PATCH 128/148] Add link to fedoramagazine-images repository


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index f3c5e07..095929b 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -24,7 +24,7 @@ Install the git and inkscape packages if you don’t have them installed already
     $ sudo dnf install git inkscape
 
 
-Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the repository.
+Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the fedoramagazine-images[https://pagure.io/fedoramagazine-images]repository.
 
 == Creating a new image using the template
 

From 075cc16b6680e9db406fe4ccef4ad57943c9b5cd Mon Sep 17 00:00:00 2001
From: Benson Muite <benson_muite@emailplus.org>
Date: Apr 15 2022 14:40:18 +0000
Subject: [PATCH 129/148] Correct link syntax


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 095929b..58b8298 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -24,7 +24,7 @@ Install the git and inkscape packages if you don’t have them installed already
     $ sudo dnf install git inkscape
 
 
-Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the fedoramagazine-images[https://pagure.io/fedoramagazine-images]repository.
+Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the https://pagure.io/fedoramagazine-images[fedoramagazine-images] repository.
 
 == Creating a new image using the template
 

From 5712a90a022dbd799562d0f86fed3213a182303f Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Apr 15 2022 15:10:17 +0000
Subject: [PATCH 130/148] Merge #50 `Add Inkscape and Git links`


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 58b8298..5e3a816 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[]
 
 Each article in the Fedora Magazine must have a featured image. The image gives the article added visual appeal. It also appears in links on social media, to attract more viewers.
 
-These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape[Inkscape]. You will also need the git[git] utility installed. 
+These images are created as SVG (scalable vector graphic) images. To work with these images, you should install a SVG capable application such as Inkscape. You will also need the git utility installed. 
 
 Watch the https://youtu.be/F6Nf1gsR9S4[Creating Featured Images Workshop video] on our YouTube channel for a visual demo of the guidelines and instructions below, plus some additional Inkscape tips.
 

From 8041235ae94eeaf2bd5453d5c7a0b8848780e9c7 Mon Sep 17 00:00:00 2001
From: Benson Muite <benson_muite@emailplus.org>
Date: Apr 17 2022 16:24:41 +0000
Subject: [PATCH 131/148] Use dnf to install fonts


Indicated how to use dnf to install packaged fonts. Bungee is not yet packaged, though there is a ticket for this, so it can be added if it becomes packaged.
---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 5e3a816..3c5a046 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -68,10 +68,14 @@ There are a few fonts that are commonly used in featured images. You are encoura
 . https://www.fontsquirrel.com/fonts/roboto-slab[Roboto Slab] (friendly with serifs)
 . https://www.fontsquirrel.com/fonts/molot[Molot] (heavier font, feels technical)
 
-To use these fonts on your Fedora system, download the font and unpack the OTF or TTF file (if required) into your ~/.fonts folder. Then update your font cache:
+To use these fonts on your Fedora system, either download the font and unpack the OTF or TTF file (if required) into your ~/.fonts folder. Then update your font cache:
 
     $ fc-cache
 
+or, where the font is packaged, install it using the package manager
+
+    $ dnf install open-sans-fonts vernnobile-oswald-fonts mozilla-zilla-slab-fonts astigmatic-grand-hotel-fonts julietaula-montserrat-fonts google-roboto-slab-fonts typetype-molot-fonts
+   
 You will need to close and reopen Inkscape, GIMP, or other applications to take advantage of the new fonts.
 
 == Getting your work reviewed

From 1bd22237461d1a12ecc6580a1a1643fd5629dafc Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: May 15 2022 23:16:49 +0000
Subject: [PATCH 132/148] Update site.yml to work with Antora version 3


---

diff --git a/site.yml b/site.yml
index f0149bd..4cc30ae 100644
--- a/site.yml
+++ b/site.yml
@@ -16,5 +16,5 @@ output:
   destinations: 
   - provider: archive 
 runtime:
-  pull: true
+  fetch: true
   cache_dir: ./cache

From 60be2eb53248786cf1104a17b4dcf6a9aa9fafa5 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: May 15 2022 23:47:50 +0000
Subject: [PATCH 133/148] Also update 'start_page' references to work with Antora v3


---

diff --git a/antora.yml b/antora.yml
index 93ff675..ffc9ace 100644
--- a/antora.yml
+++ b/antora.yml
@@ -9,7 +9,7 @@ title: Fedora Magazine # <---- PLEASE MODIFY
 version: master
 
 # We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. 
-start_page: ROOT:index
+# start_page: ROOT:index.adoc
 
 # This lists all the menu definitions of your component.
 nav:
diff --git a/site.yml b/site.yml
index 4cc30ae..590092c 100644
--- a/site.yml
+++ b/site.yml
@@ -1,6 +1,6 @@
 site: 
   title: Fedora Magazine
-  start_page: fedora-magazine::index
+  start_page: fedora-magazine::index.adoc
 content:
   sources:
    - url: .

From 11e85edf233f910ec723761b5678af2e5bbcbc63 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: May 15 2022 23:57:20 +0000
Subject: [PATCH 134/148] Theme: Update documentation show how to use Podman instead of Vagrant


---

diff --git a/modules/ROOT/pages/technical-theme.adoc b/modules/ROOT/pages/technical-theme.adoc
index 96c21c1..155670d 100644
--- a/modules/ROOT/pages/technical-theme.adoc
+++ b/modules/ROOT/pages/technical-theme.adoc
@@ -1,14 +1,36 @@
 = Maintaining the Magazine Theme
 
-The Magazine theme is maintained in https://pagure.io/fedoramagazine-theme[a Pagure repository]. If you want to submit a change, start by forking and/or cloning this repository. This page does not cover git workflow; consult https://git-scm.com/doc[git documentation] for more information, or ask the Magazine staff for help.
+The Magazine theme is maintained in
+https://pagure.io/fedoramagazine-theme[a Pagure repository].
+If you want to submit a change, start by forking and/or cloning this repository.
+This page does not cover git workflow;
+consult https://git-scm.com/doc[git documentation] for more information,
+or ask the Magazine staff for help.
 
 == Testing your changes
 
-The `Vagrantfile` lets you deploy a test system to try out your work before you deploy. Ensure you are in the cloned repository in the same directory as the `Vagrantfile`, and run the command `vagrant up` to create and provision the box. This will take some time.
-
-When done, you can point your local browser at http://localhost:5055 to see the theme in action on a test site. The Vagrant box accesses the contents of the repo directly, so you can edit changes in the repository and quickly see them in action. To iterate on changes, after modifying the theme, run `vagrant ssh -- systemctl reload httpd` so the Vagrant box's web caching is cleared. Then reload on your browser to see the modifications at work.
-
-When finished, run `vagrant halt` to stop the Vagrant box, or `vagrant destroy` to remove it from your system entirely.
+The `build.sh` and `preview.sh` scripts let you deploy WordPress in a local container
+to test your work before you push your changes to the live site.
+Ensure you are in the root of the cloned repository and enter
+`./build.sh && ./preview.sh` to create and provision the container.
+This will take some time.
+
+When done, you can point your local browser at http://localhost:5055
+to see the theme with your local revisions.
+The container accesses the contents of the repo directly,
+so you can edit changes in the repository and quickly see them in action.
+To iterate on changes, after modifying the theme,
+run `podman restart wordpress` from another terminal window
+so the containers's web caching is cleared.
+Then refresh your browser window (F5 or Ctrl+F5) to view the modifications.
+
+When finished, press **Ctrl**+**C** in the original terminal window
+from which you launched the container to stop the container.
+Optionally, you can run `./clean.sh` to remove all the contianer artifacts
+except for the repo itself from your system.
+If you remove all the artifacts (WordPress plugins, databases, etc.)
+it will take longer to run the `build.sh` and `preview.sh` commands the
+next time because everything will need to be re-downloaded and re-installed.
 
 == Tagging the theme
 

From 0ca24c42e375ffee8f05411d8034ff1fdcd67168 Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: May 19 2022 23:09:52 +0000
Subject: [PATCH 135/148] Add section for WordPress operations for updating the sidebar to show

the current release version.

---

diff --git a/README.md b/README.md
index 48aac47..7ed658b 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,7 @@ This repository contains sources of the [Fedora Magazine documentation](https://
 
 This repo includes scripts to build and preview the contents of this repository.
 
-**NOTE**: Please note that if you reference pages from other repositoreis, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions.
+**NOTE**: Please note that if you reference pages from other repositories, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions.
 
 Both scripts work on Fedora (using Podman) and macOS (using Docker).
 
@@ -53,4 +53,4 @@ Fedora Workstation doesn't come with Podman preinstalled by default — so you 
 
 ```
 $ sudo dnf install podman
-```
\ No newline at end of file
+```
diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
index a34072c..074f844 100644
--- a/modules/ROOT/pages/technical-wordpress.adoc
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -58,3 +58,100 @@ In the https://fedoramagazine.org/wp-admin/[WordPress dashboard]:
 
 If you do not know what the name of the series is, you can look in the https://fedoramagazine.org/wp-admin/edit-tags.php?taxonomy=post_series[Post Series] screen.
 This is located under the *Posts* section of the left-hand menu.
+
+== Update the current release image/text/link in the Fedora Magazine sidebar
+
+The Fedora Magazine WordPress site contains a column on the right side of the page
+that includes several "Widgets". One of these contains the default image (often
+the background) for the latest version and links to _getfedora.org_ and the 
+appropriate release announcement.
+
+The information in this widget must be changed when a new release occurs. This
+section describes the process for making the necessary changes.
+
+
+=== Navigate to the Sidebar Widget
+
+In the https://fedoramagazine.org/[Fedora Magazine Page] select:
+
+. Select: "Fedora Magazine"
++ 
+This is the second item from the left in the menu bar on https://fedoramagazine.org
+. Now select the following from the pulldown menu:
++
+ Appearances > Customize
+
+. Then:
++
+ Widgets > Sidebar
+
+You are now in the "Customizing Widgets" window.
+
+Each item in this window is shown vertically as it appears in
+the right hand sidebar menu on the Fedora magazine page. This starts with
+the "Search Fedora Magazine (magnifying glass)" followed by the
+currently available Fedora Linux version, subscription option, and so on.
+
+=== Add the feature image for the new Fedora Linux version
+
+Select the currently available image and then select "Add media". The items
+in the Media library will be shown. Select the feature image for the
+new Fedora linux version announcement from the media library.
+
+There will now be two images appearing.
+
+=== Edit the HTML text
+
+Select the "Text" tab and edit the html that now appears as follows:
+
+. Remove the html <img> tag for the previous version 
+
+. Correct the text in "...available now." to reflect the new version number 
+
+. Change the "release announcement" link to point to the new release announcement.
+
+==== Text editing example
+
+In this example the changes reflect moving from Fedora 35 to 36.
+
+After adding the second image the text might appear as follows:
+
+....
+   <img class="alignnone wp-image-36451 size-medium" 
+   src="https://fedoramagazine.org/wp-content/uploads/2022/05/f36-final-300x127.jpg"
+   alt="" width="300" height="127" />
+
+   <img class="alignnone wp-image-36451 size-medium" 
+   src="https://fedoramagazine.org/wp-content/uploads/2021/10/f35-final-300x127.jpg"
+   alt="" width="300" height="127" />
+
+   <a href="https://getfedora.org/" 
+   target="_blank" rel="noopener">Fedora Linux 35 is available now</a>.
+   Read the <a href="https://fedoramagazine.org/announcing-fedora-35/">
+   release announcement</a> for all the details.
+....
+
+The <img> for f35 should be removed. The first <a> anchor text should be edited to 
+reflect the new version number (36 in this case). The link to https://getfedora.org 
+should be left as-is.
+
+The second <a> anchor should be changed to reflect the new Fedora Magazine 
+announcement URL, for version 36, in this example.
+
+The results should appear similar to the following:
+
+....
+   <img class="alignnone wp-image-36451 size-medium" 
+   src="https://fedoramagazine.org/wp-content/uploads/2022/05/f36-final-300x127.jpg"
+   alt="" width="300" height="127" />
+
+   <a href="https://getfedora.org/" 
+   target="_blank" rel="noopener">Fedora Linux 36 is available now</a>.
+   Read the <a href="https://fedoramagazine.org/announcing-fedora-36/">
+   release announcement</a> for all the details.
+....
+
+=== Commit your changes
+
+When done go to the top of the "Customizing > Widget" window and select the 
+"Publish" button.

From 4031daff773b139a56468389576bed71083d457f Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Feb 16 2023 03:43:14 +0000
Subject: [PATCH 136/148] Add a new bullet point explaining the need to add the series tag to an

artical AFTER it has been published.

---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index d845273..743f01e 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -44,3 +44,4 @@ Putting the focus keyword at the beginning of the slug will make the SEO plugin 
 == Publishing
 
 * [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise.
+* [ ] For articles that are part of a series, it is necessary to visit the post in WordPress AFTER is has been published and add the series indicator. Refer to the section *Adding an article to a series* in the xref:technical-wordpress.adoc[WordPress Operations] page for instructions.

From c2d598bbd65b4c8c1731d29a3d65fa0616e685f9 Mon Sep 17 00:00:00 2001
From: Gregory Bartholomew <gregory.lee.bartholomew@gmail.com>
Date: Sep 05 2023 18:15:12 +0000
Subject: [PATCH 137/148] Update the link to start a new Fedora Magazine project conversation


Related to: https://discussion.fedoraproject.org/t/adding-team-to-almost-all-of-the-tags-in-project-discussion/42707
Closes: https://discussion.fedoraproject.org/t/looking-for-the-discussion-related-to-fedora-libostree-post-installation-setup-modifications-and-tips-and-tricks/89053/3

---

diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index 92f7dcf..92f32c5 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -37,5 +37,5 @@ All non-article-proposal posts concerning Fedora Magazine should be tagged with 
 * Chat Room: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] (powered by https://matrix.org[Matrix])
 * Forum: https://discussion.fedoraproject.org/
 ** Click https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[here] to start a new article proposal.
-** Click https://discussion.fedoraproject.org/new-topic?category=project&tags=magazine[here] to start a new conversation about anything else related to Fedora Magazine.
+** Click https://discussion.fedoraproject.org/new-topic?category=project&tags=magazine-team[here] to start a new conversation about anything else related to Fedora Magazine.
 

From ba4aac2c1882560366be1f52df8c0e95b83138e8 Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Nov 07 2023 17:50:59 +0000
Subject: [PATCH 138/148] Corrected example text for updating the sidebar links for downloading

the new fedora linus version

---

diff --git a/modules/ROOT/pages/technical-wordpress.adoc b/modules/ROOT/pages/technical-wordpress.adoc
index 074f844..bcc26ba 100644
--- a/modules/ROOT/pages/technical-wordpress.adoc
+++ b/modules/ROOT/pages/technical-wordpress.adoc
@@ -63,7 +63,7 @@ This is located under the *Posts* section of the left-hand menu.
 
 The Fedora Magazine WordPress site contains a column on the right side of the page
 that includes several "Widgets". One of these contains the default image (often
-the background) for the latest version and links to _getfedora.org_ and the 
+the background) for the latest version and links to _fedoraproject.org_ and the 
 appropriate release announcement.
 
 The information in this widget must be changed when a new release occurs. This
@@ -125,14 +125,14 @@ After adding the second image the text might appear as follows:
    src="https://fedoramagazine.org/wp-content/uploads/2021/10/f35-final-300x127.jpg"
    alt="" width="300" height="127" />
 
-   <a href="https://getfedora.org/" 
+   <a href="https://fedoraproject.org/" 
    target="_blank" rel="noopener">Fedora Linux 35 is available now</a>.
    Read the <a href="https://fedoramagazine.org/announcing-fedora-35/">
    release announcement</a> for all the details.
 ....
 
 The <img> for f35 should be removed. The first <a> anchor text should be edited to 
-reflect the new version number (36 in this case). The link to https://getfedora.org 
+reflect the new version number (36 in this case). The link to https://fedoraproject.org 
 should be left as-is.
 
 The second <a> anchor should be changed to reflect the new Fedora Magazine 
@@ -145,7 +145,7 @@ The results should appear similar to the following:
    src="https://fedoramagazine.org/wp-content/uploads/2022/05/f36-final-300x127.jpg"
    alt="" width="300" height="127" />
 
-   <a href="https://getfedora.org/" 
+   <a href="https://fedoraproject.org/" 
    target="_blank" rel="noopener">Fedora Linux 36 is available now</a>.
    Read the <a href="https://fedoramagazine.org/announcing-fedora-36/">
    release announcement</a> for all the details.

From 38325eda597d053edc83f9c3583e5f19170f6b1c Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Mar 30 2024 00:15:51 +0000
Subject: [PATCH 139/148] Add note re: author created images using "Contributed by"


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index 743f01e..5234733 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -39,6 +39,8 @@ Putting the focus keyword at the beginning of the slug will make the SEO plugin 
 == Featured images
 
 * [ ] Make sure the article has an appropriate xref:creating-an-image.adoc[featured image].  This is **not** the same as an image in the article text itself, and should not appear there. Use the Featured Image box in the document details in WordPress.
+* [ ] Featured images should be captioned with an appropriate attribution if they are not original or make use of third party components.
+* [ ] Featured images **submitted by the author** should  be captioned using **Contributed by:** and indicate the author's name.
 * [ ] Featured images should be included or submitted to the https://pagure.io/fedoramagazine-images[featured images repo on Pagure]. Refer to the xref:creating-an-image.adoc[documentation on featured images] for more information.
 
 == Publishing

From 0ffe5420b7d0c7262c1645468dd618872b7e3533 Mon Sep 17 00:00:00 2001
From: Andreas Haerter <fedora@andreas-haerter.com>
Date: Apr 23 2024 17:53:41 +0000
Subject: [PATCH 140/148] Update modules/ROOT/pages/getting-access.adoc (fix dead link)


There is no "magazine" tag, changed to https://discussion.fedoraproject.org/tag/magazine-team (411 times used ATM and obviously the currently valid option)
---

diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc
index d236c42..dd1a13b 100644
--- a/modules/ROOT/pages/getting-access.adoc
+++ b/modules/ROOT/pages/getting-access.adoc
@@ -19,7 +19,7 @@ that the card's overall status (i.e. the column that it is in on the board) be c
 in the card's comment section. Only the editors can update the card's status/column.
 
 **4. Join the Magazine forum and introduce yourself**:
-Join the discussion on the https://discussion.fedoraproject.org/tag/magazine[Fedora Magazine Discourse forum].
+Join the discussion on the https://discussion.fedoraproject.org/tag/magazine-team[Fedora Magazine Discourse forum].
 This is where we discuss everything to do with the Fedora Magazine.
 Introduce yourself and tell us that you wish to contribute to the Fedora Magazine.
 The Fedora Magazine editors monitor this Discourse forum and will be able to help you and answer any Fedora

From e0d1d59f76bf6b9c6058e5a6c1d3154082a8aa10 Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Apr 25 2024 17:30:12 +0000
Subject: [PATCH 141/148] Modified the links to the meeting to reflect using Matrix vs IRC and the

link to the Fedora calendar

---

diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc
index 23c04c9..c4d0ba4 100644
--- a/modules/ROOT/pages/editorial-meetings.adoc
+++ b/modules/ROOT/pages/editorial-meetings.adoc
@@ -6,8 +6,8 @@ The goal of this meeting is to set and execute a publishing schedule of appropri
 
 :hash: #
 
-Meetings happen every week in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org.
-See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
+Meetings happen every week in the https://matrix.to/#/#meeting-2:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}meeting-2:fedoraproject.org] Matrix channel on chat.fedoraproject.org.
+See the https://calendar.fedoraproject.org/meeting/10800/[Fedora Magazine Editorial board meeting] in the Fedora calendar.
 Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week].
 If the meeting time changes, be sure to update the link in this paragraph.
 

From 4e9ec52244ef4c3f189cfdb0f741d6379741d8e0 Mon Sep 17 00:00:00 2001
From: Peter Mortensen <spammaygohere@pmortensen.eu>
Date: Feb 03 2025 23:53:06 +0000
Subject: [PATCH 142/148] Update modules/ROOT/pages/index.adoc


Use HTTPS for the main site.
---

diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index 92f32c5..365d28b 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -2,7 +2,7 @@
 
 include::partial$workflow-change-banner.adoc[]
 
-http://fedoramagazine.org[Fedora Magazine] is a __WordPress-based__ site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.)
+https://fedoramagazine.org[Fedora Magazine] is a __WordPress-based__ site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.)
 
 == What does the Magazine publish?
 

From bc5efcc6406f1c3f533fd915de6798d2f10c0a6a Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Mar 18 2025 02:56:19 +0000
Subject: [PATCH 143/148] Add item re: article scheduling time for beta and GA releases


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index 5234733..d8b069a 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -46,4 +46,5 @@ Putting the focus keyword at the beginning of the slug will make the SEO plugin 
 == Publishing
 
 * [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise.
+* [ ] Schedule for **Beta** and **General Availability** releases is approximatel 14:00 UTC so the article for those should be published at 14:00 UTC or a short time after that on the selected day, unless decided otherwise. Ref. https://docs.fedoraproject.org/en-US/fedora-magazine/editorial-checklist/#_featured_images[Fedora Linux Releases Life Cycle].
 * [ ] For articles that are part of a series, it is necessary to visit the post in WordPress AFTER is has been published and add the series indicator. Refer to the section *Adding an article to a series* in the xref:technical-wordpress.adoc[WordPress Operations] page for instructions.

From a7e95304f6cf4a546838d02ede4fcb600f289590 Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Mar 18 2025 17:30:31 +0000
Subject: [PATCH 144/148] Corrected typo in external link and in a single word while I was there.


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index d8b069a..1bc27b9 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -46,5 +46,5 @@ Putting the focus keyword at the beginning of the slug will make the SEO plugin 
 == Publishing
 
 * [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise.
-* [ ] Schedule for **Beta** and **General Availability** releases is approximatel 14:00 UTC so the article for those should be published at 14:00 UTC or a short time after that on the selected day, unless decided otherwise. Ref. https://docs.fedoraproject.org/en-US/fedora-magazine/editorial-checklist/#_featured_images[Fedora Linux Releases Life Cycle].
+* [ ] Schedule for **Beta** and **General Availability** releases is approximately 14:00 UTC so the article for those should be published at 14:00 UTC or a short time after that on the selected day, unless decided otherwise. Ref.https://docs.fedoraproject.org/en-US/releases/lifecycle/#_development_schedule[Fedora Linux Releases Life Cycle].
 * [ ] For articles that are part of a series, it is necessary to visit the post in WordPress AFTER is has been published and add the series indicator. Refer to the section *Adding an article to a series* in the xref:technical-wordpress.adoc[WordPress Operations] page for instructions.

From 42a36c30d3cc5c599ffb2d0c7797e0063aa2bd83 Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Mar 18 2025 18:19:49 +0000
Subject: [PATCH 145/148] Added a space that was needed before the URL and found another

typo in the next (older) section,
that I fixed, as well

---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index 1bc27b9..c145faf 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -46,5 +46,5 @@ Putting the focus keyword at the beginning of the slug will make the SEO plugin 
 == Publishing
 
 * [ ] Schedule the article to publish at 08:00 UTC (the Magazine default timezone) on the selected day, unless decided otherwise.
-* [ ] Schedule for **Beta** and **General Availability** releases is approximately 14:00 UTC so the article for those should be published at 14:00 UTC or a short time after that on the selected day, unless decided otherwise. Ref.https://docs.fedoraproject.org/en-US/releases/lifecycle/#_development_schedule[Fedora Linux Releases Life Cycle].
-* [ ] For articles that are part of a series, it is necessary to visit the post in WordPress AFTER is has been published and add the series indicator. Refer to the section *Adding an article to a series* in the xref:technical-wordpress.adoc[WordPress Operations] page for instructions.
+* [ ] Schedule for **Beta** and **General Availability** releases is approximately 14:00 UTC so the article for those should be published at 14:00 UTC or a short time after that on the selected day, unless decided otherwise. Ref. https://docs.fedoraproject.org/en-US/releases/lifecycle/#_development_schedule[Fedora Linux Releases Life Cycle].
+* [ ] For articles that are part of a series, it is necessary to visit the post in WordPress AFTER it has been published and add the series indicator. Refer to the section *Adding an article to a series* in the xref:technical-wordpress.adoc[WordPress Operations] page for instructions.

From bfd8b6a9edfe03a98e3631b780c1a9c6e7caa82d Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Nov 01 2025 16:10:58 +0000
Subject: [PATCH 146/148] Added information about articles accompanying a new release


---

diff --git a/modules/ROOT/pages/editorial-checklist.adoc b/modules/ROOT/pages/editorial-checklist.adoc
index c145faf..df8e5f0 100644
--- a/modules/ROOT/pages/editorial-checklist.adoc
+++ b/modules/ROOT/pages/editorial-checklist.adoc
@@ -9,6 +9,10 @@ This pattern is expected for things like the CommonBugs templates in the wiki.
 * [ ] Do *not* schedule the post.
 Release announcements should be published manually after confirming the website is up to date, etc.
 
+In addition to the release announcement, each new release is accompanied by articles describing new or changed features and other information. A list of these articles and proposed publication dates can be found at this site where XX is the current Fedora Linux release number:
+
+\https://fedorapeople.org/groups/schedule/f-XX/f-XX-magazine-tasks.html
+
 == Formatting
 
 * [ ] Ensure the author's first and last name appears in the preview. If not, follow the instructions xref:technical-wordpress.adoc[here].

From 8dfde19eae8492fe6756acf36055f2bc2f70ed0b Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Nov 01 2025 21:22:38 +0000
Subject: [PATCH 147/148] Remove page URL for instruction on cloning repo


---

diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc
index 3c5a046..3df2886 100644
--- a/modules/ROOT/pages/creating-an-image.adoc
+++ b/modules/ROOT/pages/creating-an-image.adoc
@@ -23,8 +23,7 @@ Install the git and inkscape packages if you don’t have them installed already
 
     $ sudo dnf install git inkscape
 
-
-Follow the instructions at xref:fedora-docs:contributing:git.adoc[Git for docs writers] for instructions on forking the https://pagure.io/fedoramagazine-images[fedoramagazine-images] repository.
+Fork the image repository at https://pagure.io/fedoramagazine-images[fedoramagazine-images] .
 
 == Creating a new image using the template
 

From 628ca2ec56f97e0558fcd19dc28507414771817b Mon Sep 17 00:00:00 2001
From: Richard England <rlengland@gmail.com>
Date: Jan 22 2026 22:58:16 +0000
Subject: [PATCH 148/148] Added note regarding need to conform to the  Fedora AI-Assisted Contributions Policy


---

diff --git a/modules/ROOT/pages/writing-a-pitch.adoc b/modules/ROOT/pages/writing-a-pitch.adoc
index c918543..5cf5e55 100644
--- a/modules/ROOT/pages/writing-a-pitch.adoc
+++ b/modules/ROOT/pages/writing-a-pitch.adoc
@@ -7,3 +7,5 @@ Fedora Magazine welcomes anyone to submit ideas for articles.
 Just propose your idea on our https://discussion.fedoraproject.org/new-topic?category=workflows/magazine[Fedora Magazine Discourse forum].
 
 See the xref:workflow-article-proposal.adoc[Editorial Workflow - Article Proposal] page for more information.
+
+**Please Note:** All contributors are asked to conform to the https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/[Fedora AI-Assisted Contributions Policy]