rocky-linux / rocky-linux/documentation

Documentation for built-in system admin tools for new Desktop category

Open
#2,020 3 comments 0 reactions 1 assignee View on GitHub

@techstacksavvy is already working on this.

Since Apr 18, 2024.

Dominant language
Shell
Stars
476
Forks
383
Avg merge
1d 14h
Merged PRs (30d)
20

Description

Would be nice to populate the new Desktop focused category of docs at docs.r.o with Guides/Tips for using built-in (and 3rd party) GUI tools for completing Sys. Admin tasks.

As an example, the rough requirements draft for a Guide/doc covering user/group management on RL systems using a built-in GUI tool might include the following:

  • Show how to create/manage new users/groups on a RL workstation using ONLY GUI tools

  • Whenever possible, the guide should cover (expose?) as many of the important salient points/features covered by the CLI counter-parts tools (e.g useradd) and also exposed in the GUI.

  • 1st guide might cover using built-in tools like "gnome control center". Ditto something similar for KDE DE env.

  • Subsequent or future guides can cover other popular 3rd party tools for doing similar things

  • Guides should feature 1 - 3 screenshots of the most important aspect of the tool/process (e.g. attached screenshot)

  • Include extra tips for using or launching the tool from the CLI e.g. gnome-control-center user-accounts

  • Some of the initial set of built-in and out-of-the-box GUI Rocky system management tools that we can create documentation for are shown in this output :

$ gnome-control-center  -l

Available panels:
	applications
	background
	bluetooth
	camera
	color
	datetime
	default-apps
	diagnostics
	display
	info-overview
	keyboard
	location
	lock
	microphone
	mouse
	multitasking
	network
	wifi
	notifications
	online-accounts
	power
	printers
	region
	removable-media
	search
	sharing
	sound
	thunderbolt
	universal-access
	usage
	user-accounts
	wacom
	wwan
gnome-control-center - 1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.