Skip to content

Commit 109ab02

Browse files
committed
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.
1 parent fdba590 commit 109ab02

File tree

2 files changed

+26
-17
lines changed

2 files changed

+26
-17
lines changed

doc/_static/style.css

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,15 @@
5151

5252
* + * { margin-block-start: 1.2em;}
5353

54+
/* shrink spacing between first and following paragraph in a list item
55+
when the first paragraph is bold/strong. Try to tie the first paragraph
56+
pseudo header closer to the following paragraph. */
57+
li > p:has(strong):first-child
58+
{
59+
/* background: red; */
60+
margin-block-end: -0.75em;
61+
}
62+
5463
/* shrink spacing between list elements in tables of contents,
5564
badge displays */
5665
div.toctree-wrapper * + *, div.contents * + *, div.release_info * {

doc/announcement.txt

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -28,33 +28,33 @@ then unpack and test/install from the tarball.
2828
Among the significant enhancements in version 2.5.0 compared to
2929
the 2.4.0 release are:
3030

31-
* The property/field advanced search expression feature has been
32-
enhanced and documented/
31+
* **The property/field advanced search expression feature has been
32+
enhanced and documented.**
3333

34-
Search expressions are usually built using the
35-
expression editor on the search page. They can be built manually
36-
by modifying the search URL but the RPN search expression format
37-
was undocumented. Errors in expressions could return results that
38-
didn't match the user's intent. This release documents the RPN
39-
expression syntax, adds basic expression error detection, and
40-
improves error reporting.
34+
Search expressions are usually built using the
35+
expression editor on the search page. They can be built manually
36+
by modifying the search URL but the RPN search expression format
37+
was undocumented. Errors in expressions could return results that
38+
didn't match the user's intent. This release documents the RPN
39+
expression syntax, adds basic expression error detection, and
40+
improves error reporting.
4141

42-
* The default hash method for password storage is more secure.
42+
* **The default hash method for password storage is more secure.**
4343

4444
We use PBKDF2 with SHA512 (was SHA1). With this change you can
4545
lower the value of password_pbkdf2_default_rounds in your
4646
tracker's config.ini. Check the upgrading documentation for more
4747
info. (Note this may cause longer authentication times, the
4848
upgrade doc describes how to downgrade the hash method if required.)
4949

50-
* Roundup's session token is now prefixed with the magic
51-
``__Secure__`` tag when using HTTPS.
50+
* **Roundup's session token is now prefixed with the magic
51+
``__Secure__`` tag when using HTTPS.**
5252

5353
This adds another layer of protection in addition to the
5454
existing ``Secure`` property that comes with the session cookie.
5555

56-
* Data authorization can be done at the database level speeding up
57-
display of index pages.
56+
* **Data authorization can be done at the database level speeding up
57+
display of index pages.**
5858

5959
Roundup verifies the user's authorization for the data fetched
6060
from the database after retrieving data from the database. A new
@@ -66,8 +66,8 @@ the 2.4.0 release are:
6666
the database. This leads to quicker display of index pages with
6767
reduced CPU and network traffic.
6868

69-
* The REST endpoint can supply binary data (images, pdf, ...) to
70-
its clients.
69+
* **The REST endpoint can supply binary data (images, pdf, ...) to
70+
its clients.**
7171

7272
Requesting binary data from a REST endpoint has been a
7373
hassle. Since JSON can't handle binary data, images (and other
@@ -78,7 +78,7 @@ the 2.4.0 release are:
7878
``binary_content`` endpoint along with an appropriate ``Accept``
7979
header (e.g. ``image/jpeg``) in your request.
8080

81-
* Extract translatable strings from your tracker easily
81+
* **Extract translatable strings from your tracker easily.**
8282

8383
The ``roundup-gettext`` tool has been enhanced to extract
8484
translatable strings from detectors and extensions. This will

0 commit comments

Comments
 (0)