FEATURE REQUEST: better documentation of avaliable features / used technology

[tufo09]

Hi, ive just started using many-notes and it's generally amazing.
Apart from my other feature request another thing i found rather lacking is the available documentation.

Ive read in one of the other issues/discussions that documentation gets created gradually as the application evolves, which generally is a very nice approach, but i think there is some crucial information missing from the docs:

• which markdown flavor this is using, and which features "normal" markdown does not support are available.
  (i have just been reading how the default vault is written and have been trying out the buttons to see what they insert into the document to figure out what needs to be entered to for example achieve a link. this would be a very nice information to have, since specifically for local links a lot of other md editors [think obsidian, notion, logseq] use two square brackets for example.)
• maybe some advice to disable registrations after creating an initial user since otherwise random people could create accounts if one is running an publicly accessible instance.
  (whilst this definitely shouldn't be required, some people just do not think of it and i think it would be a nice touch)

I will try to familiarize myself with the codebase a bit when i have the time and will try to add such documentation myself, adhering to the guidelines outlined in the contributing page, if others agree that this is something that would be helpful.

:3

[brufdev]

My goal is to support the most common Markdown features. It uses GitHub Flavored Markdown (GFM), which is CommonMark plus a few extensions (tables, task lists, and strikethrough). Hashtags, angle-bracket autolinks, and internal links are also supported. The app is under ongoing development so the feature list may change in the future. The help modal might be a good place for this information, right? I still want to improve its UI though.

Regarding the registration toggle, I’ve already moved that option to the admin settings in the user menu. Maybe I could warn the first user to review the settings after registering?

[tufo09]

The help modal seems like a good place I think

Warning the first user would probably be the best option, so sounds good as well.

Thanks