Taskmaster4450 started the LeoGlossary project a few days ago and, as we are well accustomed to his proficiency to produce content, things are moving fast and the index (or main menu as he calls it) fills up quickly with new terms and definitions.
His declared goal is to rank up on search engines some definitions by focusing on the key terms and linking them in posts (and even comments). By doing that, Leofinance as a whole ranks up, since definitions are linked as Leofinance posts.
The idea is not bad, as a web of links helps the search engine discover easily more content on Leofinance. He needs our help for a synergistic effect.
Where I see things a little rough in this regard is the fact there is a lot of competition to rank up highly popular key terms. And since all links come from the same domain name, it won't add to the authority of the Leofinance domain.
At the same time, these definitions linked inside posts shouldn't be regarded only for SEO purposes.
Since the glossary includes both cryptocurrency and financial key terms, this is also an opportunity to educate newcomers to either domain, through short and easy-to-understand definitions.
That's why I believe the work is important. But it would be much more beneficial if more people start to use the key terms and link to definitions (as I did with 'cryptocurrency' above, but a better example is my previous post)
Challenges
The approach Taskmaster has taken isn't without challenges.
Being involved in a project of a similar nature on the previous chain, I pointed out a few and offered some tips here and there.
1. Constant Maintenance
This kind of project requires constant maintenance. That's because time goes by and some definitions need to be brought up to date. Maybe others need to be added and others removed. Plus, search engines like updated content.
2. Index Post (the "Main Menu")
If the index remains as a post, it may need to become index posts, so broken into multiple posts. The alternative would be to be turned into a special page/subdomain on the Leofinance website, but that would probably restrict Task's simple access to it. A domain of its own is another idea.
Let's see why the index would need to be broken into multiple posts if it continues to grow much bigger.
As we know the block size on Hive is 65kb. That's 65536 bytes (or characters, in our case) to be precise.
No operation on Hive can exceed that size, or it's impossible to include it in a block.
The posting operation, besides the markdown for the post also includes metadata, like the time of posting/editing, the author, the tags, the title, the permalink, the list of images included in the post, list of links included in the post, the interface where it was posted from, rewards, voters, and so on.
You can see the details here for LeoGlossary's "Main Menu". Expand the properties to see the metadata information.
Without the metadata, it looks like the index already has almost 10k in size.
But I'd add a couple of thousands for the current metadata.
It still has enough room until 65k, but remember at least links are kept in doubles, once in the markdown code and the other time in the metadata. And the index is made up mostly of links. The more key terms are added, the more links are added to both the markdown and the metadata.
To be honest, I thought by now it would have a bigger size. It may be possible to keep it well below 65k if the glossary doesn't grow much bigger than its current size.