Merge branch 'master' into 'master'

Draft: Update index.asciidoc with formatting and new TOC; add base CSS template for further editing

See merge request pacman/pacman!191

doc/index.asciidoc

@@ -1,10 +1,12 @@
 Pacman Home Page
 ================
+:stylesheet: index.css
+:toc:
 
 A simple library-based package manager.
 
-Introduction
-------------
+== Introduction
+
 pacman is a utility which manages software packages in Linux. It uses simple
 compressed files as a package format, and maintains a text-based package
 database (more of a hierarchy), just in case some hand tweaking is necessary.
@@ -14,12 +16,12 @@ packages in the system, and it will allow you to query the package database for
 installed packages, files and owners. It also attempts to handle dependencies
 automatically and can download packages from a remote server.
 
-History
-~~~~~~~
-Version 2.0 of pacman introduced the ability to sync packages (the '\--sync'
+== History
+
+Version 2.0 of pacman introduced the ability to sync packages (the '--sync'
 option) with a master server through the use of package databases. Prior to
-this, packages would have to be installed manually using the '\--add' and
-'\--upgrade' operations.
+this, packages would have to be installed manually using the '--add' and
+'--upgrade' operations.
 
 Version 3.0 was the switch to a two-part pacman -- a back-end named libalpm
 (library for Arch Linux Package Management) and the familiar pacman front-end.
@@ -36,11 +38,10 @@ list operations.
 
 Version 6.0 added support for parallel downloads.
 
-Documentation
--------------
+== Documentation
+
+=== Man Pages
 
-Man Pages
-~~~~~~~~~
 There are several man pages available for the programs, utilities, and
 configuration files dealing with pacman.
 
@@ -58,8 +59,8 @@ configuration files dealing with pacman.
 * linkman:repo-add[8]
 * linkman:vercmp[8]
 
-Changelog
-~~~~~~~~~
+=== Changelog
+
 For a good idea of what is going on in pacman development, take a look at the
 link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the
 project.
@@ -69,10 +70,7 @@ link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS]
 file for a not-as-frequently-updated list of changes. However, this should
 contain the biggest changes in a format more concise than the commit log.
 
-
-Releases
---------
-
+== Releases
 [frame="none",grid="none",options="autowidth",cols="3*a"]
 |======
 |
@@ -195,6 +193,7 @@ Releases
 
 |======
 
+
 Source code for releases since moving to gitlab is available at
 link:https://gitlab.archlinux.org/pacman/pacman/-/releases[].
 Source code for historical releases is available at
@@ -209,17 +208,16 @@ commands:
 You may wish to read the options presented by `meson` in order to
 set appropriate paths and build options that are correct for your system.
 
-Development
------------
+== Development
+
+=== Mailing List
 
-Mailing List
-~~~~~~~~~~~~
 There is a mailing list devoted to pacman development, hosted by Arch Linux.
 link:https://lists.archlinux.org/listinfo/pacman-dev/[Subscribe] or
 link:https://lists.archlinux.org/pipermail/pacman-dev/[view the archives].
 
-Source Code
-~~~~~~~~~~~
+=== Source Code
+
 Development of pacman is currently done in Git. The central repository is
 hosted by Arch Linux, although some of the developers have their own trees (ask
 on the above mailing lists if you are interested in finding the locations of
@@ -243,15 +241,15 @@ you speak a foreign language, you can help by either creating or updating a
 translation file for your native language. Instructions can be found in
 link:translation-help.html[translation-help].
 
-Bugs
-----
+== Bugs
+
 If you find bugs (which is quite likely), please report them to the issue
 tracker at link:https://gitlab.archlinux.org/pacman/pacman/-/issues[] with
 specific information such as your command-line, the nature of the bug, and even
 the package database if it helps.
 
-Copyright
----------
+== Copyright
+
 pacman is Copyright (C) 2006-2024 Pacman Development Team
 <pacman-dev@lists.archlinux.org> and Copyright (C) 2002-2006 Judd Vinet
 <jvinet@zeroflux.org> and is licensed through the GNU General Public License,