-
Notifications
You must be signed in to change notification settings - Fork 34
Tags
Orgmode Elements > Tags
Tags within lazyblorg work exactly as within Org mode in general. However, lazyblorg added functionality that exceeds the semantics of plain Org mode.
On this page, you learn about special tags and auto-tags. All other tags of a blog article heading are added to the blog article result as tags.
On Tag Pages, you will learn about creating optional tag pages to describe, what you do mean with a certain tag.
Following tags do have special meanings when applied to headings that start a blog article:
This is the default value of TAG_FOR_BLOG_ENTRY
.
As mentioned above, only headings that are tagged with blog
are
considered to be a potential heading starting a blog article.
When an article is tagged as hidden
, the article gets published in
the resulting files. However, following things do ignore or conceal
the article:
- Entry page
- All feeds
- Navigational pages
This way, you are able to publish an article so that only people who know the final URL are able to navigate to it. The URL is derived as usual:
- The
ID
is used as the directory of the article- Optional ISO datestamps are removed beforehand
- examples:
-
foo-bar
→foo-bar
-
2017-07-21-foo-bar
→foo-bar
-
- The URL is either:
-
BASE_URL/foo-bar/
for persistent articles -
BASE_URL/2017/07/21/foo-bar/
for temporal articles -
BASE_URL/tags/foo-bar/
for tag pages
-
Please notice that adding the hidden
tag after the blog article was
published before without the hidden
tag might still lead to hits
when somebody is searching for it via search engines.
This is the default value of TAG_FOR_PERSISTENT_ENTRY
.
See Persistent-Pages for details.
This is the default value of TAG_FOR_TAG_ENTRY
.
See Tag-Pages for details.
This is the default value of TAG_FOR_TEMPLATES_ENTRY
.
See Templates for details.
Headings with this tag never find their way to the blog result.
You can use this to temporarily omit a heading or a sub-hierarchy of an article or for headings containing your personal notes or for TODO tasks related to the article.
The current implementation of lazyblorg supports only one type of auto-tag: the language of the blog article.
In the future, there could be more auto-tags such as for article length (small, medium, large) and such. Please take part in the discussion for an existing related issue or create a new one for a new idea for an auto-tag.
Auto-tags differ from user tags visually. For example, the language
auto-tag for German looks like language:deutsch
. You notice the
colon within, which is not possible with a normal Org mode tag.
Language detection within lazyblorg is done very easily: in
lib/utils.py you will find a defined list of STOPWORDS
and the
function guess_language_from_stopword_percentages()
.
Within the list, all known languages with their most frequent stopwords are set.
If you need to add support for an additional language, all you have to
do is appending a corresponding list item to STOPWORDS
.
When your blog is (re-)generated by lazyblorg, the text of each blog
article is compared to the stopwords. If the set of stopwords for
exactly one language is dominant over the other(s), we do have an
educated guess on the article language. If this is not that clearly,
lazyblorg assigns the auto-tag language:unsure
instead.
To manually override the “unsure” decision or even override the
clear decision for a different language, you are able to tag the blog
article with the language identifier used in STOPWORDS
. This will
override the language detection in any case.
Using lazyblorg:
- Page Types (must-read)
- Orgmode Elements (must-read)
- FAQs
- Roadmap
- Project Origin
- Similar Projects
Coding: