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
I have checked existing issues and there are no existing ones with the same request.
Feature description
tl;dr
Add support for various types of periodic notes. Currently, only daily notes (a.k.a. journal) are supported.
Types of Periodic Notes
Daily (currently implemented using the "core.journal" module)
Weekly
Monthly
Quarterly
Yearly
Custom
Custom Notes
It would be beneficial to allow custom periodic notes, such as 2-week periods. See my use case for further details.
Implementation Idea
All periodic notes could be implemented as presets of custom periodic notes. This means reorganizing the current support for daily journal notes into a more flexible system that supports custom periods. After this, presets for core periodic notes (such as daily, weekly, monthly, etc.) can be added for ease of use.
My Use Case
I use notes for both my professional and personal life. Here is how I organize them:
By adding support for these additional types of periodic notes and implementing them as presets of custom notes, users will have more flexibility in how they organize and manage their notes, catering to both personal and professional needs. This approach not only simplifies the implementation but also enhances user experience by providing ready-to-use templates for common periodic notes.
P.s. It would be great to have the ability to generate links between periodic notes. For example, links from a weekly note to all 7 daily notes and from each daily note back to the weekly note. However, this might be better suited as a separate feature request.
Help
Yes, but I don't know how to start. I would need guidance
Implementation help
No response
The text was updated successfully, but these errors were encountered:
I think you could implement this with the current journal + the dynamic templates plugin and a few auto commands, it would just require a decent bit of logic (that could be extracted into its own neorg module). The thing you would need a neorg module is the custom commands.
Becuase this feature should use dynamic templates, I think it should be its own external module that makes use of neorg-templates rather than an internal module.
This sounds like a cool idea, although it should still be somehow linked to the journal IMO. This might require some sort of rethink of how the journal functions, or allowing the journal to operate in various modes. Some planning is required for this before an implementation is made.
Issues
Feature description
tl;dr
Add support for various types of periodic notes. Currently, only daily notes (a.k.a. journal) are supported.
Types of Periodic Notes
Custom Notes
It would be beneficial to allow custom periodic notes, such as 2-week periods. See my use case for further details.
Implementation Idea
All periodic notes could be implemented as presets of custom periodic notes. This means reorganizing the current support for daily journal notes into a more flexible system that supports custom periods. After this, presets for core periodic notes (such as daily, weekly, monthly, etc.) can be added for ease of use.
My Use Case
I use notes for both my professional and personal life. Here is how I organize them:
Personal Life:
Job:
This feature is inspired by the "periodic notes" plugin for Obsidian.
By adding support for these additional types of periodic notes and implementing them as presets of custom notes, users will have more flexibility in how they organize and manage their notes, catering to both personal and professional needs. This approach not only simplifies the implementation but also enhances user experience by providing ready-to-use templates for common periodic notes.
P.s. It would be great to have the ability to generate links between periodic notes. For example, links from a weekly note to all 7 daily notes and from each daily note back to the weekly note. However, this might be better suited as a separate feature request.
Help
Yes, but I don't know how to start. I would need guidance
Implementation help
No response
The text was updated successfully, but these errors were encountered: