Added meta data to a bunch of articles, moved various partials to article, fixed various issues.

modules/ROOT/nav.adoc

@@ -112,7 +112,7 @@
 * Databases
 ** xref:postgresql.adoc[PostgreSQL]
 ** xref:installing-mysql-mariadb.adoc[Installing, Configuring and Troubleshooting MySQL/MariaDB]
-** xref:manage-sql-server.adoc[How to Manage your SQL Server from GUI]
+** xref:manage-database-servers-from-gui.adoc[How to Manage Various Database Servers from GUI]
 
 * Printing and scanning
 ** xref:how-to-debug-printing-problems.adoc[Troubleshooting printing issues]

modules/ROOT/pages/adding-or-removing-software-repositories-in-fedora.adoc

@@ -1,5 +1,14 @@
 = Adding or removing software repositories in Fedora
+Anthony McGlone
+:revnumber: F37
+:revdate: 2023-01-05
+:category: Administration
+:tags: How-to DNF Application Software-Installation  
+//:page-aliases: 
 
+include::partial$attributes.adoc[]
+
+[abstract]
 This section describes how to add, enable, or disable a software repository with the DNF application.
 
 == Adding repositories

modules/ROOT/pages/creating-and-using-a-live-installation-image.adoc

@@ -1,10 +1,14 @@
 = Creating and using a live installation image
+Chase Lau ; The Fedora Docs Team
+:revnumber: unknown
+:revdate: 2019-10-05
+:category: Installation
+:tags: How-to Workstation  
+//:page-aliases: 
 
-// include::{partialsdir}/proc_downloading-fedora.adoc[leveloffset=+1]
+include::partial$attributes.adoc[]
 
-//[id='downloading-fedora']
 == Downloading Fedora
-//include::{partialsdir}/attributes.adoc[]
 
 You can download Fedora from https://getfedora.org/.
 

modules/ROOT/pages/howto-file-a-bug.adoc

@@ -1,11 +1,20 @@
 = How to file a bug
-:imagesdir: ./images
-include::partial$attributes.adoc[]
-:toc:
+Ankur Sinha; Joe Walker
+:revnumber: all
+:revdate: 2023-05-15
+:category: Bugs
+:tags: How-to Bug-Report 
+//:imagesdir: ./images
 
+include::partial$attributes.adoc[]
+
+
+[abstract]
 The purpose of this document is to give step by step instructions on filing bugs in Fedora.
 For more information about using Bugzilla,
-see the xref:bugzilla.adoc[Bugs section] of the Quick Docs.
+see the xref:bugzilla/index.adoc[Bugs section] of the Quick Docs.
+
+
 
 A software bug does not necessarily need to be a software crash.
 Any undesired behaviour in software can be filed as a bug.

modules/ROOT/pages/installing-plugins-for-playing-movies-and-music.adoc

@@ -10,12 +10,12 @@ As a Fedora user and system administrator, you can use these steps to install ad
 
 WARNING: If you live in a country where software patents apply, such as in the United States or in Japan, you need to obtain multimedia codecs from a source that legally distributes patented software in your country. For example, see the Fluendo Codec Pack: link:https://fluendo.com/en/products/enterprise/fluendo-codec-pack/[].
 
-[discrete]
+
 == Prerequisites
 
 * xref:setup_rpmfusion.adoc[Enable the RPMFusion repositories].
 
-[discrete]
+
 == Procedure
 
 * Use the `dnf` utility to install packages that provide multimedia libraries:
@@ -28,7 +28,6 @@ sudo dnf install lame\* --exclude=lame-devel
 sudo dnf group upgrade --with-optional Multimedia
 ----
 
-[id='related-information-{context}']
 == Related information
 
 * There are also media players that include all relevant codecs by themselves. Consider using one of the following for offline video viewing:
@@ -36,7 +35,4 @@ sudo dnf group upgrade --with-optional Multimedia
 ** MPV, available from the `mpv` package in RPM Fusion Free
 
 
-// The following line is necessary to allow assemblies be included in other
-// assemblies. It restores the `context` variable to its previous state.
-ifdef::parent-context[:context: {parent-context}]
-ifndef::parent-context[:!context:]
+

modules/ROOT/pages/installing-skype.adoc

@@ -1,6 +1,14 @@
 = Installing Skype on Fedora
+alciregi; Man2Dev ; The Fedora Docs Team
+:revnumber: F38
+:revdate: 2023-07-06
+:category: Applications
+:tags: How-to 
+
+
+// include::{partialsdir}/3rdparty-message.adoc[]
+include::partial$3rdparty-message.adoc[]
 
