Test Notes
I have set up the note list to be sorted by update time.
Tag optimization is currently underway.
One has been pushed to GitHub, the other published to Cloudflare.
Using Cursor
I have used Cursor to optimize the app.
It took several hours.
Optimized time sorting, optimized the issue of the keyboard obscuring the input field, and optimized the issue of adding attachments like images and files to the timeline.
Now continuing to optimize notes.
Why Tags Matter
Tags are not only a user-interface feature. They also help the publishing workflow decide where a note belongs after it becomes a blog post. A note about Astro should not be mixed with a note about Raspberry Pi or YouTube automation unless the relationship is intentional.
For SEO, this matters because search engines read internal links, headings, category pages, and repeated topic signals. If tags are stable, the app can map notes to better blog categories and the generated article can appear under the correct topic page.
Next Steps
The next useful improvement is to store both a display tag and a normalized slug. The display tag can remain readable in the app, while the slug can be used for URLs, filters, and future automated publishing rules.
I also want to record whether a note has already been published. That prevents duplicate posts and makes it easier to update an existing article instead of creating a new URL for every small edit.
Publishing Rule
A useful rule is to separate private app tags from public blog topics. Private tags can describe workflow states such as draft, reviewed, published, or needs image. Public topics should describe the subject readers search for, such as Astro, Raspberry Pi, ESP32, AI tools, or YouTube.
Keeping those two layers separate will make the app easier to use while also producing cleaner category pages on the blog.