diff options
| -rw-r--r-- | TODO.md | 41 |
1 files changed, 41 insertions, 0 deletions
| @@ -7,13 +7,54 @@ sourcecode: https://sledjhamr.org/cgit/notYetAnotherWiki/ | |||
| 7 | --- | 7 | --- |
| 8 | ## Do these | 8 | ## Do these |
| 9 | 9 | ||
| 10 | Clean up the favicon and logo stuff. | ||
| 11 | Have one in a root directory that the pages in sub directories point to, instead of the current symlinks. | ||
| 12 | Apply the same solution to default.template. | ||
| 13 | |||
| 14 | Clean up docs and bump to version 0.0. RELEASE!!!????!!!!???? | ||
| 15 | |||
| 16 | See the conversion therapy section below. | ||
| 17 | |||
| 10 | Add an Edit button that opens up the page in what ever wiki system it came from, for editing. | 18 | Add an Edit button that opens up the page in what ever wiki system it came from, for editing. |
| 11 | 19 | ||
| 12 | 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. | 20 | 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. |
| 13 | One quirk to watch for is if a URL path cahnges, the docs that have that URL need to be redone. | 21 | One quirk to watch for is if a URL path cahnges, the docs that have that URL need to be redone. |
| 22 | pandoc is a lot slower though, so do this for sure when dealing with that. | ||
| 14 | 23 | ||
| 15 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. | 24 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. |
| 16 | 25 | ||
| 26 | ### conversion therapy | ||
| 27 | |||
| 28 | For importing from other systems, have a script that runs on that system | ||
| 29 | and creates a nYAWsite.lua structure, same as sites[], which nYAW then | ||
| 30 | downloads so it knows what web pages to convert. | ||
| 31 | |||
| 32 | Both ends need to know what they are converting. | ||
| 33 | Other system end needs to know how to construct a nYAWsite.lua table from whatever format it's content is in. | ||
| 34 | Both system ends may need to cooperate to get nYAWsite.lua into a place nYAW can download. Or if running on the same system, drop it into the other system root. | ||
| 35 | nYAW system end needs to know how to convert and clean up the pages. | ||
| 36 | nYAWsite.lua should include the name of the convert and clean up script that will be part of notYetAnotherWiki. | ||
| 37 | |||
| 38 | NOTE - security risks here - | ||
| 39 | Automatically running Lua scripts from some other system. | ||
| 40 | Letting the other system tell us what script to run. | ||
| 41 | |||
| 42 | Alternative is to figure out what the nYAWsite.lua is by poking at the other system. Any given other system might not give that info easy. | ||
| 43 | |||
| 44 | ROADMAP - | ||
| 45 | put my table dumping stuff in it's own Lua library | ||
| 46 | use it to write the Foswiki and PmWiki install -> nYAWsite.lua scanners, which gets created in their respective directories | ||
| 47 | |||
| 48 | while notYetAnotherWiki is scanning for .md files to convert to | ||
| 49 | HTML, if it comes across a nYAWsite.lua file in a directory, | ||
| 50 | stop scanning for that directory and use that instead. | ||
| 51 | this is where it needs to know where to get the web pages to convert, and how to convert | ||
| 52 | which is stored in the nYAWsite.lua file | ||
| 53 | so we can start with a bare minimum one that just tells us the format, to be replaced by the newly generated one, which needs the format in it as well for next time | ||
| 54 | pandoc URL | cleanupscript > page.md | ||
| 55 | page.md -> page.HTML as usual | ||
| 56 | figure out the nYAWsite.lua file downloading step later | ||
| 57 | |||
| 17 | 58 | ||
| 18 | 59 | ||
| 19 | ## Try out | 60 | ## Try out |
