@Zhiyuan_Chen Thank you for this. I figured the same. I think where I am having trouble is I have forgotten where I put in the contents of the template. Is it between “PROPERTIES” and “END”? Do the contents have to be one the same line as properties?
I believe the most convenient way to deal with templates is to create a dedicated file that will hold all the templates in one place (in my case I named it ls_templates.md. that way, I can easily find and edit my source templates.
note that templates can be structured bullets, but also be :PROPERTIES: (with one drawback : the order of properties is not saved) or a mix of both.
Completely forget all the time, some times I make templates, other times they are partially there and other times nothing. I feel like there should be a better way with templates.
when Logseq asks you to name a template, show the user a list of existing templates automatically so you can better choose a name that fits with your current templates.
have Logseq automatically create/reserve a Logseq page called “templates” that collects and displays existing templates, also making it easier for the user to find the “home” location of all templates so they can easily review and edit existing ones
Thank you Cobblepot,
I appreciate your detailed template info.
Do you have any other resources or know more about Template creation
How to work with the properties, what are the limitations in creating one.
any case studies to understand on how to create the properties and use them.
And also for modifying my templates (I have a fair share of beginner mistakes in them), I change the block. Yet when I go back to /template I find the good old version there again.
Any help is appreciated
Looking for this exact fix. Any ideas? Sometimes I want to add new fields after I’ve created my template. It’s a bit of a pain to go to each page and update it one by one