Update Documentation for 'Open Daily Note' Feature

[jsjoeio]

Things we should document for this new feature:

• what it is
• how to change the Filename format
• how to change the File extension
• how to change the Title format of the daily note
• how to set the Daily notes directory

Questions:

• do we remove it from the Roadmap after implementation?
• do we remove the implementation page?

Based on how the docs are set up, my best guess is this would fall under a Recipe. Curious to hear thoughts from @jevakallio

Related:

• Add 'Open Daily Note' Command #54
• Add open daily note base feature #79

[juanfrank77]

Hey guys!

Just throwing some ideas here.

• Would it be good to have a dedicated section for the note's settings on the VS Code UI so that people could change them there instead of going to the .vscode/settings.json?
• Make the documentation as clear as possible so that a non-dev person would know where to go and what options to enable/disable according to preference.

I think that once is completed, removing it from the roadmap and also the implementation page would be a good idea (unless the intention is to let it there as a reminder of how far the project has gone 😉).

Also agree that I would be better being a Recipe under the 'write' category. Maybe something like 'Configure your daily notes'

[jsjoeio]

Would it be good to have a dedicated section for the note's settings on the VS Code UI so that people could change them there instead of going to the .vscode/settings.json?

Good idea! You can use the Settings UI with how it's implemented right now. Here's what it will look like.

But if we find it hard for non-devs, we can always brainstorm how to improve the UX. For v1, this seems like it should get the job done.

Make the documentation as clear as possible so that a non-dev person would know where to go and what options to enable/disable according to preference.

Agreed! Definitely something we want to keep in mind.

Thanks for adding your input! 🙏🏼 Really helpful to have a second opinion.

[riccardoferretti]

@ingalless I believe this has now been sorted, can you double check and close the issue if that's the case? thanks!

[ingalless]

Looks great to me @riccardoferretti! Thanks @jsjoeio and @juanfrank77 for your input 💪🏻