# Subtitles inside text

2026-03-01 This is not a very good idea now that I am trying to simplify formatting and posts to keep it as simple as possible, avoiding too format dependent. 2026-09-07 However, I think we can deal with something similar in the future now that we have metadata separated.

Scenario: I want to journal everyday and sometimes it is better to inside one text to quote different content like a movie I watched, a recipe I thought of or something work related. Usually I would need to write one post per subject which would generate separate texts without cohesion.

Idea: it would be nice to have a way to index subtext so I can write about several subjects inside the same text and still be able to search or reference the subjects for the reader. Let's draw an example:

# Main title
2025-11-20 tag

Today I worked about some #csharp code that had me spend some hours because it
needed to configure #windbg in a certain way that I will describe here.

I also watched [The Title of the Movie] today, which I think does not deserve a review,
but could be searchable inside this text if someone is curious to know if I wrote
something about it. #movies

Notice that I could add tags as hashtags inside each paragraph, which could
count as a separate piece of text searchable in tags. Also in the case of
The Title of the Movie it will be listed as a different post in the blog or as a
different title in some e-book indexed by title. And as it has #movies tag it
will also be listed a a movie.

Consider that The Title of the Movies does not exist and it is not referenced. If
there was an entry then we could just reference and then the reversal references
implementation (TBD) would work. Also need to be decided if a text that does
this kind of empty link (no reference) could in the future reference some
new entry just because, without the need to enter the reference in the old
text. This would be cool, but has to pay attention about other signals
like `[1]` (this need to be entered as code, or it is a bottom reference?).

Ideas to be implemented here and could be divided in other issues:

• Reference paragraphs.
• Tag paragraphs.
• Consider subtitles as able to be listed and search (including by its internal tags).
• When a new text with same slug is created reference old text with same pseudo-slug.
• Reverse reference (paragraphs that reference other titles and subtitles).
• Consider bottom references ([1]) when thinking about this.

# Apply tags based on metadata

This issue is to allow to separate tagging based on metadata from tagging based on content. Tagging based on content should be by example the author tags something like "movies" or "cooking" because the content is related to these subjects. Tagging based on metadata should be by example to tag some post as "miniviews" because the content has only one paragraph and it is tagged as "movies" already. Or to tag something like "quotes" because there is only one paragraph and it is a quote.

This tagging by metadata form should not be in the original text, it should be configured as metadata analysis in a separate config form. The author should be able to create different tags based on metadata for different purpose. Tagging based on content should remain simple. The author should not think anymore about to tag content based on its metadata, only in its content that cannot be deduced without IA or author purpose.

# Tags hierarchy by frequency

How about a new future issue where not only the tags are related to each other, but the main ones are deduced by their volume, and the smaller tags are hidden from the overview? This would make navigation simpler for those looking to find something through them.

At the same time, this would allow for granular categorization. For example, a level-3 tag (rarely used) could be designated as a keyword (like the keywords in a research paper) or something along those lines.

The configuration could be based on the percentage of total posts, regardless of how many levels there are. There wouldn’t be direct control from the author, but as they start writing more about a particular topic, the tag would automatically be promoted to a category (main tag).

# Remove personal information from code and support scripts

Today the scripts contain personal blog and book information such as links, author, description.

We are going to move all that to configuration and style (proto theme) settings.

# Suport footnotes

Support to footnotes in ebook or even in the blog.

# Related tags

The idea is to remove necessity of posts to contain every possible tags they fit in to just the main ones (hopefully one). The sister tags will be shown in each tag page so the user can click on the main tag and navigate to other similar tags. By example, a post has "movies" as tag and inside "movies" tag page we see other tags to navigate to its page as "cinema", "miniviews" and so on.

This information can be deduced by the posts and all the tags in common. By example, if one post have the tags movies, cinema and anime then when clicking in each of one of these tags it will list the other tags as a option to navigate.

Eventually there will be a post about a particular group to nest all these tags but no singular post will have to have all those.

# Sections as month/year

Today the blog is structured in "chapters" that are the month and year when each post is labelled. They are put together into the same HTML page as a chapter tied by date.

The idea here is to continue to use date as a marker, but also support other kinds of markers to group posts together as a classic chapter from a book. It should be possible to create, maybe inside the tags, values that are parsed as new groups despite the date each one belongs.

The final view will be posts organized by these new markers and not appearing anymore to the months market. It will be shown in the blog just as the month/year pages, but with another name to group.