←back to thread

Red Hat Technical Writing Style Guide

(stylepedia.net)
199 points jumpocelot | 2 comments | 10 Jul 25 15:01 UTC | HN request time: 0.579s | source
Show context
ban2ly ◴[10 Jul 25 17:12 UTC] No.44523176[source]▶
Seems useless, as Red Hat does not write documentation
replies(1): >>44523221 #
curt15 ◴[10 Jul 25 17:17 UTC] No.44523221[source]▶
Red Hat has some of the most professional documentation of any distro. E.g https://docs.redhat.com/en/documentation/red_hat_enterprise_...
replies(2): >>44523685 #>>44524291 #
bauruine ◴[10 Jul 25 17:56 UTC] No.44523685[source]▶
Much of it is behind a paywall though. I manage more than a hundred licenced RHEL machines, was an RHCSA and RHCE with a company mail but I'd have to ask someone in my org to give me access. I just blocked access.redhat.com on kagi. F you.
replies(2): >>44523875 #>>44523996 #
worthless-trash ◴[10 Jul 25 18:12 UTC] No.44523875[source]▶
Most of the 'docs' are not behind the paywall, you're mixing up the KCS / FAQ's.

The docs are on https://docs.redhat.com/

replies(1): >>44524094 #
1. bauruine ◴[10 Jul 25 18:35 UTC] No.44524094[source]▶
I didn't mix it up but most of the time I stumble upon redhat.com it's KCS (access.redhat.com) articles. Yes it's not "documentation" but if it's worth to create an article because that many people have the same issue I'd say you could add it to your documentation as known issues.
replies(1): >>44528662 #
2. worthless-trash ◴[11 Jul 25 05:28 UTC] No.44528662[source]▶
I dont think that google is indexing that without a login/subscription though. TIL.