Meanwhile, the code text is a bit of a gooey html with a lot of duplicate-looking formatting, so the starting file isn't plain text, it's a web page, hence the thread title.
I think a key feature is for the app to read a proposed CSS design and intelligently find the (Spans?) etc where the text goes, so that outside of Zen Garden I can go to places on the net with free CSS templates etc.
Absolutely crucial is for the app to read the entire site folder with its nested items, figure out the whole linked site, and output a similar/paired site that "just works".
Maybe later on another task I'd want an upgrade/other app that adds chat boxes/site comments/etc. I don't know what that's about yet.
More essential features - I kinda dislike databases, because it's "all that data in a big blob". I did a modestly detailed study of "Tree Databases" a while back, and in a close call this one beat out the runner up because it created mostly intelligent child html files. (The other one felt like it was creating "data trap" because the output files were total gibberish.) But the html files are not quite perfect - "FreedomCody1436.html, IHateSOPA2334.html" etc. So the app should be able to do a mass file rename, check if there are any collisions, and if not, take all the numbers off of the ends.
It should be able to "clean up the code" on the child pages too. Another plus of the winning program is that all told, the pages aren't artificially obfuscated. They just offend my simplicity aesthetics by blasting out (thematically, the syntax is fake) "Format Arial 10 pt font left justified           position justified=1 border pixel=2" for every paragraph or such. I roughly think all that is the job of the CSS side, so I think the right result is just simple barebones html and <BR> breaks. (And even when I'm not using CSS then I let browsers pick their own defaults anyway so clean code is nicer on my eyes.)
More things - it should do light graphics handling to insert icons and text into the graphics, and be able to do extremely basic graphic management, maybe checking for missing graphics and making a list, and maybe a rough pixel count or something of the graphics width against a rough width of the text, so that when my long topic names trail in an ugly mess off the graphic I can get a list of which graphics to go open in an editor and try to expand or something.
Be ready for a couple more features as they pop up.
The intended license is one of the Creative Commons variants that I'll figure out later.
We'll have to check with Mouser on NANY to do dual credit so I am Commissioner (uh... or something) and the coder(s!?) get NANY credit (but I don't want to wait til December!) because the point of the site is creating fun software but I can't pay any of your "billable rates" - about all I can roughly allocate is the initial $50 and possibly another $50 on either part 2 or a second app.
Regards to all,