1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
here is the websocket app: https://github.com/grothedev/websocket-template
run the server and set the WS_URL env variable of this laravel app appropriately
#### TODO:
- a site statistics page
- total visits, visit frequency, country of recent visits, average location makeup,
- current connections, time spent on site (average, min, max, )
-
- views
- want to make a view that consolidates the two styles of files and links
- links
- add additional metadata on hover
- files
- htmx
- make /htmx/{thing}/{param} routes for sub-elements of pages? e.g. /links/# gives a blade page, but /htmx/links/# would give just the single html element (and maybe would be queried by /links/#, though it might be silly to have to require a double request like that, when the php can already do the necessary processing in blade)
- error handling and validation for file upload and everything
- writing
- fix the preview which stopped working
- add drag-drop file to upload and then generate appropriate html to embed that file
- auto capitalization https://marked.js.org/using_pro
- index filter and sort
- FIX THE CSS WTF
- quickbuttons, for adding in snippets of things like embedding an image
- update markup on a timer instead of every character (and/or see if i can prevent it from making unnecessary network requests like loading embedded files)
- each user has their own status pane html element
- and user conglomerate's (e.g. a band) can have their own full html page
- the html is stored in db
- look into forwarding routes to containers for security and better route networkning
- tests
- test the return code and body of every route to make sure no error introduced
- general
- import any model via json
- break out the canvas cursor renderer from main.js
- and more js organizination: treat each js file like a "plugin" that provides some functionality to some page if the page has the appropriate elements on it. define what dom elems are needed and optional for some js file. this way it won't be coupled with the page as much.
- homepage image
the entire webapp downloads and stores an application in the users localstorage.
if connection lost, user can still interact with the website services while offline.
in addition, other users who are on the same network can still use the webapp if it was downloaded to their localstorage.
- user dashboard system
|
