Thank you for writing this and the original manifesto.
I'm reminded of my first website project (which called with ambition a "Portal"). It was called Ghostnetworks and, at the time as I was running between the school library and my home computer which I didn't have at the time, I managed to fit all of it on a floppy.
I feel "frameworks" by and large are contrary to the spirit of DIY and shoestring-budget construction, but to each is own. Hosted frameworks do substantially lower the cost to NeoCities as well, and subdirectories will certainly add to the flexibility. However you should be cautious of feature creep.
I've used Thingamablog ( http://thingamablog.com ) which enables static site/blog publishing, however it works via FTP. An API could be greatly beneficial to upload a site created with a tool like Thingamablog.
I do NOT believe FTP access is a good idea.
I feel the subdirectory, minfy, sorting problems can be greatly reduced with the introduction of an API. A desktop or mobile application that can upload content quickly will offload the burden of arranging the site away from you.
Hey, thanks for the response. As far as frameworks, I discuss in my post that I used a stripped down version of Foundation, but I don't feel this should be a requirement for anyone (I don't use a framework on my personal site, for instance)—it just lets you deploy quickly and is good for people who don't want to worry much about responsive-ness, they just want it to work.
I agree that FTP access would not be a good move on the part of neocities, I think they should just allow multi-file upload and directory support.
Multi-file upload will definitely be welcomed. E.G. When I was first setting up my site, I copy > pasted the index.html source to other files and changed the content. But then I realized I made a mistake, so now I had to go back and upload each and every file. I imagine, this is a slightly increased burden on NeoCities as well since they need to serve the upload page a bunch of times.
Authentication is easier. Application access becomes simpler as well, since even a JS tool running on a browser can connect and check your site. That also means not running an additional S/FTP server, which frees up resources to serve content (which would include responses to API requests).
Plus you get more fine-grained control of exactly which features are displayed to applications and this could include number of hits and other statistics (if they chose to implement it).
I'm reminded of my first website project (which called with ambition a "Portal"). It was called Ghostnetworks and, at the time as I was running between the school library and my home computer which I didn't have at the time, I managed to fit all of it on a floppy.
I feel "frameworks" by and large are contrary to the spirit of DIY and shoestring-budget construction, but to each is own. Hosted frameworks do substantially lower the cost to NeoCities as well, and subdirectories will certainly add to the flexibility. However you should be cautious of feature creep.
I've used Thingamablog ( http://thingamablog.com ) which enables static site/blog publishing, however it works via FTP. An API could be greatly beneficial to upload a site created with a tool like Thingamablog.
I do NOT believe FTP access is a good idea.
I feel the subdirectory, minfy, sorting problems can be greatly reduced with the introduction of an API. A desktop or mobile application that can upload content quickly will offload the burden of arranging the site away from you.