Customer Problem:

As a Quay user, it is hard to figure out all the configuration options.

Goal: Document Quay configuration so that it is accurate, complete and usable

Problem:

• current focus on UI rather than automation
• config is spread out over multiple docs
• need to make config docs more usable - currently listed alphabetically, not by feature/priority
• minimal, one-liners for lots of config options, with no details on real world use
• lots of obsolete options need to be removed

Why is this important: 

• Current docs make it hard for Quay users to understand config, especially new users

Dependencies (internal and external):

• none

Prioritized epics + deliverables (in scope / not in scope):

• basic structure and introduction for guide
• direct editing of config.yaml
• using the configuration API
• using the config UI tool
• document minimal config for quick start
• complete documentation for all current options
• determine and remove obsolete/irrelevant op

Estimate (XS, S, M, L, XL, XXL):  XXL

Previous Work: 

Open questions