diff options
-rw-r--r-- | TODO.md | 36 |
1 files changed, 0 insertions, 36 deletions
@@ -5,10 +5,6 @@ pagehistory: https://sledjhamr.org/cgit/notYetAnotherWiki/log/TODO.md | |||
5 | --- | 5 | --- |
6 | ## Do these | 6 | ## Do these |
7 | 7 | ||
8 | See the conversion therapy section below. | ||
9 | |||
10 | Add an Edit button that opens up the page in what ever wiki system it came from, for editing. | ||
11 | |||
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. | 8 | 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 changes, the docs that have that URL need to be redone. | 9 | - One quirk to watch for is if a URL path changes, the docs that have that URL need to be redone. |
14 | - pandoc is a lot slower though, so do this for sure when dealing with that. | 10 | - pandoc is a lot slower though, so do this for sure when dealing with that. |
@@ -21,38 +17,6 @@ The first link of the testing/even/deeper trail is still wrong. | |||
21 | 17 | ||
22 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. | 18 | Add atom feed for single page. Alas cgit only seems to have ATOM feed on the whole repo, not individual files. |
23 | 19 | ||
24 | ### conversion therapy | ||
25 | |||
26 | For importing from other systems, have a script that runs on that system | ||
27 | and creates a nYAWsite.lua structure, same as sites[], which nYAW then | ||
28 | downloads so it knows what web pages to convert. | ||
29 | |||
30 | Both ends need to know what they are converting - | ||
31 | - Other system end needs to know how to construct a nYAWsite.lua table from whatever format it's content is in. | ||
32 | - 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. | ||
33 | - nYAW system end needs to know how to convert and clean up the pages. | ||
34 | - nYAWsite.lua should include the name of the convert and clean up script that will be part of notYetAnotherWiki. | ||
35 | |||
36 | NOTE - security risks here - | ||
37 | - Automatically running Lua scripts from some other system. | ||
38 | - Letting the other system tell us what script to run. | ||
39 | |||
40 | 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. | ||
41 | |||
42 | #### conversion ROADMAP | ||
43 | put my table dumping stuff in it's own Lua library | ||
44 | |||
45 | use it to write the Foswiki and PmWiki install -> nYAWsite.lua scanners, which gets created in their respective directories | ||
46 | |||
47 | while notYetAnotherWiki is scanning for .md files to convert to HTML, if it comes across a nYAWsite.lua file in a directory, stop scanning for that directory and use that instead. | ||
48 | - this is where it needs to know where to get the web pages to convert, and how to convert | ||
49 | - - which is stored in the nYAWsite.lua file | ||
50 | - - 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 | ||
51 | - pandoc URL | cleanupscript > page.md | ||
52 | - page.md -> page.HTML as usual | ||
53 | |||
54 | figure out the nYAWsite.lua file downloading step later | ||
55 | |||
56 | 20 | ||
57 | 21 | ||
58 | ## Try out | 22 | ## Try out |