aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authordvs12024-12-22 03:25:18 +1000
committerdvs12024-12-22 03:25:18 +1000
commit1ed6c0b61ac80c2f1ba7b6e79eb75c4257cc4de9 (patch)
treed1538cfe32e22e1724df36066ea4fd5e8b91baef
parentLet's see if a symlink will keep the old cgit happy. (diff)
downloadnotYetAnotherWiki-1ed6c0b61ac80c2f1ba7b6e79eb75c4257cc4de9.zip
notYetAnotherWiki-1ed6c0b61ac80c2f1ba7b6e79eb75c4257cc4de9.tar.gz
notYetAnotherWiki-1ed6c0b61ac80c2f1ba7b6e79eb75c4257cc4de9.tar.bz2
notYetAnotherWiki-1ed6c0b61ac80c2f1ba7b6e79eb75c4257cc4de9.tar.xz
Try it the other way, cgit is fussy about it's README.
-rw-r--r--[l---------]README68
l---------[-rw-r--r--]README.md68
-rwxr-xr-xnotYetAnotherWiki.lua2
3 files changed, 69 insertions, 69 deletions
diff --git a/README b/README
index 1cfe87d..334cea4 120000..100644
--- a/README
+++ b/README
@@ -1 +1,67 @@
1/home/dvs1/AboutMe/notYetAnotherWiki/README.md \ No newline at end of file 1---
2favicon: cartdave_favicon.png
3pagetitle: "notYetAnotherWiki is not another wiki, at least not yet. It'll be much more than that, eventually."
4author: onefang
5feedatom: https://sledjhamr.org/cgit/notYetAnotherWiki/atom
6history: https://sledjhamr.org/cgit/notYetAnotherWiki/log/index.md
7sourcecode: https://sledjhamr.org/cgit/notYetAnotherWiki/
8---
9
10notYetAnotherWiki is not another wiki, at least not yet. It'll be much
11more than that, eventually.
12
13So to start with it's not a wiki. It's currently a way to create a web
14site with CommonMark wiki markup, using git to update the content.
15
16So it's not a wiki, yet.
17
18Next comes accounts and online editing of content with the web pages.
19It'll then barely be a wiki.
20
21The missing bit is talk pages, which requires some sort of archiving chat
22system built into the thing. Now it's Yet Another Wiki.
23
24Finally comes the magic, so it's "not Yet Another Wiki", it's much more
25than that.
26
27A web forum is basically a web based chat system with archiving. We got
28that now, we can just say it's a web forum as well. Just leave off the
29wiki page bit.
30
31Only difference between an instant messaging system and a web forum is
32how fast it runs. So just make this fast, then we can call it an instant
33messaging system.
34
35Put email behind a web forum, you got a mailing list with a web archive.
36
37An issue tracker is basically a wiki type page with the forum style
38messages, and often an email control system. Only that last bit needs to
39be added.
40
41A lot of projects will put together all of these things to support their
42users. Different systems, different accounts, same info. Too much "Oh,
43that's in the forum somewhere" on the mailing list or whatever.
44
45notYetAnotherWiki puts it all together as a single system, with multiple
46ways of using it depending on what the users want, and ways of organising
47the useful info that makes it's way into the system one way or another.
48
49Someone comes into your chat system, asking for help, within minutes
50people are helping out and come up with a working solution. After a few
51other people turn up with the same problem, the existing conversations
52are moved to the decumentation section, where the original participants
53and others can polish it into proper documentation about solving what has
54suddenly become a common problem. Every one knows where to find it, on
55the one system. They can chat about it, on the one system.
56
57## What does it do already?
58
59Currently it'll scan the current directory and subdirectories rooking for
60.md files in CommonMark syntax. This should cover some MarkDown
61variations. Then it produces .HTML files converted from these .md files,
62and links them all together into a web site.
63
64git is used to store the .md files, and provides edit history. Added on
65the footer is links to cgit, which is used to store the files in git on
66your server. This provides acces to the source code, history, and ATOM
67feed for the site.
diff --git a/README.md b/README.md
index 334cea4..100b938 100644..120000
--- a/README.md
+++ b/README.md
@@ -1,67 +1 @@
1--- README \ No newline at end of file
2favicon: cartdave_favicon.png
3pagetitle: "notYetAnotherWiki is not another wiki, at least not yet. It'll be much more than that, eventually."
4author: onefang
5feedatom: https://sledjhamr.org/cgit/notYetAnotherWiki/atom
6history: https://sledjhamr.org/cgit/notYetAnotherWiki/log/index.md
7sourcecode: https://sledjhamr.org/cgit/notYetAnotherWiki/
8---
9
10notYetAnotherWiki is not another wiki, at least not yet. It'll be much
11more than that, eventually.
12
13So to start with it's not a wiki. It's currently a way to create a web
14site with CommonMark wiki markup, using git to update the content.
15
16So it's not a wiki, yet.
17
18Next comes accounts and online editing of content with the web pages.
19It'll then barely be a wiki.
20
21The missing bit is talk pages, which requires some sort of archiving chat
22system built into the thing. Now it's Yet Another Wiki.
23
24Finally comes the magic, so it's "not Yet Another Wiki", it's much more
25than that.
26
27A web forum is basically a web based chat system with archiving. We got
28that now, we can just say it's a web forum as well. Just leave off the
29wiki page bit.
30
31Only difference between an instant messaging system and a web forum is
32how fast it runs. So just make this fast, then we can call it an instant
33messaging system.
34
35Put email behind a web forum, you got a mailing list with a web archive.
36
37An issue tracker is basically a wiki type page with the forum style
38messages, and often an email control system. Only that last bit needs to
39be added.
40
41A lot of projects will put together all of these things to support their
42users. Different systems, different accounts, same info. Too much "Oh,
43that's in the forum somewhere" on the mailing list or whatever.
44
45notYetAnotherWiki puts it all together as a single system, with multiple
46ways of using it depending on what the users want, and ways of organising
47the useful info that makes it's way into the system one way or another.
48
49Someone comes into your chat system, asking for help, within minutes
50people are helping out and come up with a working solution. After a few
51other people turn up with the same problem, the existing conversations
52are moved to the decumentation section, where the original participants
53and others can polish it into proper documentation about solving what has
54suddenly become a common problem. Every one knows where to find it, on
55the one system. They can chat about it, on the one system.
56
57## What does it do already?
58
59Currently it'll scan the current directory and subdirectories rooking for
60.md files in CommonMark syntax. This should cover some MarkDown
61variations. Then it produces .HTML files converted from these .md files,
62and links them all together into a web site.
63
64git is used to store the .md files, and provides edit history. Added on
65the footer is links to cgit, which is used to store the files in git on
66your server. This provides acces to the source code, history, and ATOM
67feed for the site.
diff --git a/notYetAnotherWiki.lua b/notYetAnotherWiki.lua
index 977a117..e7f0873 100755
--- a/notYetAnotherWiki.lua
+++ b/notYetAnotherWiki.lua
@@ -117,7 +117,7 @@ end
117 117
118local directory = arg[1] 118local directory = arg[1]
119if nil == directory then directory = '.' end 119if nil == directory then directory = '.' end
120for l in io.popen('find ' .. directory .. ' -name "*.md" -type f -printf "%P\n"'):lines() do 120for l in io.popen('find ' .. directory .. ' -name "*.md" -type f,l -printf "%P\n"'):lines() do
121 local dir = '' 121 local dir = ''
122 local files, subs = {}, {} 122 local files, subs = {}, {}
123 local c, parent = 1, '' 123 local c, parent = 1, ''