|
|
|
|
|
|
by verusfossa
3804 days ago
|
|
|
Neat project, good luck with it. I think I'll stick with Hugo, it's freaky-fast and postcss breaking CSS into an AST makes it really modular. Power moved from js into css which I'm okay with (and browsers are too). As for git. The reason these blogs are so heavy is because editing text files for most people requires a text editor interface on the http which in turn means you need dynamic content whicn in tern means you need a database which in tern means you need a way to submit this code so php which in t... and down the rabbit hole goes. If you get rid of the "editing files requires a text editor" part, then your site is easy and maintainable. Git I think is a bit more programmer-focused of an api for random blogger joe, but a light wrapper might work. Maybe something like emailing a server with subject "POST: title of blog post" body "text for post" and having the server grab that data from the email, if it came from an allowed user, throwing it into the posts/ folder, git committing it and then deploying it to an apache server on itself. Actions like "delete", "edit" would just search for files with the exact name as in the subject and do the required git action on it. Something like this could probably work. Email clients already have the text editor users want, why rebuild the wheel? If there was someway to wrap this all up without requiring users actually host their own entire email, I think it would be nice. I think teaching your mom git is a pipe dream unfortunately even if it would fix the Copy-of-Copy-of-Birthday-List_OLD2.txt problem. |
|
|
I wouldn't put too much faith in email clients html output being sane, or consistent across clients.
You could do it with markdown, but then you're still having to teach them markdown.