You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMHO it will be great to support such tag extensions (or something similar) into the standard github reader. It's hardly to explain in a few words how useful it is to be able to tag content and how it helps in a daily basis. Some references can be found searching for Zettlekasten methods:
My project's tag extension improves over standard the Zettlekasten methodology by splitting tags into topics/subtopics -dimensions/coordinates-, allowing for a simple and more efficient management.
From a software architecture point of view, such extensions allows to convert a simple markdown into a "CMS":
The MD itself becomes a text-source database, and the database engine runs completely into user's browser.
This method is not only very useful for humans, but also a great help for training ML engines like LLM, providing "orthogonal" context "around" the text.
This same taggin system can/could be used to tag software source code, by just embedding the tags into comments. IDEs with tag supports will/would just be able to navigate the code based on orthogonal aspects like UI, security, data model, business model, usability, QA, Project Management, ... (Yes I know, I'm dreaming!).
It follows an example of the markdown extension I use in practice to classify Java programming notes:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
Hi all,
I created a markdown reader with some non-standard extensions that boost "productivity" by allowing to tag content according to topics and subtopics.
The project is available in github at https://github.com/earizon/txt_world_domination
IMHO it will be great to support such tag extensions (or something similar) into the standard github reader. It's hardly to explain in a few words how useful it is to be able to tag content and how it helps in a daily basis. Some references can be found searching for Zettlekasten methods:
My project's tag extension improves over standard the Zettlekasten methodology by splitting tags into topics/subtopics -dimensions/coordinates-, allowing for a simple and more efficient management.
From a software architecture point of view, such extensions allows to convert a simple markdown into a "CMS":
This method is not only very useful for humans, but also a great help for training ML engines like LLM, providing "orthogonal" context "around" the text.
This same taggin system can/could be used to tag software source code, by just embedding the tags into comments. IDEs with tag supports will/would just be able to navigate the code based on orthogonal aspects like UI, security, data model, business model, usability, QA, Project Management, ... (Yes I know, I'm dreaming!).
It follows an example of the markdown extension I use in practice to classify Java programming notes:
Beta Was this translation helpful? Give feedback.
All reactions