Dear all,
I thought I had found a good hosted Wiki solution for our Pagoda Technical Manual. It appeared to provide lots of functionality, a clean design, and everything we needed to develop our manual with a small group of people.
However, when adding the fist two new members (and then trying it out myself, next to my admin account) the service appeared slow and unreliable. I even hit bugs. When I wrote to the organisation behind it, I found out they were overstretched. So all of a sudden committing all our data to that site seemed like a bad idea. For you old timers, a little like why we moved away from the original Yahoo groups: we would not be in control of our own destiny.
As a result I set up our own Wiki on our own website. That means we control and own the data, I make automatic backups every night, and we can always move to a different provider. However, in doing so I had to make a number of decisions.
First, the tool. I chose PmWiki (
http://www.pmwiki.org/). Instructions on how to edit and change text are here:
http://www.pmwiki.org/wiki/PmWiki/BasicEditing. Detailed documentation on everything is here:
http://www.pmwiki.org/wiki/PmWiki/DocumentationIndex.
Secondly, how to access this all. Currently,
only active Full Members of the Pagoda SL Group have WRITE access. Only they can add, or modify pages.
To get access you log-in with your e-mail address and the same password that you use to access our site http://www.sl113.org.
Note that all full members have this write access today. All members can READ the Technical Manual.
This was a conscious decision. In future we may allow:
all site members (both full and basic members) to have read access; Done already!- add, modify and delete access only to selected full members;
- everyone read access (i.e. even non-members of the group).
However, until we have a reasonable set of pages and until we have worked out, and implemented a workable structure, access is limited. It becomes a board decision on what we are actually going to do with regards to access. When some of our members are beginning to develop the manual, I shall be adding new technical features and helping in structuring the data. So I will create a mailing list of interested members and we will communicate on how we can put the manual together.
One of the goals is to ultimately create a manual that can be published -- and updated on a regular basis (I intend to make a snapshot of everything on the site every 6 months, except when the volume of change does not warrant this frequency), without keeping us stocks. New basic members or new Pagoda SL owners can always purchase this (up to date) manual for a fee. Full members can buy it at cost. We intend to use the on-demand publishing service
http://www.lulu.com for this.
To give you an idea, using Lulu.com and creating a A4 of Letter size book with 100 pages (with a plastiCoil binding for easy opening or a perfect bound volume) in black and white would have a member cost of €6 or $7. In colour it would cost €19 or $20. For twice the number of pages these fees would be slightly less than double. For non-members we would charge at least a markup of around one-years membership fee.
Ok, so what can you do today? If you are a full member, go here
http://www.sl113.org/wiki/pmwiki.php and log in using your e-mail address and password. Then have a look at Edit Notes (
http://www.sl113.org/wiki/pmwiki.php?n=Main.EditNotes) to see how that would work, and look at Engine Starting Aid (
http://www.sl113.org/wiki/pmwiki.php?n=Main.Engine-starting-aid-tour) to see how things could look in the manual. If you like, you can start adding sections to the manual. Do not worry if they are not perfect, we can change lots of things later on.
Remember, I will be adding lots of functionality to the site, such as: WikiTrails, to enable us to make a single manual from all these pages, PDF print functionality, so that we can generate PDF’s from the content for printing on
http://www.lulu.com, RSS feed generators so that you can keep track of which pages have been updated in the technical manual, and much more.
However, I’m already spending lots of time keeping the technology working. I need your help in providing the content.
I look forward to seeing you and seeing the technical manual change.
Peter
Check out
http://bali.esweb.nl for photographs of classic car events and my 1970 280SL