# TODO Make it perphekd! ## Do these Automate symlinks. - any .md.md file should be linked along with it's matching .md file if it's outside of Foswiki/ and PmWiki/. Syntax highlighting in code blocks. Other colour shenanigans. Might be useful to automatically convert anything looking like a URL into a linky. Check the timestamps on the files, only update if source is newer than destination. Meh, it's already 600 times faster than the pandoc version. - One quirk to watch for is if a URL path changes, the docs that have that URL need to be redone. - pandoc is a lot slower though, so do this for sure when dealing with that. - When scraping the web sites, they tend to be dynamically generated with no useful timestamp on them. - The web site scrape happens locally anyway, I can compare source file timestamps. Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. - git.devuan.org might have usable per page history. - However, once timestamps are sorted, I can use that code to generate (static?) RSS and ATOM feeds, and create page histories using diffs. Deal with complex directory trees. - /testing/even should display as even/deeper on the testing page, coz even/ has no files, but even/deeper does. - On the other hand, I could just create an empty page with the sub directories shown as usual. - Scanning /usr/share/doc on my super desktop with looots of software installed will be fun. - On the gripping hand, this is where we want empty directories to vanish. - SOOOOOOO don't show empty directories, but show their subs that have content, even if that sub is deep, but as per usual stop once we find a sub on that branch. EEEEW branches. Allow default.template files in sub directories. Bugs - - /users/dunno/Devuan Cluster.HTML   A very lengthy and complex document, I'll likely miss something, but chip away at the obvious. Lots of colour shenanigans. - unsorted/JensKorte/DevuanReleases_fos.HTML the header sorting links and colours on the table look tricky to unravel. Especially the extra row for Daedalus, just to change it's colour. - unsorted/Debdog_pm.HTML several tables of links encoded as code blocks, but they linkyness gets dropped, likely by pandoc. ## Try out htmx cgit has Lua ## User system Reuse the user system from SledjChisl. levels - - everyone - banned - reader - member - moderator - editor - admin - shell - root Everyone can read the pages, no need for an account. Banned people can't do squat, except maybe pester an admin once to start the unbanning process. When first registered, accounts are set to reader level. Initial verification by email. Readers can only edit their own profile. If an existing member vouches for a reader, they get promoted to member. Some invite system would count is vouching, but need to get secure invite credentials to someone outside the system. Members can chat, and create their own sandboxes that might get promoted by editors / moderators to proper content. Moderators can move things around, including to a spam/trash place. They can ban readers and members. Editors can edit any content, and move things around. They can't edit the site elements itself. So they can edit the site menu and structure of the content, but not the footer? Certainly can't edit any admin stuff. Admins are set by other admins. Admins can promote / demote people and content at any time. Admins can edit anything, including web editing of config files, and managing of modules. shell level means you have direct access to the files that are the web site, including configuration and modules. Likely this is the person that set the system up in the first place. Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level. Built in file browser might do the trick. Would be useful for content creators to to organise the content. Naturally should obey the permissions. root level is whoever controls the server things are running on. They can do anything at all.