Converting italics *somehow* to a format that can be stored and displayed. PHPOffice/PHPWord and having it as a word file makes the most sense. Maybe the best conversion here is to use i-brackets. I should do my first test with a *much* smaller document.
Dumping it into the database in a semi-automatic way. Once I figure out the format of the data, it's really just a matter of separating by chapter headings (maybe via converting the numbers 1-31 going backwards into something unused like $$$ and then splitting by that, then splitting again by \n***\n to get vignettes. Do one of these with the current version of the draft just to test it and the above, and test other stuff too (but save the code and steps in a comment) Then when the editor is done I can db dump and redo everything.
Conversion the other way somehow -- maybe I can paste RTF segments into word and then migrate it from there? Look into pasting entire HTML files -- if that's the case this would be super easy to do. Looks like it would work
Being able to add italics on the fly in the editors. contenteditable="true" seems to be the way to go here, with highlighted editing sticking i-tags around the highlighted block. Obviously will want to test this and also make sure that I can even *get* a highlighted bit within a div. And that copy and pasting works. And that I'm not just creating i-tags over i-tags. And something filters out weird instances of this. And then downstream it just turns it into i-brackets. Needs a live example and a bunch of testing basically. Having an i-mode would be nice but isn't explicitly required if I can just get this working, that will be good for now. Looks like a good solution. I need to research javascript's Selection object closer to figure out all the caveats. One neat consequence of this is italicizing/unitalicizing a word just from having the cursor inside it. Not necessary here, but possible!
Easy backups of *something*. Raw html files, if I'm dumping things that way maybe? Or zips? Or SQL data stuck in Gdrive. Not too worried about backing up the software, but definitely need to back up the data. Cronjob dumps and something as part of my pre-sleep routine would probably work best. There's a Gdrive api but it isn't worth it. I do need to be able to do this easily from my phone though.
POV handling, with more than one instance per chapter as an option. And then filtering accordingly -- multiples allowed. Seems easy enough. The order column is *super* important too for later rendering. Chapter + order should be the way things are laid out.
Additional tagging for characters present would be helpful. Can't do this automatically because of nicknames or whatever.
Search and search/replace functionality. Case sensitive as an option. Obviously need this, that's one of the main reasons I'm taking time out for this project. I'm thinking searches will turn up a bunch of results with the stuff highlighted, and then clicking will navigate there within the main view. My workflow will change a lot though because I can find things like 16-V very easily now. For replacement, I need to save the old version of everything in case I goof, and have some means of reversion.
Word count is just spaces + 1, right? Not super important really.
Version control for sanity purposes. I'm not worried about space.
If I get logged out or I can't reach the server for whatever reason, I should be able to recover the work I did.
Obviously it should be guarded though.
For new projects I need to be able to add vignettes and chapters both, including inline. And reorder things easily.
I need to think a lot about the UI here.
A little button for em dashes would be helpful. Next to the italics one probably.
Notes integration would be useful, and checklists too -- that's a future feature though. I can keep my workflow the way it is for now.
Aren't the quotes formatted kind of weird? And apostrophes too. Need to look into this, or just file a note to convert them later (assuming that's not going to be a giant manual pain in the ass, which it probably will be).
