Modularize the project

[neo451]

I would say it will not be a big breaking change, we can just do:

Add a enabled field to existing submodule

like templates.enabled = false, this can also help user who don't do templates or dailies to have a cleaner command interface: #78
this is also quite a idiomatic thing for neovim plugins, like snacks.nvim and lazy.nvim all do this for its submodules.

Make modules correspond to code modules, and wiki page

move img_paste.lua to attachments/ folder, daily related functions to daily_notes/ folder and etc, so that more developer friendly. This also this gives us a more clear sense of the core/

New modules

for existing plugins. we can either fork these into our org if not actively maintained, or just simply add integration as a command and have a config module into it.

sync

obsidian-git
remotely-save

recorder

• insert audio as attachment
• async.
• have a placeholder spinner.

task

#29

orgmode editing

https://orgmode.org/org.html#Structure-Editing

M-enter and etc

Inspiration:

1. Obsidian's idea of core plugins

2. Neorg's module system

[ffricken]

I like the modular idea, we just need to be precise and concise about what our 'core' is.
Utilizing the organization to maintain other related plugins is a great idea as well!