aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/TODO.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--TODO.md77
1 files changed, 49 insertions, 28 deletions
diff --git a/TODO.md b/TODO.md
index dc5a44b..3453ba0 100644
--- a/TODO.md
+++ b/TODO.md
@@ -4,34 +4,51 @@ Make it perphekd!
4 4
5## Do these 5## Do these
6 6
7Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. 7Convert it to polygLua.
8 8
9- However, once timestamps are sorted, I can use that code to generate (static?) RSS and ATOM feeds, and create page histories using diffs. 9It's all a bit too fragile, fix what I can. Too many messes colliding.
10
11Flock it.
12
13Some sort of search system.
14
15A member system, and edit / manage system for their pages.
10 16
11Fix up linky conversion. DONE, mostly. 17Fix up linky conversion. DONE, mostly.
12 18
13- This is the "page moved" problem, but now it's "page copied" and "page linked", a generic solution might work.
14- Rethink this, I might be going the wrong way.
15- Need to deal with real file name versus title. Also symlink name not matching what it points to. 19- Need to deal with real file name versus title. Also symlink name not matching what it points to.
16- . Hmmm, might it be good policy to have a single canonical context for each page? The "real URL" .md.md thing?
17- . Loop through the manually placed symlinks, adjusting "real URL" as we go.
18- + What to do about mulitple symlinks pointing to the same page? Compare timestamps, most recent wins.
19 20
20Deal with complex directory trees. 21Use the default.template that comes with nYAW if none is availaable.
22
23"collapsing headings" I guess that means click on a heading to hide / show the content under that heading.
21 24
22- /testing/even should display as even/deeper on the testing page, coz even/ has no files, but even/deeper does. 25- 🙈
23- On the other hand, I could just create an empty page with the sub directories shown as usual. 26- Should do that for the main content and the menu TOC.
24- Scanning /usr/share/doc on my super desktop with looots of software installed will be fun. 27- Also allow editing just a section, a section being the bits between one heading and the next.
25- On the gripping hand, this is where we want empty directories to vanish. 28- + 📝 ✒️✏️🖊️🖋 🖌️🖍️
26- 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. 29- + When someone starts editing, create pagename_draft.md and .HTML, and update those when they want to see a preview.
30- + Or pagename-heading_draft.md
31- + Use that draft.md file as a lock on editing that file / section.
32- + Have the hourly cron job remove any stale ones.
27 33
34Add ATOM feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files.
35
36- However, once timestamps are sorted, I can use that code to generate RSS and ATOM feeds, and create page histories using diffs.
37- Instead of an hourly cron job to update everything, see if I can hook
38into Fos and Pm edit form's save function. So when they save in the
39original wiki, the nyaw version gets updated, diffed, and ATOMed / RSSed.
40- + Actually a BFI method might do the trick, stick with doing a full scan
41and only updating the stuff that needs it, likely that's only the page that just got saved.
42- 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.
43- + There's also the email thing, but I don't want to spread email addresses around, not even sure we have them anyway.
44- Should also see if gitea can handle that, and if they want wiki content saved to git.
45
46Syntax highlighting in code blocks. The highlight package looks promising, already had it installed on my desktop.
28 47
29## Some ideas 48## Some ideas
30 49
31Mostly from something chomwitt deleted. 50Mostly from something chomwitt wrote -
32 51
33- "collapsing headings" I guess that means click on a heading to hide / show the content under that heading.
34- + Should do that for the main content and the menu TOC.
35- "validation", not sure exactly what that would validate. 52- "validation", not sure exactly what that would validate.
36- I'll just quote some of the rest - 53- I'll just quote some of the rest -
37 54
@@ -42,16 +59,8 @@ Mostly from something chomwitt deleted.
42 ** for example search-completion to other workflows names-tags. 59 ** for example search-completion to other workflows names-tags.
43~~~ 60~~~
44 61
45- Syntax highlighting in code blocks. 62- Allow default.template files in sub folders.
46- Might be useful to automatically convert anything looking like a URL into a linky. 63- Might be useful to automatically convert anything looking like a URL into a linky.
47- Allow default.template files in sub directories.
48
49Check the timestamps on the files, only update if source is newer than destination. Meh, it's already 600 times faster than the pandoc version.
50
51- One quirk to watch for is if a URL path changes, the docs that have that URL need to be redone.
52- pandoc is a lot slower though, so do this for sure when dealing with that.
53- When scraping the web sites, they tend to be dynamically generated with no useful timestamp on them.
54- The web site scrape happens locally anyway, I can compare source file timestamps.
55 64
56Automate symlinks. 65Automate symlinks.
57 66
@@ -60,16 +69,28 @@ Automate symlinks.
60 69
61## Try out 70## Try out
62 71
72lua-lpeg-patterns might be useful
73
74lua-luxio might be the wheel I'm reinventing?
75
76lua-wsapi-fcgi
77
63https://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. 78https://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.
64 79
65htmx 80htmx
66 81
67cgit has Lua 82cgit has Lua
68 83
84lua-gall for git stuff
85
86lua-lace for access control
87
88lua-unbound
89
69 90
70## User system 91## Member system
71 92
72Reuse the user system from SledjChisl. 93Reuse the member system from SledjChisl.
73 94
74levels - 95levels -
75 96
@@ -111,6 +132,6 @@ site, including configuration and modules. Likely this is the person
111that set the system up in the first place. 132that set the system up in the first place.
112 133
113Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level. 134Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level.
114Built in file browser might do the trick. Would be useful for content creators to to organise the content. Naturally should obey the permissions. 135Built in file browser might do the trick. Would be useful for content creators to organise the content. Naturally should obey the permissions.
115 136
116root level is whoever controls the server things are running on. They can do anything at all. 137root level is whoever controls the server things are running on. They can do anything at all.