Posted 09 April 2012 - 04:33 AM
As I guess that this happens from time to time to you guys around here, too, I wonder if it would make sense to collaborately work on a kind of manual document explaining key actions to be done for an editor. So there could be an open document or wiki providing texts in different languages and supportive images we all could use to e.g. turn it into a nice PDF or printed handbook (yes, some clients still like paging through paper) where we just have to replace images.
I don't think this work has to be done over and over again by each one of us for his own purpose. And I'm sure, all our clients would benefit from something like this. Also it would be a nice plus for everyone thinking about using PW the first time for a client project.
Posted 09 April 2012 - 07:43 AM
I had thought to tack on a /help section to the client site and use the csv importer to generate most of the topics and then modify as required.
Posted 09 April 2012 - 09:00 AM
Posted 09 April 2012 - 09:58 AM
If we decide to go a bit further and write instructions on how to deal with date fields etc then that's not a problem as anything that's not relevant can be deleted on a per-client basis, but takes longer to add it every time
Posted 10 April 2012 - 02:09 PM
We've been planning to build something like this for our clients, and most likely still will, considering that most of them speak Finnish (and not providing any kind of guide in their own language is hardly an option.)
Anyway -- a wiki would be nice way to deal with this considering collaboration, translations and everything. I'd definitely be interested in participating in creating the material.
Posted 11 April 2012 - 03:33 PM
Why not use processwire itself for the manual? If wiki-style-linking is desired, a textformatter could be used to achieve this.
Posted 11 April 2012 - 04:31 PM
Posted 12 April 2012 - 01:04 AM
When discussing the platform choices, keep in mind that most wiki platforms are exceptionally good at handling stuff like multiple editors, access restrictions and revision history - absolute necessities if we're going to have more people producing content. My experience comes mostly from MediaWiki, though, so that's what I'd suggest. It's ugly and kinda bloated but it does get things done
@charliez, that sounds great too, but wouldn't it provide some extra credibility if wiki site was running at manual.processwire.com or something similar? Though I'm not sure if this was what Ryan had in mind..
Posted 12 April 2012 - 02:18 AM
Is there not something we could do with ProcessWire? I mean, how complicated are we thinking of going with the manual? I get that wikis are great because you can discuss the page that's being edited, plus there is a revision history, but aside from the revision history (at the moment!) this sounds like something you could achieve with a PW install and the comments module. In terms of a login system it should be easy enough to tie in the forum logins with PW users.
I'd actually say that we shouldn't rush into this. I like the ideas and the momentum but I would hate for us to use the wrong software for the job (not saying my suggestion is right either, I just don't really like MediaWiki as it's old and slow - there are likely other, newer systems out there that should be considered if we were to go down the wiki route).
Edit: I was only really reading the last post so I didn't spot all the other comments saying "why not use PW?" until just now
Posted 12 April 2012 - 09:34 AM
PW was not designed as a Wiki, so it'll take some work to make it behave like one. That means somebody coding it before we can populate any content. I think the content has to come before the software here. (Though if the editors actually prefer to use PW as-is rather than a real Wiki, then we'll do that). If it were just me, I would probably use PW since I don't know my way around Wikis. But PW is a multi-purpose tool, and a Wiki is a single-purpose tool that designed for the exact purpose we are looking for.
Assuming a Wiki is a better environment for the editors, my opinion is that it's a good way to get things going short term. Moving it into a PW-powered Wiki longer term would be ideal. That way we could maximize the flexibility of the content… even providing JSON doc feeds to live PW installs like mentioned above.
If we've accomplished what we want to with the content, then converting and delivering it with PW will be the easy and fun part.
Posted 13 April 2012 - 08:58 AM
What do you guys think about hostname? Here are a few ideas:
- processwire.org (already setup)
- processwire.net (already setup)
- man.processwire.com (unix style)
Also tagged with one or more of these keywords: manual, clients, wish
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users