If the browser tries to close the page, open a confirmation box if there is any unsaved text

Actually .default URLs shouldn't even exist.

When i use Ctrl+tab to switch tabs in Firefox, a tabulation character is added.

Currently a page that does not exist only shows "page not found" and does not accept the same keyboard shortcuts as the other pages.

Mermaid lets you create diagrams using text and code, inside Markdown.

We could add this as a .mermaid representation.

It would be nice to have a dark mode that simply uses the user’s preference.

No need for a UI to switch modes, it would just use the browser’s preference, using @media (prefers-color-scheme: dark) {.

(node) sys is deprecated. Use util instead.
Cakefile#1 is using require('sys') which has been deprecated in Node 4.0.0.

- {print} = require 'sys'
+ {print} = require 'util'

The idea would be to encrypt data in the browser, so that Edith never sees the passphrase, nor the secret that was typed.

If you don’t know the secret you can still clear the page so that nobody can “own” a page.

Usage

To encrypt: go to /foo.crypt (A) and type a secret in a password input at the top of the page. In the bottom textarea you can type a message, with the usual autosave on every keystroke (B). Instead of sending the typed text, the JavaScript will use the password to encrypt the data on the client-side and then send the encrypted blob of data to the server.

To decrypt: go to /foo.crypt again and you will see an empty passphrase input and encrypted text (C). On every keystroke in the password field, the data will be decrypted using that key (D). If you type the correct password that only you know (not even edith does), the data will be correctly decrypted (E). You can now read the text, or modify it and have it save on every keystroke.

If you visit the page (/foo) you would only see the encrypted text (F).

Behavior that has yet to be defined:

• What happens if you type text before typing a password?
• What happens when you change the key while you are editing the page?

Mockups

A (going to /foo.crypt):

🔑 [              ]

B (same page after filling both the page):

🔑 [•••••••       ]

This is the top secret message!

C (same page but with no key):

🔑 [              ]

���&�?=�;�⏾E��~�;�#�����-XdMe�e��X ���8[ДJME�����R��HvYO}�zJfs�+ئ�Q���T{���=�B�yu

D (same page but with wrong key):

🔑 [•             ]

M9�b�)����80��M-�\����a!~�"�ԶfE����:b\�Ô#�O�?I?�!#ƺ7c�qX�XHj���f�}pC��B���BΜR~3

E (same page but with wrong key):

🔑 [•••••••       ]

This is the top secret message!

F (going to /foo):

���&�?=�;�⏾E��~�;�#�����-XdMe�e��X ���8[ДJME�����R��HvYO}�zJfs�+ئ�Q���T{���=�B�yu

In order to render table for example

First title | Second title
------------- | ------------
data       | data     
data       | data     

It should be possible to show a representation of the page in 16x16 in the Favicon.

Write a user and a password at the top of the textarea to protect the page from editing with a HTTP Basic Auth.
A solution with one line :

user: my_username, password: my_password
content of the file…

A solution with a YAML Front Matter like Jekyll :

---
user: my_username
password: my_password

---
content of the file…

These credentials must be invisible from all others representations.

Reported in #8.

@Largo: You're right, it doesn't seem to work anymore since af802e3

It's a bug in edith.

Such lovely project need a docker image :)

Saving should be done as soon as you are back online so that you can use the app offline.

Instead of saving every 2 seconds Edith should try to save at every text input (keystroke), waiting for the previous ajax requests to be done to send a new one.

When writing

# This is a title

I would find useful for the generated code to be:

<h1 id="this-is-a-title">This is a title</h1>

On save, save the position where you were typing in the editor (for example in localStorage). This way, on page reload you can place the caret at the same place and continue typing where you were before.

Infinote protocol : http://infinote.org/
JavaScript implementation of the protocol : https://github.com/sveith/jinfinote

The ACE editor has good features for Edith including:

• syntax highlighting (if there is an extension like .js, .md, …)
• good looking themes
• indent and outdent with soft tabs
• highlight matching parentheses
• displays hidden characters
• drag and drop text using the mouse
• code folding
• multiple cursors and selections

In order to be a good fit for Edith, the editor should be as transparent as possible.

Collaborative editing should be impletemend as a no-ui lightweight text updates.

Possible services that provide collaborative editing:

• ProseMirror
• Tiptap
• Y.js

While any changes are waiting to be saved, change the favicon.

Use keyboard shortucts (for example ctrl-h or esc) to move from the edit page to the html and txt version.

Add a configuration constant that allows developers to specify a list of page names that cannot be modified.

This would help protect the index page from getting modified.