1 files changed, 30 insertions, 6 deletions

diff --git a/TODO.md b/TODO.md
index f421644..3453ba0 100644
--- a/TODO.md
+++ b/TODO.md
@@ -4,6 +4,7 @@ Make it perphekd!
 
 ## Do these
 
+Convert it to polygLua.
 
 It's all a bit too fragile, fix what I can.  Too many messes colliding.
 
@@ -17,7 +18,20 @@ Fix up linky conversion.  DONE, mostly.
 
 - Need to deal with real file name versus title.  Also symlink name not matching what it points to.
 
-Add atom feed for single page.  Alas cgit only seems to have ATOM feed on the whole repo, not individual files.
+Use the default.template that comes with nYAW if none is availaable.
+
+"collapsing headings" I guess that means click on a heading to hide / show the content under that heading.
+
+- 🙈
+- Should do that for the main content and the menu TOC.
+- Also allow editing just a section, a section being the bits between one heading and the next.
+- + 📝 ✒️✏️🖊️🖋 🖌️🖍️
+- + When someone starts editing, create pagename_draft.md and .HTML, and update those when they want to see a preview.
+- + Or pagename-heading_draft.md
+- + Use that draft.md file as a lock on editing that file / section.
+- + Have the hourly cron job remove any stale ones.
+
+Add ATOM feed for single page.  Alas cgit only seems to have ATOM feed on the whole repo, not individual files.
 
 - However, once timestamps are sorted, I can use that code to generate RSS and ATOM feeds, and create page histories using diffs.
 - Instead of an hourly cron job to update everything, see if I can hook
@@ -25,15 +39,16 @@ into Fos and Pm edit form's save function.  So when they save in the
 original wiki, the nyaw version gets updated, diffed, and ATOMed / RSSed.
 - + Actually a BFI method might do the trick, stick with doing a full scan 
 and only updating the stuff that needs it, likely that's only the page that just got saved.
+- git commit can have an arbitrary author / committer, so I can use that to make sure the person that actually made the change gets author / committer.
+- + There's also the email thing, but I don't want to spread email addresses around, not even sure we have them anyway.
 - Should also see if gitea can handle that, and if they want wiki content saved to git.
 
+Syntax highlighting in code blocks.  The highlight package looks promising, already had it installed on my desktop.
+
 ## Some ideas
 
-Mostly from something chomwitt deleted.
+Mostly from something chomwitt wrote -
 
-- "collapsing headings" I guess that means click on a heading to hide / show the content under that heading.
-- + 🙈
-- + Should do that for the main content and the menu TOC.
 - "validation", not sure exactly what that would validate.
 - I'll just quote some of the rest -
 
@@ -44,7 +59,6 @@ Mostly from something chomwitt deleted.
     ** for example search-completion to other workflows names-tags.
 ~~~
 
-- Syntax highlighting in code blocks.  The highlight package looks promising, already had it installed on my desktop.
 - Allow default.template files in sub folders.
 - Might be useful to automatically convert anything looking like a URL into a linky.
 
@@ -55,6 +69,10 @@ Automate symlinks.
 
 ## Try out
 
+lua-lpeg-patterns might be useful
+
+lua-luxio might be the wheel I'm reinventing?
+
 lua-wsapi-fcgi
 
 https://inclusive-components.design/tooltips-toggletips/ has some ideas about the "tooltip" HTML attribute, and what to do about it.  A rabbit hole that ends in javascript, but might be useful up to that point.
@@ -63,6 +81,12 @@ htmx
 
 cgit has Lua
 
+lua-gall for git stuff
+
+lua-lace for access control
+
+lua-unbound
+
 
 ## Member system