Mercurial > p > roundup > code
changeset 8353:85aae98b8c82
docs: bold summary lines in update list; fix formatting issue.
When scanning the document, the summary lines in the list didn't
standout. Also the spacing before and after the summary line were
equal. The spacing under the line should be less to tie it to the
following paragraph.
Not sure I like the bolded summary lines, it's a little too much
emphasis.
I think the css tweak works though.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Thu, 03 Jul 2025 13:19:01 -0400 |
| parents | 6ea309c6d17c |
| children | 586e49dda652 |
| files | doc/_static/style.css doc/announcement.txt |
| diffstat | 2 files changed, 26 insertions(+), 17 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/_static/style.css Thu Jul 03 12:30:21 2025 -0400 +++ b/doc/_static/style.css Thu Jul 03 13:19:01 2025 -0400 @@ -51,6 +51,15 @@ * + * { margin-block-start: 1.2em;} +/* shrink spacing between first and following paragraph in a list item + when the first paragraph is bold/strong. Try to tie the first paragraph + pseudo header closer to the following paragraph. */ +li > p:has(strong):first-child + { + /* background: red; */ + margin-block-end: -0.75em; +} + /* shrink spacing between list elements in tables of contents, badge displays */ div.toctree-wrapper * + *, div.contents * + *, div.release_info * {
--- a/doc/announcement.txt Thu Jul 03 12:30:21 2025 -0400 +++ b/doc/announcement.txt Thu Jul 03 13:19:01 2025 -0400 @@ -28,18 +28,18 @@ Among the significant enhancements in version 2.5.0 compared to the 2.4.0 release are: -* The property/field advanced search expression feature has been - enhanced and documented/ +* **The property/field advanced search expression feature has been + enhanced and documented.** - Search expressions are usually built using the - expression editor on the search page. They can be built manually - by modifying the search URL but the RPN search expression format - was undocumented. Errors in expressions could return results that - didn't match the user's intent. This release documents the RPN - expression syntax, adds basic expression error detection, and - improves error reporting. + Search expressions are usually built using the + expression editor on the search page. They can be built manually + by modifying the search URL but the RPN search expression format + was undocumented. Errors in expressions could return results that + didn't match the user's intent. This release documents the RPN + expression syntax, adds basic expression error detection, and + improves error reporting. -* The default hash method for password storage is more secure. +* **The default hash method for password storage is more secure.** We use PBKDF2 with SHA512 (was SHA1). With this change you can lower the value of password_pbkdf2_default_rounds in your @@ -47,14 +47,14 @@ info. (Note this may cause longer authentication times, the upgrade doc describes how to downgrade the hash method if required.) -* Roundup's session token is now prefixed with the magic - ``__Secure__`` tag when using HTTPS. +* **Roundup's session token is now prefixed with the magic + ``__Secure__`` tag when using HTTPS.** This adds another layer of protection in addition to the existing ``Secure`` property that comes with the session cookie. -* Data authorization can be done at the database level speeding up - display of index pages. +* **Data authorization can be done at the database level speeding up + display of index pages.** Roundup verifies the user's authorization for the data fetched from the database after retrieving data from the database. A new @@ -66,8 +66,8 @@ the database. This leads to quicker display of index pages with reduced CPU and network traffic. -* The REST endpoint can supply binary data (images, pdf, ...) to - its clients. +* **The REST endpoint can supply binary data (images, pdf, ...) to + its clients.** Requesting binary data from a REST endpoint has been a hassle. Since JSON can't handle binary data, images (and other @@ -78,7 +78,7 @@ ``binary_content`` endpoint along with an appropriate ``Accept`` header (e.g. ``image/jpeg``) in your request. -* Extract translatable strings from your tracker easily +* **Extract translatable strings from your tracker easily.** The ``roundup-gettext`` tool has been enhanced to extract translatable strings from detectors and extensions. This will