Checklist

• I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
• I performed a search in the issue tracker for similar issues, using keywords relevant to my problem.

The speed comparison in your website and the README file are completely outdated. It would be a good idea considering Rufus had major changes since

I want to document all the distros added by @ZeTriUm. But since they are quit a few it still in progress:

• #187 GeckoLinux
• #186 ArchLabs
• #185 Maui Linux
• #184 ArchStrike
• #183 Runtu
• #182 Chakra GNU/Linux
• #181 RoboLinux
• #180 Scientific Linux
• #179 Calculate Linux
• #178 SolydXK
• #177 OSGeo-Live
• #176 Siduction
• [ ]

When you launch Fedora Media Writer, it looks like this:

My feeling is that the list is missing a bit of context. What is it? What's happening here?

It would be good to add some information which explains how the media writer works and what the list is for. For example:

"Create

Several customers request following functionality:

Automatically update of the „Metadata Date" Field with the current date at every save. The behaviour, if it updates automatically or not, can be configured e.g. at gpt.xml.
Nice to have: The user can set the behaviour in the client UI for the edit session which overules the in the gpt.xml configured default behaviour.
![metadata_date_ui](http

It should not output anything except the image path when no error happen by default. You can introduce a verbose flag for the current output.

Then we can pipe the output (image path) to something else and build some workflow.

(it's also a problem with nixos-rebuild and other official tools and should be fixed upstream if possible)

When we search for files to render, we should recursively check the given directory. Currently we only search the given directory.

docs/
  components/
    a.md
    b.md
  overview/
    installation.md

The XSLT engine moved from built-in JAXP to Saxon with #999

Currently I'm not sure if there's any formal documentation on how exactly elementary measures and performs their release process.

I am aware that active development is synced with Ubuntu LTS releases, but other than that my awareness is formed completely from external observation.

Currently we have build instructions for macOS / Linux users but point Windows users to the AppVeyor builds.

This is great for the more common user, but if one is interested in developing/improving extract-iso it can be helpful to have build instructions.