Skip to content

Commit cdfec45

Browse files
committed
Initial restructuring of pages.
Also some minor content tweaks.
1 parent d2d9b74 commit cdfec45

19 files changed

+31
-28
lines changed

docs/API-Reference.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
layout: default
33
title: API Reference
4-
nav_order: 3
54
---
65

76
{: .no_toc }

docs/Android-Client.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
22
layout: default
33
title: Android Client
4-
nav_order: 40
4+
parent: Legacy
55
---
66

77
## **IMPORTANT**
88

99
* The original tt-rss-android project, hosted at <https://tt-rss.org/> and its various subdomains,
10-
[will be gone after 2025-11-01](https://community.tt-rss.org/t/the-end-of-tt-rss-org/7164).
10+
went away on 2025-11-01.
1111
* There are currently no plans to continue maintaining the app.
1212
* The app's source code may be found at <https://github.com/tt-rss/tt-rss-android>.
13-
* **APK downloads from <https://gitlab.tt-rss.org/tt-rss/tt-rss-android/-/releases> are no longer working. This is likely permanent.**
13+
* APKs that were available at <https://gitlab.tt-rss.org/tt-rss/tt-rss-android/-/releases> are gone.
1414
* This page's content should only be treated as a historical reference.
15-
* Refer to <https://github.com/tt-rss/tt-rss/discussions/29> for more information.
15+
* Refer to <https://github.com/tt-rss/tt-rss-android/discussions/8> for more information.
1616

1717
## Screenshots
1818

docs/Archived-Feed.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Archived Feed
4-
nav_order: 41
4+
parent: Features
55
---
66

77
Archived is the place for articles for which originating feed no longer exists.

docs/Content-Filters.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Content Filters
4-
nav_order: 20
4+
parent: Features
55
---
66

77
Filters are a very powerful and flexible tool which may significantly ease the

docs/Email-Digests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Email Digests
4-
nav_order: 42
4+
parent: Features
55
---
66

77
Users may opt into receiving daily (sent once every 24 hours) digests of unread headlines via email.

docs/Encryption.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
---
22
layout: default
33
title: Encryption
4-
nav_order: 43
4+
parent: Security
55
---
66

7-
Transparent at rest encryption is optionally supported for sensitive data stored in the database, currently limited to stored session data and passwords for feeds with authentication enabled.
7+
Transparent at-rest encryption is optionally supported for sensitive data stored in the database,
8+
currently limited to stored session data and passwords for feeds with authentication enabled.
89

9-
To enable, [global configuration](Global-Config) option `TTRSS_ENCRYPTION_KEY` should be set to a 32-byte hex string of random bytes, which may be generated using CLI like this:
10+
To enable, [global configuration](Global-Config) option `TTRSS_ENCRYPTION_KEY` should be set to a 32-byte hex string of random bytes,
11+
which may be generated using CLI like this:
1012

1113
```sh
1214
php ./update.php --gen-encryption-key
@@ -15,4 +17,6 @@ php ./update.php --gen-encryption-key
1517
If enabled, existing plaintext login sessions are automatically encrypted when used, plaintext feed passwords are encrypted on feed update.
1618

1719
{: .warning }
18-
> Automatic encryption of plaintext data is a one-way process. If you decide to disable `TTRSS_ENCRYPTION_KEY` afterwards, all encrypted sessions would become invalid and you will get logged out. Feed passwords would become unreadable until you either enable encryption back using same key or edit feeds manually.
20+
> Automatic encryption of plaintext data is a one-way process. If you decide to disable `TTRSS_ENCRYPTION_KEY` afterwards, all encrypted sessions would
21+
> become invalid and you will get logged out. Feed passwords would become unreadable until you either enable encryption back using same key or edit feeds
22+
> manually.

docs/FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: FAQ
4-
nav_order: 30
4+
nav_order: 3
55
---
66

77
{: .note }

docs/Feed-Handler-Plugins.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
layout: default
33
title: Feed Handler Plugins
4-
nav_order: 44
4+
parent: Plugins
5+
nav_order: 2
56
---
67

78
{: .warning }

docs/Generated-Feeds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Generated Feeds
4-
nav_order: 45
4+
parent: Features
55
---
66

77
You can generate a feed (in Atom or JSON format) for almost anything displayed

docs/Global-Config.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: default
33
title: Global Configuration
4-
nav_order: 21
4+
nav_order: 4
55
---
66

77
All settings (see `_DEFAULTS[]` for default values) are listed here:

0 commit comments

Comments
 (0)