-include::{partialsdir}/3rdparty-message.adoc[]
 
 link:https://www.skype.com/[Skype] is a cross-platform proprietary chat (text and video) application.
 

modules/ROOT/pages/installing-spotify.adoc

@@ -1,14 +1,15 @@
 = Installing Spotify on Fedora
-The Fedora Documentation Team
+Ankur Sinha; Weverton do Couto Timoteo; Mohammadreza Hendiani
 :revnumber: F38
-:revdate: 2023-08-04
-
-// Optional  free form useful additional information as comment
-
+:revdate: 2023-07-04
 :category: Installation
 :tags: How-to Flatpak DNF RPMFusion Spotify
 
-include::{partialsdir}/3rdparty-message.adoc[]
+// Optional  free form useful additional information as comment
+
+//include::{partialsdir}/3rdparty-message.adoc[]
+include::partial$3rdparty-message.adoc[]
+
 
 link:https://www.spotify.com/[Spotify] is a cross-platform proprietary music streaming service.
 Spotify is a freemium service, with advertisements which can be removed by purchasing a subscription.

modules/ROOT/pages/join-active-directory-freeipa.adoc

@@ -1,4 +1,12 @@
 = Joining an Active Directory or FreeIPA domain
+Oliver Gutierrez
+:revnumber: F38
+:revdate: 2021-07-04
+:category: Administration
+:tags: How-to Network-Management Active-Directory FreeIPA
+
+// Optional  free form useful additional information as comment
+
 
 Fedora can join Active Directory and FreeIPA domains using the `realm` command.
 
@@ -12,26 +20,26 @@ If you want your Fedora machine to be part of an Active directory or FreeIPA dom
 
 . Configure the DNS to use the Active Directory or FreeIPA domain DNS servers (if your network uses DHCP to set this DNS to the correct server, skip this step)
     You can do this editing the network settings using the GNOME configuration panel or you can edit directly the file `/etc/systemd/resolved.conf` and add your DNS manually.
-
++
 ....
     [Resolve]
     DNS=192.168.122.143 172.17.0.2 1.0.0.1
 ....
 
 . After saving the file, restart `systemd-resolved` service.
-
++
 ....
     $ sudo systemctl restart systemd-resolved
 ....
 
 . Change the machine name to the machine name you want + the domain name.
-
++
 ....
     $ sudo hostnamectl set-hostname my_machine.example.domain
 ....
 
 . Use the `realm` command to join the machine to the domain.
-
++
 ....
     $ sudo realm join example.domain -v
 ....

modules/ROOT/pages/manage-database-servers-from-gui.adoc

@@ -1,4 +1,12 @@
-== How to Manage SQL SERVER from GUI
+= How to Manage Various Database Server from GUI
+Héctor Louzao; Rafael Fontenelle
+:revnumber: F38
+:revdate: 2023-01-04
+:category: Databases
+:tags: How-to Database-Administration
+
+// Optional  free form useful additional information as comment
+
 
 For database management, it is more user-friendly to use graphical tools:
 
@@ -52,8 +60,8 @@ sudo dnf install phpPgAdmin
 
 for Fedora >= 33
 
-[[installation]]
-=== Installation
+
+== Installation
 
 The installation of the postgresql GUI web-server is a little bit different
 in comparison to older Fedora because the package is out of the repo.

modules/ROOT/pages/openh264.adoc

@@ -1,12 +1,17 @@
 = OpenH264
+Caleb McKee
+:revnumber: unknown
+:revdate: 2021-06-04
+:category: Applications
+:tags: How-to Multimedia 
 
-
+[abstract]
 This page contains information on the Cisco 
 https://www.openh264.org/[OpenH264] codec.
 
-[[background]]
-Background
-----------
+
+== Background
+
 
 Cisco provides an OpenH264 codec (as a source and a binary), which is
 their of implementation H.264 codec, and they cover all licensing fees
@@ -22,9 +27,7 @@ Upstream Firefox versions download and install the OpenH264 plugin by
 default automatically. Due to it's binary nature, Fedora disables this
 automatic download.
 
-[[installation-from-fedora-cisco-openh264-repository]]
-Installation from fedora-cisco-openh264 repository
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+== Installation from fedora-cisco-openh264 repository
 
 A `fedora-cisco-openh264` repository is distributed since Fedora 24 by
 default (if you have at least `fedora-repos-24-0.5` package or newer).
@@ -51,9 +54,7 @@ You can do a simple test whether your H.264 works in RTC on
 https://mozilla.github.io/webrtc-landing/pc_test.html[this page] (check
 _Require H.264 video_).
 
