Currently if you produce a 404 (e.g. by going to https://www.osbuild.org/guides/developer-guide/404.html) you get an unstyled version of the page.

Managing repositories - OSBuild guides doesn't provide the documentation on adding a copr repo as 3rd part repo and neither does man composer-cli-sources,

Btw if I composer-cli sources add a TOML as follows,

id="kexec-tools-crashkernel"
name="kexec-tools-crashkernel"
url="https://download.copr.fedorainfracloud.org/results/coiby/kexec-tools-crashkernel/fedora-34-x86_64"
type="yum-baseurl"
check_gpg = false
check_ssl = false
system = false

Running composer-cli compose start crashkernel qcow2 gives the following error,

ERROR: DepsolveError: DNF error occured: RepoError: Error occurred when setting up repo: Failed to download metadata for repo '4': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Let's add a section that describes how, how long, and what guarantees are given for osbuild stages and experimental stages.

It could explain terms that are used across our organization or it could point to the right place containing explanation:

• manifest
• blueprint
• pipeline
• upload target
• etc

Missing sections:

• building containes, importing into podman, using them
• building installers, their usage

@achilleas-k or @gicmo would you like to write it?

Excuse me, I want to build remote worker, have som guide? I ref this, but I dont see composer side listen port 8700, so I need a guide. Thanks.

To enable better reviewing of PRs that refactor or restructure the guides (e.g. #86) it would be nice to add a step to our GitHub Actions workflow to provide the results of the build that happens anyway to the reviewer.

This is possible through the native archiving step (see https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts).
One limitation is that the archive is not available until after the workflow is done so you cannot easily post a comment with a link to the archive to the pull request.

https://www.osbuild.org/guides/user-guide/managing-repositories.html

focuses mostly on overrides

expand the guide to cover additional repos as well (composer-cli sources)

The valid values for the types of repositories aren't mentioned anywhere.
We should probably list them on the managing-repositories page (yum-baseurl, yum-metalink, yum-mirrorlist).

The section is only about repository overrides and leaves out important details like:

• It is not supposed to be used to specify custom repos (that's where composer-cli sources is supposed to be used)

This should be fixed by:

• stressing the fact that this is only for "overrides"
• Writing a new section on 3rd party repos: #23

I have a few comments to the section:

1. While the osbuild-composer does not inherit the system repositories, it comes with a few predefined repositories of its own in /usr/share/osbuild-composer. I think that it would make sense to mention it. Also it may make sense to mention, that /etc/osbuild-composer directory has a precedence over the one in /usr/share/ and can effectively override the default one shipped with osbuild-composer (since the list of paths is traversed in a specific order and the first found file is used).

2. The sentence Then, create a JSON file with the following structure should be more specific, since it is mandatory for the JSON file to me named <distro>.json, e.g. fedora-32.json.