summaryrefslogtreecommitdiff
path: root/searx/templates/__common__/about.html
AgeCommit message (Collapse)Author
2020-09-29Merge pull request #2226 from dalf/fix-searx-migrationAlexandre Flament
[fix] migration from github.com/asciimoo/searx to github.com/searx/searx : fix URLs
2020-09-28[fix] about.html: fix small inconsistencies in about page (#2219)Qt Resynth
2020-09-28[fix] migration from github.com/asciimoo/searx to github.com/searx/searx : ↵Alexandre Flament
fix URLs
2020-09-22"Egde" → "Edge"Qt Resynth
2020-05-12[fix] about page- 'How to set as the default search engine?'Markus Heiser
Searx supports OpenSearch, remove the inline JS from the about page. close: https://github.com/asciimoo/searx/issues/1949 close: https://github.com/asciimoo/searx/issues/1616 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-03-31[fix] template: fix typo in about.htmlDalf
2020-03-26Minor improvements of the HTML *about* pageMarkus Heiser
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-03-26Rewrite of the HTL *about* pageMarkus Heiser
The *about* page should only address higher-level issues that are important to each user. Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-03-26brands: hardcode ISSUE_URL and some links on the about-pageMarkus Heiser
A *brand* of searx is a fork which might have its own design and some special functions which might bee reasonable in a special context. In this sense, the fork might have its own documentation but not its own issue tracker. The *upstream* of a brand is always https://github.com/asciimoo from where the brand-fork pulls the master branch regularly. A fork which has its own issue tracker is a spin-off and out of the scope of the searx project itself. The conclusion is: - hard code ISSUE_URL (in the Makefile) - always refer to DOCS_URL - links in the about page refer to the *upstream* (searx project) except DOCS_URL - "fork me on github" ribbons refer to the *upstream* Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-03-25[fix] brands: add variables from build env to jinja templatingMarkus Heiser
We have some variables in the build environment which are also needed in the templating process. Theses variables are relavant if one creates a fork with its own branding. We treat these variables under the term 'brands'. Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-02-14[mod] move public instance list to https://searx.spaceDalf
2018-06-18Create an include for __common__/aboutextend.html for imprint purposes.Thomas Renard
2017-01-20[mod] add a __common__ template that can't be selected but that provides a ↵Alexandre Flament
common place for shared templates. What has been moved into this template : * opensearch*.xml is always the same whatever the themes. * the text inside */about.html