diff options
| author | dvs1 | 2025-03-18 15:33:41 +1000 |
|---|---|---|
| committer | dvs1 | 2025-03-18 15:33:41 +1000 |
| commit | 0766d4e8568373d26a0d4dc42e2149efc8d035d1 (patch) | |
| tree | 6514caa499f28b17f7c155998112241cfdeef280 | |
| parent | Add a cleaning script. (diff) | |
| download | notYetAnotherWiki-0766d4e8568373d26a0d4dc42e2149efc8d035d1.zip notYetAnotherWiki-0766d4e8568373d26a0d4dc42e2149efc8d035d1.tar.gz notYetAnotherWiki-0766d4e8568373d26a0d4dc42e2149efc8d035d1.tar.bz2 notYetAnotherWiki-0766d4e8568373d26a0d4dc42e2149efc8d035d1.tar.xz | |
Minor TODO tweaks.
| -rw-r--r-- | TODO.md | 8 |
1 files changed, 4 insertions, 4 deletions
| @@ -16,10 +16,10 @@ Fix up linky conversion. DONE, mostly. | |||
| 16 | 16 | ||
| 17 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. | 17 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. |
| 18 | 18 | ||
| 19 | - However, once timestamps are sorted, I can use that code to generate (static?) RSS and ATOM feeds, and create page histories using diffs. | 19 | - However, once timestamps are sorted, I can use that code to generate RSS and ATOM feeds, and create page histories using diffs. |
| 20 | - Instead of an hourly cron job to update everything, see if I can hook | 20 | - Instead of an hourly cron job to update everything, see if I can hook |
| 21 | into Fos and Pm edit form's save function. So when they save in the | 21 | into Fos and Pm edit form's save function. So when they save in the |
| 22 | original wiki, the nyaw version gets updated, diffed, and RSSed. | 22 | original wiki, the nyaw version gets updated, diffed, and ATOMed / RSSed. |
| 23 | - Should also see if gitea can handle that, and if they want wiki content saved to git. | 23 | - Should also see if gitea can handle that, and if they want wiki content saved to git. |
| 24 | 24 | ||
| 25 | It's all a bit too fragile, fix what I can. Too many messes colliding. | 25 | It's all a bit too fragile, fix what I can. Too many messes colliding. |
| @@ -41,8 +41,8 @@ Mostly from something chomwitt deleted. | |||
| 41 | ~~~ | 41 | ~~~ |
| 42 | 42 | ||
| 43 | - Syntax highlighting in code blocks. | 43 | - Syntax highlighting in code blocks. |
| 44 | - Might be useful to automatically convert anything looking like a URL into a linky. | ||
| 45 | - Allow default.template files in sub directories. | 44 | - Allow default.template files in sub directories. |
| 45 | - Might be useful to automatically convert anything looking like a URL into a linky. | ||
| 46 | 46 | ||
| 47 | Automate symlinks. | 47 | Automate symlinks. |
| 48 | 48 | ||
| @@ -102,6 +102,6 @@ site, including configuration and modules. Likely this is the person | |||
| 102 | that set the system up in the first place. | 102 | that set the system up in the first place. |
| 103 | 103 | ||
| 104 | Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level. | 104 | Admin should have access to everything that shell level has, but there's always things need tweaking at some lower level. |
| 105 | Built in file browser might do the trick. Would be useful for content creators to to organise the content. Naturally should obey the permissions. | 105 | Built in file browser might do the trick. Would be useful for content creators to organise the content. Naturally should obey the permissions. |
| 106 | 106 | ||
| 107 | root level is whoever controls the server things are running on. They can do anything at all. | 107 | root level is whoever controls the server things are running on. They can do anything at all. |