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
Setup «Weekly Pages» with this manual and «Monthly Pages» with this one.
Install Block Calendar plugin to create year overview calendar.
Install Missing Commands plugin to create tabular view for quarter breakdown.
Let's prepare the query for monthly records. Create anywhere in Logseq (ex: in «Queries» page) the following query (use copy button in the top right corner):
Restriction: currently there is no way in Logseq to avoid copying of other queries, so they are hardcoded in template body. Please vote for this feature here and like this comment.
Create 🏛template anywhere in Logseq (ex: in «Templates» page). (Use copy button in the top right corner):
Copy reference to query created before via right clicking on corresponding bullet and selecting «Copy block embed»:
…and insert them replacing line with «INSERT HERE» text in the template (there are three lines). It should look like:
And add \d{4}::.yearly page inserter text to Default Template plugin's setting /advancedRegex:
Additionally you can setup Awesome Links plugin to have colored references to Monthly Pages (according to type:: month):
Goto plugin settings (t s) → Awesome Links and set the inheritFromProp setting to type:
Go to [[month]] page and add page property color:: mediumseagreen (choose any value you want via this service).
❤️ Enjoy the full automatic monthly page creation!
FAQ
Why are queries embedded instead of being written directly in the template?
Because if you want to change the query, you would only need to modify it in one place - and the changes will be immediately visible on all already created weekly pages. This is very handy. But if you don't need this - you can do without embed and each time "enclose" the query inside the weekly page. Then, when changing the query in the template, only new pages will see its new look.
Why is the property reference:: with the value #podcast displayed in the query block?
Visually, it's clear what type of data we're looking at. Although you could use the query title for this, or simply write the heading "Podcasts Overview".
For an easy configuration, if you suddenly want to change #podcast to something else (for example, to #youtube-video).
To have a block with a query in Linked References, on the podcast page. This is handy if you want to rename the podcast page (e.g. to 🎙️). The block with the query will be renamed automatically. If it is not in Linked References, you will have to a) remember that the block with the query on the pages requires manual modification b) carry out this manual modification.
If you want to hide this property, you can do this via custom.css:
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
inspired by this Obsidian video and @inzagi1's question
2024-08-15.15.04.31.mp4
Steps
Setup «Weekly Pages» with this manual and «Monthly Pages» with this one.
Install
Block Calendar
plugin to create year overview calendar.Install
Missing Commands
plugin to create tabular view for quarter breakdown.Let's prepare the query for monthly records. Create anywhere in Logseq (ex: in «Queries» page) the following query (use copy button in the top right corner):
Restriction: currently there is no way in Logseq to avoid copying of other queries, so they are hardcoded in template body. Please vote for this feature here and like this comment.
Create
🏛template
anywhere in Logseq (ex: in «Templates» page). (Use copy button in the top right corner):Copy reference to query created before via right clicking on corresponding bullet and selecting «Copy block embed»:

…and insert them replacing line with «INSERT HERE» text in the template (there are three lines). It should look like:
Now, let's install and setup
Default Template
plugin to automatically insert🏛️template
. Create another template:And add

\d{4}::.yearly page inserter
text toDefault Template
plugin's setting/advancedRegex
:Additionally you can setup
Awesome Links
plugin to have colored references to Monthly Pages (according totype:: month
):t s
) → Awesome Links and set theinheritFromProp
setting totype
:[[month]]
page and add page propertycolor:: mediumseagreen
(choose any value you want via this service).❤️ Enjoy the full automatic monthly page creation!
FAQ
Why are queries embedded instead of being written directly in the template?
Because if you want to change the query, you would only need to modify it in one place - and the changes will be immediately visible on all already created weekly pages. This is very handy. But if you don't need this - you can do without embed and each time "enclose" the query inside the weekly page. Then, when changing the query in the template, only new pages will see its new look.
Why is the property
reference::
with the value#podcast
displayed in the query block?#podcast
to something else (for example, to#youtube-video
).podcast
page. This is handy if you want to rename thepodcast
page (e.g. to🎙️
). The block with the query will be renamed automatically. If it is not in Linked References, you will have to a) remember that the block with the query on the pages requires manual modification b) carry out this manual modification.custom.css
:See also
Additional info
Beta Was this translation helpful? Give feedback.
All reactions