That's a good point, I think I agree. Let me think about that for a while.
Other people's ideas/opinions welcome!
On Tue, Aug 21, 2018 at 2:52 PM Sanja Bonic <sanja(a)redhat.com> wrote:
Putting it under Technical Teams would mean it is three clicks away from
the original documentation (Engineering -> Technical Teams -> x). That
diminishes the value of having it integrated into the Fedora documentation
since there is no search bar on top where people would find things if they
searched for it, it'd be a "have to know it to find it" thing.
Silverblue, CoreOS, Containers are important parts of how Fedora can
position itself as not just the distribution it is known for, but also for
the value its container-based development options bring to developers.
These three sections should be incorporated onto the main site of the
Fedora documentation. There are two options I can think of to achieve that:
1. Either as boxes under "Fedora Project & Community" or
2. the whole "Engineering" part under "Fedora Project &
be taken out, made its own point and Modularity is then its own section box
just like Silverblue, CoreOS, and Containers.
Otherwise the content is hidden away. Let me know whether you think one of
the options is feasible or whether you have other ideas. Thanks for your
On Tue, Aug 21, 2018 at 9:13 AM, Adam Samalik <asamalik(a)redhat.com> wrote:
> Hey Sanja,
> Great to see this!
> I've just tried a local build of all three and it worked fine for me
> (using "./build.sh && ./preview.sh"). Let me know if I can be of
> About the next step, let me know when you're ready and I'll add them to
> the Fedora Docs. I think the best way to integrate them would be to link
> them from the "Technical Teams" section . All three repos then get
> own space, the same way as Modularity  has. Would that work for you?
>  https://docs.fedoraproject.org/en-US/fesco/teams/
>  https://docs.fedoraproject.org/en-US/modularity/
> On Mon, Aug 20, 2018 at 10:55 PM Sanja Bonic <sanja(a)redhat.com> wrote:
>> Hi everyone,
>> The docs repositories for CoreOS, Silverblue, and container tooling are
>> now set up (links below). I used the template repository that Adam linked
>> in a previous email. Thanks for that! More content will be added this week.
>> This was just an initial commit.
>> The local building didn't work because of errors that I'll verify
>> another time (with regards to whether it's because of the code or my
>> current system).
>> How do we go about integrating them as sections in the current Fedora
>> documentation? The goal is to publish some of the current really good
>> documentation we have (like Chris Negus' Kubernetes on Fedora guide,
>> container guide in general, etc.), and to be able to tell people where to
>> go in order to get informed. With the integration into Fedora docs we now
>> don't have to worry about infrastructure and formatting anymore, which is
>> really nice.
>> docs mailing list -- docs(a)lists.fedoraproject.org
>> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
> Adam Šamalík
> Software Engineer
> Red Hat
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
docs mailing list -- docs(a)lists.fedoraproject.org
To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines