Re: [libvirt] [PATCH 12/17] docs: expand downloads page to cover all modules

Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com&gt; --- docs/downloads.html.in | 391 +++++++++++++++++++++++++++++++++++++++---------- docs/libvirt.css | 13 +- 2 files changed, 322 insertions(+), 82 deletions(-) diff --git a/docs/downloads.html.in b/docs/downloads.html.in index 1a3400a..374ccb0 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in

+ <table class="top_table downloads"> + <thead> + <tr> + <th>Module</th> + <th>Releases</th> + <th>GIT Repos</th>

+ </tr> + </thead> +

+ <h2>Primary download site</h2> + + <p> + Most modules have releases made available for download on the project + site, via FTP, HTTP or HTTPS. Some modules are instead made available + at alternative locations, for example, the Perl binding is made + available only on CPAN. </p> <ul> <li><a href="ftp://libvirt.org/libvirt/">libvirt.org FTP server</a></li> <li><a href="http://libvirt.org/sources/">libvirt.org HTTP server</a></li>

+ <li><a href="http://libvirt.org/sources/">libvirt.org HTTPS server</a></li>

</ul> <h2><a name="hourly">Hourly development snapshots</a></h2> @@ -35,23 +313,25 @@ <h2><a name="schedule">Primary release schedule</a></h2> <p> - Libvirt follows a time based plan, with releases made once a month - on the 1st of each month give or take a few days. The only exception - is at the start of the year where there are two 6 weeks gaps (first - release in the middle of Jan, then skip the Feb release), giving - a total of 11 releases a year. + The core libvirt module follows a time based plan, with releases made + once a month on the 1st of each month give or take a few days. The only#

+ exception is at the start of the year where there are two 6 weeks gaps + (first release in the middle of Jan, then skip the Feb release), giving + a total of 11 releases a year. The Python and Perl modules will aim to + release at the same time as the core libvirt module. Other modules have + independant ad-hoc releases with no fixed time schedle.