-[[manual-install-of-binary]]
-Manual install of binary
-~~~~~~~~~~~~~~~~~~~~~~~~
+== Manual install of binary
 
 * View and agree to the https://www.openh264.org/BINARY_LICENSE.txt
 * Download the appropriate binary for your system here:
@@ -68,12 +69,9 @@ cd ~/.mozilla/firefox/<yourprofile>/gmp-gmpopenh264/1.1/ +
 unzip ~/openh264-linux64-v1.1-Firefox33.zip
 ....
 
-[[firefox-config-changes]]
-Firefox config changes
-^^^^^^^^^^^^^^^^^^^^^^
+== Firefox config changes
 
-Type about:config into the Firefox address/URL field and accept the
-warning.
+Type about:config into the Firefox address/URL field and accept the warning.
 
 * From the Search field type in 264 and a handful of options will
   appear. Give the following Preference Names a value of true by

modules/ROOT/pages/performing-administration-tasks-using-sudo.adoc

@@ -1,21 +1,111 @@
-ifdef::context[:parent-context: {context}]
-:context: performing-administration-tasks-using-sudo
-[id='performing-administration-tasks-using-sudo']
 = Performing administration tasks using sudo
+Harsh Jain; Peter Boy 
+:revnumber: unknown
+:revdate: 2023-08-08
+:category: Administration
+:tags: How-to root-privilegies  
+//:page-aliases: 
 
+//include::partial$attributes.adoc[]
+
+
+[abstract]
 How to perform tasks requiring *root* privileges without logging in as *root*.
 
-include::{partialsdir}/con_what-is-sudo.adoc[leveloffset=+1]
+== What is sudo?
+
+The [command]`sudo` command allows users to gain administrative or root access. When trusted users precede an administrative command with [command]`sudo`, they are prompted for their own password. Then, when they have been authenticated and assuming that the command is permitted, the administrative command is executed as if they were the root user.
+
+Only users listed in the [filename]`/etc/sudoers` configuration file are allowed to use the [command]`sudo` command. The command is executed in the user's shell, not a root shell.
+
+The syntax for the sudo command is as follows:
+
+[subs=quotes]
+----
+sudo _COMMAND_
+----
+
+Replace `_COMMAND_` with the command to run as the root user.
+
+
 
 
 [id='how-to-use-sudo']
 == How to use sudo
 
-include::{partialsdir}/con_using-sudo-assign-admin-privileges.adoc[leveloffset=+2]
+=== Using sudo to assign administrator privileges
 
-include::{partialsdir}/proc_using-same-password-for-root-as-user.adoc[leveloffset=+2]
+Add users to the [directory]`/etc/sudoers` configuration file to allow them to use the [command]`sudo` command. For these users, the [command]`sudo` command is run in the user’s shell instead of in a root shell. As a result, the root shell can be disabled for increased security.
 
-include::{partialsdir}/con_logging-sudo-commands.adoc[leveloffset=+2]
+The administrator can also allow different users access to specific commands using the sudo configuration. Administrators must use the [command]`visudo` command to edit the [directory]`/etc/sudoers` configuration file. 
+
+To assign full administrative privileges to a user, type [command]`visudo` and add the following line to the user privilege section after replacing `_USERNAME_` with the target user name:
+
+[subs=quotes]
+----
+_USERNAME_ ALL=(ALL) ALL
+----
+
+This line allows the specified user to use [command]`sudo` from any host and execute any command.
+
+To allow a user access to specific commands, use the following example after replacing `_USERS_` with a target system group:
+
+[subs=quotes]
+----
+_%USERS_ localhost=/usr/sbin/shutdown -h now
+----
+
+This command allows all members of the `_USERS_` system group to issue the [command]`/sbin/shutdown -h` as long as the command is issued from the console.
+
+The man page for [command]`sudoers` has a detailed listing of options for this file.
+
+
+=== Using the same password for root as the user account
+
+If you use a single user desktop, you might find it convenient to configure [command]`sudo`, so you can use the same password to access *root* as you use for your regular account. To do this, select to be added to the Administration group during installation. To do it at later stage, or to add a different user, use the following procedure:
+
+. Become the *root* user:
++
+----
+$ su -
+----
++
+. Enter the password for the root account when prompted.
+
+. To use your regular password for the root access, run:
++
+[subs=quotes]
+----
+# usermod _USERNAME_ -a -G groupname
+----
++
+Replace `_USERNAME_` with your account name
+
+. Log off and back on in order to have access to the group. 
+
+NOTE: When [command]`sudo` prompts you for a password, it expects your user password, not the `root` password.
+
+
+=== Logging sudo commands
+
+Each successful authentication using the [command]`sudo` command is logged to the [filename]`/var/log/messages` file. For each authentication, the [filename]`/var/log/secure` file lists the user name and the command that was executed.
+
+For additional logging, use the `pam_tty_audit` module to enable TTY auditing for specific users. TTY auditing prints the file name of the terminal connected to the standard I/O. To enable TTY auditing, add the following line to your [filename]`/etc/pam.d/system-auth` file:
+
+[subs=quotes]
+----
+session required pam_tty_audit.so disable=pattern enable=_PATTERN_
+----
+
+Replace `_PATTERN_` with a comma-separated list of users (and globs, if needed).
+
+For example, the following command enables TTY auditing for the root user and disables it for all other users:
+
+----
+session required pam_tty_audit.so disable=* enable=root
+----
+
+Using the `pam_tty_audit` PAM module for auditing only records TTY input. As a result, when the audited user logs in, `pam_tty_audit` records the user’s exact keystrokes and saves them in [filename]`/var/log/audit/audit.log`. For more information, see the *pam_tty_audit(8)* manual page.
 
 
 [[warning-and-caveats]]
