Apply sentence case to all H1s in docs/en/ and remove redundant "FreshRSS" from titles where the docs site context already implies it. Align the three section index titles to "Administrator/Developer/User manual", matching the existing root H1 "FreshRSS manual (English)". Add missing H1s to two pages that were silently dropped from the sidebar: the user FAQ and the Caddy reverse proxy page. The sidebar template uses page.title (derived from H1 by jekyll-titles-from-headings), so pages without an H1 had title=nil and were skipped. Update sidebar parent labels in docs_nav.html and the chapter list in en/index.md to use the new "* manual" naming. Update link text in section indexes that referenced the old H1s. Bundle two grammar fixes encountered along the way: "an User Interface" -> "a user interface", and drop the awkward "the" in "Configuring the email address validation". EN only. No filenames, URLs, or anchor targets changed (anchors come from H2 and below, which are untouched). FR is generated from EN via po4a and will be regenerated separately. Co-authored-by: Bjørn A. Andersen <polybjorn@users.noreply.github.com>
7.4 KiB
OPML
FreshRSS supports the OPML format to export and import lists of RSS/Atom feeds in a standard way, compatible with several other RSS aggregators.
However, FreshRSS also supports several additional features not covered by the basic OPML specification. Luckily, the OPML specification allows extensions:
An OPML file may contain elements and attributes not described on this page, only if those elements are defined in a namespace.
and:
OPML can also be extended by the addition of new values for the type attribute.
FreshRSS OPML extension
FreshRSS uses the XML namespace https://freshrss.org/opml to export/import extended information not covered by the basic OPML specification.
The list of the custom FreshRSS attributes can be seen in the source code, and here is an overview:
HTML+XPath or XML+XPath
<outline type="HTML+XPath" ...: Additional type of source, which is not RSS/Atom, but HTML Web Scraping using XPath 1.0.
ℹ️ XPath 1.0 is a standard query language, which FreshRSS supports to enable Web scraping.
<outline type="XML+XPath" ...: Same thanHTML+XPathbut using an XML parser.
The following attributes are using similar naming conventions than RSS-Bridge.
frss:xPathItem: XPath expression for extracting the feed items from the source page.- Example:
//div[@class="news-item"]
- Example:
frss:xPathItemTitle: XPath expression for extracting the item’s title from the item context.- Example:
descendant::h2
- Example:
frss:xPathItemContent: XPath expression for extracting an item’s content from the item context.- Example:
.
- Example:
frss:xPathItemUri: XPath expression for extracting an item link from the item context.- Example:
descendant::a/@href
- Example:
frss:xPathItemAuthor: XPath expression for extracting an item author from the item context.- Example:
"Anonymous"
- Example:
frss:xPathItemTimestamp: XPath expression for extracting an item timestamp from the item context. The result will be parsed bystrtotime().frss:xPathItemTimeFormat: Date/Time format to parse the timestamp, according toDateTime::createFromFormat().frss:xPathItemThumbnail: XPath expression for extracting an item’s thumbnail (image) URL from the item context.- Example:
descendant::img/@src
- Example:
frss:xPathItemCategories: XPath expression for extracting a list of categories (tags) from the item context.frss:xPathItemUid: XPath expression for extracting an item’s unique ID from the item context. If left empty, a hash is computed automatically.
JSON+DotNotation
-
<outline type="JSON+DotNotation" ...: Similar toHTML+XPathbut for JSON and using a dot/bracket syntax such asobject.object.array[2].property. -
frss:jsonItem: JSON dot notation for extracting the feed items from the source page.- Example:
data.items
- Example:
-
frss:jsonItemTitle: JSON dot notation for extracting the item’s title from the item context.- Example:
meta.title
- Example:
-
frss:jsonItemContent: JSON dot notation for extracting an item’s content from the item context.- Example:
content
- Example:
-
frss:jsonItemUri: JSON dot notation for extracting an item link from the item context.- Example:
meta.links[0]
- Example:
-
frss:jsonItemAuthor: JSON dot notation for extracting an item author from the item context. -
frss:jsonItemTimestamp: JSON dot notation for extracting an item timestamp from the item context. The result will be parsed bystrtotime(). -
frss:jsonItemTimeFormat: Date/Time format to parse the timestamp, according toDateTime::createFromFormat(). -
frss:jsonItemThumbnail: JSON dot notation for extracting an item’s thumbnail (image) URL from the item context. -
frss:jsonItemCategories: JSON dot notation for extracting a list of categories (tags) from the item context. -
frss:jsonItemUid: JSON dot notation for extracting an item’s unique ID from the item context. If left empty, a hash is computed automatically.
JSON Feed
<outline type="JSONFeed" ...: UsesJSON+DotNotationbehind the scenes to parse a JSON Feed.
HTML+XPath+JSON
<outline type="HTML+XPath+JSON+DotNotation" frss:xPathToJson="..." ...: Same asJSON+DotNotationbut first extracting the JSON string from an HTML document thanks to an XPath expression.- Example:
//script[@type='application/json']
- Example:
cURL
A number of cURL options are supported:
frss:CURLOPT_COOKIEfrss:CURLOPT_COOKIEFILEfrss:CURLOPT_FOLLOWLOCATIONfrss:CURLOPT_HTTPHEADERfrss:CURLOPT_MAXREDIRSfrss:CURLOPT_POSTfrss:CURLOPT_POSTFIELDSfrss:CURLOPT_PROXYfrss:CURLOPT_PROXYTYPEfrss:CURLOPT_USERAGENT
Miscellaneous
frss:priority: Used for priority / visibility of the articles of that feed. Can be:important,main(default),category,feed,hidden.frss:unicityCriteria: Criteria used for the unicity of articles. E.g.id(default),link,sha1:link_published,sha1:link_published_title,sha1:title, etc.frss:unicityCriteriaForced: Boolean to force the usage of the selected unicity criterion even in the case of many duplicates (otherwise, the default behaviour is to fall back to a more precise unicity criteria).frss:cssFullContent: CSS Selector to enable the download and extraction of the matching HTML section of each articles’ Web address.- Example:
div.main, .summary
- Example:
frss:cssContentFilter: CSS Selector to remove the matching HTML elements from the article content or from the full content retrieved byfrss:cssFullContent.- Example:
.footer, .aside.frss:cssFullContentConditions: List (separated by a new line) of search queries to trigger a full content retrieval as defined byfrss:cssFullContent.
- Example:
frss:filtersActionRead: List (separated by a new line) of search queries to automatically mark a new article as read.
Dynamic OPML (reading lists)
frss:opmlUrl: If non-empty, indicates that this outline (category) should be dynamically populated from a remote OPML at the specified URL.
Example
<?xml version="1.0" encoding="UTF-8"?>
<opml version="2.0">
<head>
<title>FreshRSS OPML extension example</title>
</head>
<body>
<outline xmlns:frss="https://freshrss.org/opml"
text="Example"
type="HTML+XPath"
xmlUrl="https://www.example.net/page.html"
htmlUrl="https://www.example.net/page.html"
description="Example of Web scraping"
frss:priority="main"
frss:xPathItem="//a[contains(@href, '/interesting/')]/ancestor::article"
frss:xPathItemTitle="descendant::h2"
frss:xPathItemContent="."
frss:xPathItemUri="descendant::a[string-length(@href)>0]/@href"
frss:xPathItemThumbnail="descendant::img/@src"
frss:cssFullContent="article"
frss:filtersActionRead="intitle:⚡️ OR intitle:🔥 something"
/>
</body>
</opml>