MyArtGallery 20240526 Major Update
Rejoice, MyAG users, as i have done something i thought was impossible: made the darn thing Actually Work! It took me a bit, but the entire structure was rewritten to be much safer, easier to maintain, and such and such. The idea remains the same, and the database format didn't change, but the execution is about 98% less sloppy now. You can get it here for free; deployment to Neocities takes 10 minutes at most, after which you get yourself an easily managed online gallery - deviantart style, but all yours.
For starters, here's the updated look of the editor - it has tabs now, which is much more convenient. Moreover, the artworks tab allows filtering by group to quickly access & edit your stuff! The item moving procedure became much less flashy and more robust, too.
The entire editing process has been streamlined, and now it's even less clunky than before. What also became streamlined is the page layout: the editor and the default pages now use semantic HTML and same standard CSS sheets that my other projects (and the upcoming neomanager) use. They're readable, lightweight, easily cuszomised.
Better yet, the way MyAG renders your gallery has been improved drastically. I noticed that people were struggling to style the default MyAG page, but MyAG wasn't working with anything but its default page. Now, rolling your own pages that use MyAG as a component is super easy - by just importing necessary scripts and styles, and adding a specific class to some container like a <div> - MyAG will automatically find it and render to it.
The list of default properties available as "easy customisations" to style has been reduced to basic spacing, colours, and such - located in "myag_user/style.css" as before. I figured that instead of making a complicated defaults system for inexperienced users to keep being inexperienced, a short set of defaults and a more open-ended structure is better; new CSS can now be added directly and gradually to the user style CSS file, and will not be affected by updates.
JS settings system has also been changed, so that you no longer have to be manually merging your custom settings with the newly introduced ones on every update. Settings are declared by the main code, not exposed to you the user - but may be overridden in "myag_user/settings.js". As before, the only two mandatory settings are URLs to some Neocities file editor windows to make the update process faster; changing anything else is not required.
Finally, i updated the goddarn manual to read like an actual manual and represent reality. So now, deploying MyAG via the step-by-step guide Actually Works. I added a guide on how to integrate MyAG to existing pages, or make a page that uses it from scratch, omitting the default pageset. I hope it helps - but as always, feedback and questions are appreciated.
P.S. neomanager is on its steady way to a stable version! I had to make MyAG sane first before returning to assuring safety and reliability of neomanager - some crappy MyAG subsystems started influencing my design decisions in a bad way, and i had to get rid of them first. Soon(tm)!