@@ -25,12 +115,55 @@ You must use the user account you created following the installation process, at
 
 There are several potential risks to keep in mind when using the [command]`sudo` command. You can avoid them by editing the [filename]`/etc/sudoers` configuration file using [command]`visudo` command.
 
-include::{partialsdir}/con_sudo-timeout.adoc[leveloffset=+2]
 
-include::{partialsdir}/con_using-sudo-access-docker.adoc[leveloffset=+2]
+=== sudo timeout
+
+By default, [command]`sudo` stores the password for a five minute timeout period. Any subsequent uses of the command during this period will not prompt you for a password. This could be exploited by an attacker if you leave your workstation unattended and unlocked while still being logged in. You can change this behavior by adding the following line to the `/etc/sudoers` configuration file:
+
+[subs=quotes]
+------------
+Defaults    timestamp_timeout=_VALUE_
+------------
+
+Here, `_VALUE_` is the desired timeout length in minutes. Setting the value to 0 causes [command]`sudo` to require a password every time. 
+
+If an account is compromised, an attacker can use [command]`sudo` to open a new shell with administrative privileges. 
+
+Opening a new shell as a root user in this way allows an attacker administrative access for a theoretically unlimited period of time and bypasses the timeout period specified in the `/etc/sudoers` file. Using this method, the attacker *does not* need to provide a password for [command]`sudo` again until the session ends.
+
+
+=== Using sudo to access Docker
+
+Docker has the ability to change the group ownership of the Docker socket to allow users added to the Docker group to be able to run Docker containers without having to execute the [command]`sudo` or [command]`su` command to become root.
+
+Enabling access to the Docker daemon from non-root users is a problem from a security perspective. It is a security issue for Fedora, because if a user can talk to the Docker socket they can execute a command which gives them full root access to the host system. Docker has no auditing or logging built in, while [command]`sudo` does.
+
+It is recommended that sudo rules are implemented to permit access to the Docker daemon. This allows [command]`sudo` to provide logging and audit functionality.
+
+
+=== Run Docker using sudo
+
+. Set up [command]`sudo` as shown in xref:performing-administration-tasks-using-sudo.adoc#_using_sudo_assign_admin_privileges[Using sudo to assign administrator privileges].
+. Create an alias for running the docker command by adding the following line to your `~/.bashrc` file:
++
+----
+alias docker="sudo /usr/bin/docker"
+----
++
+When the user executes the docker command as non-root, sudo will be used to manage access and provide logging.
+
+
+=== Using sudo without a password
+
+You can enable `root` access without a password specified, allowing any process on your system to become `root`. Add the following line to your `/etc/sudoers` file:
+
+[subs=quotes]
+------------
+_user_        ALL=(ALL)       NOPASSWD: /usr/bin/docker
+------------
+
+This will allow `_user_` to access docker without a password. 
+
+IMPORTANT: For security reasons, it is recommended that you always use [command]`sudo` with a password. 
 
-include::{partialsdir}/proc_run-docker-using-sudo.adoc[leveloffset=+2]
 
-include::{partialsdir}/con_using-sudo-without-password.adoc[leveloffset=+2]
-ifdef::parent-context[:context: {parent-context}]
-ifndef::parent-context[:!context:]