Lists:

• Starred labels
• Starred articles (limit to five or so)
• Last edited articles (limit to five or so)

Starred articles are listed in the sidebar, but there is also a virtual label "Starred".

Notes are shown in view mode by default. Need to click "edit" to change to markdown editing mode.

The /notes route lists all notes in a sortable table with title, last change, creation date, and labels.

Just provide the secret as an environment variable to the docker container. The login screen just asks for that secret and sends it with every request as a cookie.

To be eventually replaced by the full authorization system in #149.

Suggests a title ("Note created YYYY-MM-DD hh:mm") and automatically tags it with the "quick note" label.

Labels can have a name, color, and icon and can be listed in the sidebar if starred.

The default route / has a dashboard with useful functionality.

To be used in the sidebar, instead of fetching all notes.

Backend

Don't require a title on creation. If no explicit title was set, extract the title from the first header in the body or the first line, if there is no header. Do this on creation and changes.

If the header was set explicitly, set a flag in the DB (exposed via the API), and never change it automatically.

Frontend

The title is not editable by default, it only turns into an input field on click.

If there is no title, use 'Note from YYYY-mm-dd' as title. (Depends on #150.)

Use dbupgrade to automatically migrate the database when necessary when first opening it. Copy the old database to e.g. hej.sqlite.v3 when migrating hej.sqlite from version three and then try the upgrade.

Log the fact that the database was migrated and that the old database file can be removed. Use log level info, but specially configure the logger for this to show the message by default.

While an edited article will be saved and synced continuously, the app will create "checkpoints", which can be recalled later. A checkpoint will be created under the following circumstances:

• When the user hits Ctrl-s
• When the page was changed and the user stops input for five(?) minutes
• When the page was changed and the user leaves the article
• When the page was changed and the user opens the article (this can happen if the user closes a page without saving)

The user has the ability to remove checkpoints manually or the add a comment.

Replace the simple authorization system (#143) with a full system. Users and (encrypted) passwords are stored in the database. Session keys are generated using JWT tokens, no sessions are stored server-side. The JWT secret is stored in a file in the data directory.

Only save the note after 500ms of inactivity or 1m at the most.