A bit of frontend implementation analysis todos

Rewritten-docs.md

@@ -283,6 +283,26 @@ Czech). Most notable features are following:
 
 @todo: what apis can be used on server frontend side, why rest in particular
 
+@todo: php frameworks, why nette
+
+@todo: what database can be used, how it is mapped and used within code
+
+@todo: authentication, some possibilities and describe used jwt
+
+@todo: solution of forgotten password, why this in particular
+
+@todo: rest api is used for report of backend state and errors, describe why and other possibilities (separate component)
+
+@todo: what files are stored in api, why there are duplicates among api and fileserver
+
+@todo: why are there instances and for which they can be used for, describe licences and its implementation
+
+@todo: groups and hierarchy, describe arbitrary nesting which should be possible within instance
+
+@todo: where is stored which workers can be used by supervisors and which runtimes are available, describe possibilities and why is not implemented automatic solution
+
+@todo: on demand loading of students submission, in-time loading of every other submission, why
+
 @todo: what technologies can be used on client frontend side, why react was used