Ideas #1

New Issue

ardent · 2023-03-29T15:07:29+02:00

ardent commented

2023-03-29 15:07:29 +02:00

Use git to store the changes
-Allows for being 'stateless' if no authentication is needed
https://github.com/czproject/git-php
Can make a commit for every change
-If single repo, add filename to commit message so can find all changes for specific file
Allow for changing branches to keep better track?
-Disadvantage is that it can't be done on a per-file basis
If per file repository is created, easier to keep track of changes and makes multiple branches a lot easier. Can also keep metadata in repository. If you want to push all the repositories it can become very cluttered

Raw rendering of HTML pages (return correct filetype), also allows for replacing certain special tokens with (full) raw url to other snips.

Can use highlightjs to render code nicely (based on extension?):
https://highlightjs.org/

Use git to store the changes -Allows for being 'stateless' if no authentication is needed https://github.com/czproject/git-php Can make a commit for every change -If single repo, add filename to commit message so can find all changes for specific file Allow for changing branches to keep better track? -Disadvantage is that it can't be done on a per-file basis If per file repository is created, easier to keep track of changes and makes multiple branches a lot easier. Can also keep metadata in repository. If you want to push all the repositories it can become very cluttered Raw rendering of HTML pages (return correct filetype), also allows for replacing certain special tokens with (full) raw url to other snips. Can use highlightjs to render code nicely (based on extension?): https://highlightjs.org/

ardent commented

2023-03-29 15:12:07 +02:00

Comment system? This can perhaps be done as metadata as well, keep comments in separate file can be nice if each file/project is separate repository.