#22 RFE overview or apprach for docs site
Closed by pbrobinson. Opened by langdon.

Reading (quickly) through the docs, I feel like it gets too detailed too quickly. I think the content is missing the answers to the "why" and/or the "grand plan."

In other words, an overview of the edition and what it is including things like a) it is an ostree image; b) apps are provided via container; c) what solutions does the edition strive for (e.g. desktop? web server? iot gateway?).

I would also like to know "what is the X year plan." For example, "we are currently focused on making the a-board, b-board and c-board actually provide the [web-server] solution. Next we will take on more boards (or maybe it is more solutions?)." I would also indicate how malleable this is. For example, im a guy who really likes k-boards and fedora and wants to make that board work, can I expect "support" doing that? same for solutions.


So can you provide an example around the Edition wording, I don't see that in some of the other docs.fp.o and it mostly seems to target technical docs which is what I'm aimed for at the moment. Similarly with X year plans. The two projects I base a bunch of the IoT bits on, modularity and silverblue don's appear, at least at a quick glance, have multi year plans etc documented.

In the case of supported boards, that's an interesting one. How do you define "supported"? Supported by the vendor that makes the device? Supported by the IoT team? Supported by the Arm team? Community supported? At the moment we're using the term reference platforms for a reason. We're working with some vendors to have them actively support their devices at which point they can be classed as a reference platform. At the other end of the scale we will quite happily work with the community to assist them in supporting devices. Feedback welcome on suggestions for this but the term "support" is very overloaded.

We've addressed some of this, docs are now on github https://github.com/fedora-iot/iot-docs

Metadata Update from @pbrobinson:
- Issue status updated to: Closed (was: Open)

Metadata