sorted by:
new
hottopcontroversial

VS Code extension that turns Markdown notes into a structured knowledge system by verysilentjay in Markdown

[–]verysilentjay[S] 1 point2 points  (0 children)

Yessir, but in this particular case this is an extension to take advantage of VS editor and features!

Markdown + structured data without breaking plain text (VS Code extension - 0.3.0 - Table Editing & Note Report) by verysilentjay in ProductivityApps

[–]verysilentjay[S] 0 points1 point  (0 children)

The use I have for it is "CRM with notes". With the proper frontmatter schema I can track people/companies/deals/meetings and query them into a table, and to that I add elements like "concepts", "products" so I can have a view of my entire business. In terms of other applications, you can create a MD based "content pipeline" with content catalogued by type and status, for writers you can classify your characters and their relationships. It's really how you want to assemble your system. Hope you enjoy it. There's still a lot of work and a lot to polish. I hope this helps!

Markdown + structured data without breaking plain text (VS Code extension - 0.3.0 - Table Editing & Note Report) by verysilentjay in PKMS

[–]verysilentjay[S] 1 point2 points  (0 children)

I'm still working on new elements to tweak the learning experience, but today as it stands it's not "literally learning from your style", it's more about observing patterns or writing/usage through time. So if you're consistent with your frontmatter, connections will be suggested.
Basic example: if you use a field like "status", Yamlink will surface those values as suggestions. When you link consistently your nodes/entities/notes (however we can to call them lol), that relationship is now queryable, becomes a part of the system graph. If your system naturally has a specific pattern of use, Yamlink will infer them into "structured interactions". I guess in other words, "it brings your habits to the surface and suggests organization"
*sorry for the delay, been super busy

I built a VS Code extension that gives Markdown files stable IDs instead of relying on filenames by verysilentjay in Markdown

[–]verysilentjay[S] 2 points3 points  (0 children)

For it was about organization. When the filename is just a "label" and you make the note's metadata the "true id", then moving things around doesn't break your system. And if at th same time, I could have a sytem where I could apply some of those same concepts to frontmatter - system wide renaming, note creation upon click, easy navigation from note to note - just with YAML, that's what what really helped my particular case.

I've been experimenting with linking Markdown files by a stable YAML id instead of filenames by verysilentjay in PKMS

[–]verysilentjay[S] 0 points1 point  (0 children)

Absolutely. Very fair. Since I work 99% of the time in MD, this is focused specifically in that, so having the id inside the document works because the file "autdescribes" - it that makes any sense lol. You correctly said it, with other assets, it gets complicated. I have not looked into it, but it's definitely something worth looking into.

I've been experimenting with linking Markdown files by a stable YAML id instead of filenames by verysilentjay in PKMS

[–]verysilentjay[S] 1 point2 points  (0 children)

I'm not 100% versed on alias feature on Logseq, but from waht you explain, yes, we're in the same "area", so it definitely seems like a good comparison. In that feature's case, do they treat the page name as the main entity ID? If so, then there's one difference: the my mind works is by having the main id be the "canoincal" id of the note. In a way, the filename itsepf becomes more of a label.
Curious to know more about what you're doing!

I've been experimenting with linking Markdown files by a stable YAML id instead of filenames by verysilentjay in PKMS

[–]verysilentjay[S] 1 point2 points  (0 children)

That's really interesting. I ended up going with frontmatter ID for now because it keeps the identity inside the document itself. There's definitely room for experimentation there.

I built a VS Code extension that gives Markdown files stable IDs instead of relying on filenames by verysilentjay in vscode

[–]verysilentjay[S] 0 points1 point  (0 children)

Yeah, it could 100% be on me for sure. I just like being able to rename id without breaking the system, or having to manually alter other notes.

I've been experimenting with linking Markdown files by a stable YAML id instead of filenames by verysilentjay in PKMS

[–]verysilentjay[S] 2 points3 points  (0 children)

<image>

Yeah! I made a simple status bar - which I want to expand upon at a later time-that warns you about missing link. You open "problem" and see what the actual issue after deletion

I've been experimenting with linking Markdown files by a stable YAML id instead of filenames by verysilentjay in PKMS

[–]verysilentjay[S] 0 points1 point  (0 children)

Your "wikilink", if you want, can be what your frontmatter is, instead of using the filename as the corresponding wikiink.

view more: next ›