aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/TODO.md
diff options
context:
space:
mode:
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md61
1 files changed, 25 insertions, 36 deletions
diff --git a/TODO.md b/TODO.md
index fc3ffff..8aa73b8 100644
--- a/TODO.md
+++ b/TODO.md
@@ -4,55 +4,34 @@ Make it perphekd!
4 4
5## Do these 5## Do these
6 6
7Automate symlinks.
8
9- any .md.md file should be linked along with it's matching .md file if it's outside of Foswiki/ and PmWiki/.
10
11Other colour shenanigans.
12 7
13TOC 8Fix up linky conversion. DONE, mostly.
14 9
15- Maybe have it on the left, as the sub menu of the current page's menu item, automatically generated from the $body$ headings. 10- Need to deal with real file name versus title. Also symlink name not matching what it points to.
16- Sub headings get sub menus etc.
17 11
18Check the timestamps on the files, only update if source is newer than destination. Meh, it's already 600 times faster than the pandoc version. 12Some sort of search system.
19 13
20- One quirk to watch for is if a URL path changes, the docs that have that URL need to be redone. 14A member system, and edit / manage system for their pages.
21- pandoc is a lot slower though, so do this for sure when dealing with that.
22- When scraping the web sites, they tend to be dynamically generated with no useful timestamp on them.
23- The web site scrape happens locally anyway, I can compare source file timestamps.
24 15
25Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. 16Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files.
26 17
27- git.devuan.org might have usable per page history. 18- However, once timestamps are sorted, I can use that code to generate RSS and ATOM feeds, and create page histories using diffs.
28- However, once timestamps are sorted, I can use that code to generate (static?) RSS and ATOM feeds, and create page histories using diffs. 19- Instead of an hourly cron job to update everything, see if I can hook
29 20into Fos and Pm edit form's save function. So when they save in the
30Deal with complex directory trees. 21original wiki, the nyaw version gets updated, diffed, and ATOMed / RSSed.
31 22- Should also see if gitea can handle that, and if they want wiki content saved to git.
32- /testing/even should display as even/deeper on the testing page, coz even/ has no files, but even/deeper does.
33- On the other hand, I could just create an empty page with the sub directories shown as usual.
34- Scanning /usr/share/doc on my super desktop with looots of software installed will be fun.
35- On the gripping hand, this is where we want empty directories to vanish.
36- 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.
37
38FIXTHEM: If there's a single word and period at the beginning of a line, it gets turned into a list, or list item by lunamark at the final Parse stage.
39 23
24It's all a bit too fragile, fix what I can. Too many messes colliding.
40 25
41## Some ideas 26## Some ideas
42 27
43Mostly from something chomwitt deleted. 28Mostly from something chomwitt deleted.
44 29
45- A toolbar is mentioned, which is what I'm half way through creating with those hamburger / sunglasses icons, they are a bar of tools.
46- + "everything" and "unsorted" as toolbar icons.
47- + Maybe "users"?
48- Maybe tabs as well as a toolbar, for the list of sub directories.
49- Syntax highlighting in code blocks.
50- Allow default.template files in sub directories.
51- Might be useful to automatically convert anything looking like a URL into a linky.
52- "collapsing headings" I guess that means click on a heading to hide / show the content under that heading. 30- "collapsing headings" I guess that means click on a heading to hide / show the content under that heading.
31- + 🙈
53- + Should do that for the main content and the menu TOC. 32- + Should do that for the main content and the menu TOC.
54- "validation", not sure exactly what that would validate. 33- "validation", not sure exactly what that would validate.
55- I'll just quote the entire rest - 34- I'll just quote some of the rest -
56 35
57~~~ 36~~~
58 !!! co-editing 37 !!! co-editing
@@ -61,9 +40,19 @@ Mostly from something chomwitt deleted.
61 ** for example search-completion to other workflows names-tags. 40 ** for example search-completion to other workflows names-tags.
62~~~ 41~~~
63 42
43- Syntax highlighting in code blocks. The highlight package looks promising, already had it installed on my desktop.
44- Allow default.template files in sub folders.
45- Might be useful to automatically convert anything looking like a URL into a linky.
46
47Automate symlinks.
48
49- any .md.md file should be linked along with it's matching .md file if it's outside of Foswiki/ and PmWiki/.
50
64 51
65## Try out 52## Try out
66 53
54lua-wsapi-fcgi
55
67https://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. 56https://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.
68 57
69htmx 58htmx
@@ -71,9 +60,9 @@ htmx
71cgit has Lua 60cgit has Lua
72 61
73 62
74## User system 63## Member system
75 64
76Reuse the user system from SledjChisl. 65Reuse the member system from SledjChisl.
77 66
78levels - 67levels -
79 68
@@ -115,6 +104,6 @@ site, including configuration and modules. Likely this is the person
115that set the system up in the first place. 104that set the system up in the first place.
116 105
117Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level. 106Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level.
118Built in file browser might do the trick. Would be useful for content creators to to organise the content. Naturally should obey the permissions. 107Built in file browser might do the trick. Would be useful for content creators to organise the content. Naturally should obey the permissions.
119 108
120root level is whoever controls the server things are running on. They can do anything at all. 109root level is whoever controls the server things are running on. They can do anything at all.