djsudduth / djsudduth/keep-it-markdown
Feature Request: Allow custom template for note export
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 706
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
This is a big ask, but submitting just in case this would be valuable to other users.
The Issue
Currently, there is no way to customize the way markdown notes are generated for each note in Google Keep.
Proposed Solution
Using a templating engine like Jinja, users could be able to specify their own Jinja template to use for generating markdown notes.
For example:
Below is the default export format:
- I'd like to find system for (X)
- Is a hot dog a sandwich?
- Add questions to document
Created: 2024-01-15 05:40:34 --- Updated: 2024-01-15 05:40:34
[https://keep.google.com/#NOTE/1705297229969.1234682776](https://keep.google.com/#NOTE/1705297229969.1234682776)
Using a custom template, the user could have their markdown notes formatted in the following way if they prefer having the note metadata stored in markdown frontmatter:
---
created: 2024-01-15T05:40:34
updated: 2024-01-15T05:40:34
note-url: [https://keep.google.com/#NOTE/1705297229969.1234682776](https://keep.google.com/#NOTE/1705297229969.1234682776)
---
- I'd like to find system for (X)
- Is a hot dog a sandwich?
- Add questions to document
The template file for the above would look something like:
---
created: {{ created_at }}
updated: {{ updated_at }}
note-url: [{{ note_url }}]({{ note_url }})
---
{{ note_content }}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name any files, tests, or entry points. Begin by locating the note export code and its existing markdown formatting path, then determine how a user-supplied template would be configured and validated. Done means custom templates can render note content and metadata while the current default export remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100