Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should we drop 'Content hosts'? #2795

Open
jeremylenz opened this issue Feb 15, 2024 · 3 comments
Open

should we drop 'Content hosts'? #2795

jeremylenz opened this issue Feb 15, 2024 · 3 comments

Comments

@jeremylenz
Copy link
Contributor

A "content host" is simply a host that has been registered with subscription-manager.

With the Content Hosts legacy web UI going away soon and the combination of the Content Hosts and All Hosts into a single All Hosts page, we've been moving toward just using the term "hosts" rather than "content hosts." Should we remove "content hosts" from our documentation everywhere and make "hosts" the new standard? I think this may be a bit less confusing and more consistent.

@ekohl
Copy link
Member

ekohl commented Feb 16, 2024

Host and (if needed specifically) host with content sounds like a good idea to me.

@maximiliankolb
Copy link
Contributor

If Foreman Web UI drops the term/page "content hosts", docs will obviously follow, yes.

@Lennonka
Copy link
Contributor

Yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants