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
To complement template-sync command there could be a new-node command or something that creates a boilerplate file given enough params to do so. This should be a plugin point complementary to parse, that is a parse-capable plugin would typically support writing a new file to the same source space, starting with markdown.
sctx template apply ... # apply a template to a new or existing node - fills in blanks for existing nodes
sctx template sync ... # new home for existing templates-sync
Embracing node types as a thing
As above but s/template/type/ and see what that feels like conceptually
sctx type apply ...
sctx type template-sync ...
[!note] on deriving location for a new node
Issue #73 talks about content type inference from structure. It might be better to extend that to being a content structure signal more broadly, used for type inference, but also for working out where to put a new file. eg "flat" structure puts everything in one folder, "by-type" would find a matching directory by type for new files.
The type inference work (folder-based type inference from #1c94898) opens a path for this — a new-node command could use the same inference logic to determine the correct type or placement for a new file given a target location, reducing what the user needs to specify explicitly.
Activity
mindsocket commentedon Apr 7, 2026
The type inference work (folder-based type inference from #1c94898) opens a path for this — a
new-nodecommand could use the same inference logic to determine the correct type or placement for a new file given a target location, reducing what the user needs to specify explicitly.