commit 6e524d1be9a8b87de6156c1f47a8bdd453f1d1f0
parent 39c6540bc6a851f97493bbd8790a22451aa9af57
Author: René Wagner <rwa@clttr.info>
Date: Wed, 14 Jul 2021 08:32:13 +0200
update to some templates
most notably:
remove the footer on pages where it's not useful
Diffstat:
5 files changed, 5 insertions(+), 16 deletions(-)
diff --git a/serve/templates/about.gmi b/serve/templates/about.gmi
@@ -32,6 +32,3 @@ If you want to learn more, you should head over to the Gemini Project site itsel
For more extensive documentation about how GUS works, please see the documentation pages.
{% include 'fragments/documentation-toc.gmi' %}
-
-
-{% include 'fragments/footer.gmi' %}
diff --git a/serve/templates/documentation/backlinks.gmi b/serve/templates/documentation/backlinks.gmi
@@ -12,8 +12,6 @@ For a given page in Geminispace, backlinks are all the other pages in Geminispac
The URL structure for retrieving a certain URL's backlinks page is predictable, should you want to link directly to it in other contexts. All you need to do is URL encode the entire URL you want information on, then pass that as a query to gemini://gus.guru/backlinks. An example follows:
-=> gemini://gus.guru/backlinks?gus.guru
+=> gemini://geminispace.info/backlinks?geminispace.info
Note the distinction between "internal" and "cross-capsule" backlinks. Internal backlinks are backlinks from within your own capsule to the given page. Cross-capsule backlinks are backlinks from other users' capsules. Note that the cross-capsule determination is slightly more advanced than purely checking if the hosts are different - it also takes into account different users on pubnixes, so, for example, gemini://foo.bar, gemini://foo.bar/~ronald, and gemini://foo.bar/~mcdonald would all be considered distinct capsules, as they are all presumably authored and maintained by distinct humans.
-
-{% include 'fragments/footer.gmi' %}
diff --git a/serve/templates/documentation/indexing.gmi b/serve/templates/documentation/indexing.gmi
@@ -12,7 +12,7 @@ GUS is a search engine for all content served over the Gemini Protocol. It can h
GUS will only index content within Geminispace, and will neither follow nor index links out to other protocols, like Http or Gopher. GUS will only crawl outwards by following Gemini links found within `text/gemini` pages. If you return a `text/plain` mimetype for a page, Gemini links within it will not register with GUS (though the content of the `text/plain` page will itself get indexed).
-Textual pages over 1MB in size will not be indexed.
+Textual pages over 5 MB in size will not be indexed.
Please note that GUS' indexing has provisions for manually excluding content from it, which maintainers will typically use to exclude pages and domains that cause issues with index relevance or crawl success. GUS ends up crawling weird protocol experiments, proofs of concepts, and whatever other bizarre bits of technical creativity folks put up in Geminispace, so it is a continual effort to keep the index healthy. Please don't take it personally if your content ends up excluded, and I promise we are continually working to make GUS indexing more resilient and scalable!
@@ -20,7 +20,7 @@ Please note that GUS' indexing has provisions for manually excluding content fro
To control crawling of your site, you can use a robots.txt file, Place it in your capsule's root directory such that a request for "robots.txt" will fetch it. It should be returned with a mimetype of `text/plain`.
-GUS obeys User-agent of "indexer" and "*".
+GUS obeys User-agents of "indexer" and "*".
### How can I recognize GUS requests?
@@ -32,5 +32,3 @@ You can identify the GUS by looking for any requests to your site made by the fo
### Does GUS keep my content forever?
No. After repeated failed attempts to connect to a page (e.g., because it moved, or because the capsule got taken down, or because of a server error on your host), GUS will invalidate that page after 1 month of unavailability in its index, thus removing it from search results.
-
-{% include 'fragments/footer.gmi' %}
diff --git a/serve/templates/documentation/searching.gmi b/serve/templates/documentation/searching.gmi
@@ -42,9 +42,7 @@ To allow greater insight into both how pages are ranking against each other, as
There is a button at the top of each search results page to toggle verbose mode on or off, but you can also specify verbose mode manually in your URLs by utilizing the below pattern. Simply add a new "v" path component to the URL preceding the "search" path component. Below is an example:
-=> gemini://gus.guru/search?gemini
-=> gemini://gus.guru/v/search?gemini
+=> gemini://geminispace.info/search?gemini
+=> gemini://geminispace.info/v/search?gemini
Note that verbose mode is sticky, and will persist between pages of results results, so you will need to manually toggle verbose mode off when you are finished with it.
-
-{% include 'fragments/footer.gmi' %}
diff --git a/serve/templates/news.gmi b/serve/templates/news.gmi
@@ -90,5 +90,3 @@ geminispace.info is going public! Yeah! :)
### 2021-01-18
test drive of instance search.clttr.info started
-
-{% include 'fragments/footer.gmi' %}
