> As I understand it, a single editor to a page? He or she has > the sole responsibility of fixing typos, maintaining accuracy > in rewrites of the content--it seems like a lot of > responsibility and a lot of work. > An aggressive editor should be able to keep a nicely > organized page with the realization that some information is > going to be removed because it is not on-topic. But, most > people don't want to step on other's toes and you end up with > a somewhat well written page with a bunch of miscellaneous > cruft that doesn't belong, but the editor doesn't want to > remove. (I'm speaking in general here, not anything specific > to piclist.com.) The aspect of the wiki I like, is that > anyone (with access) can make small or big corrections. In > the end, the contents ends up naturally filtered through many > minds and produces a fairly good product. It is difficult to > find a balance between openness and protection, though. I've tried to make it less intimidating by allowing people to "give up" or release the position of page editor. Technically, you can take a page, change it, and release it. There is a slight delay in each part of that, but not much. > Yes, I imagine it would be an overnight or even over the > weekend project to effectively "compile" the site for burning > to CD if you used Wikimedia. It would also probably have a > larger disk load given that it maintains page revisions > automatically. Out of curiosity, how much of that 3gig is > maintained content and how much is mailing list archive? > I actually don't know. I think its about 2 GB in the archive and another gig of additional content. > > Most of the functions will work without javascript, the > scripting is > > there to "enhance the experience" if you will. Is there a > > better way to do it? > > A button that counts down to zero is not very common in most > user interfaces. It is more common to simply have a wait > page with a nice simple animated GIF to occupy the user while > the browser counts down a redirect. Though not everyone has > javascript enabled and not everyone follows redirects. You must be referring to the search delay page? That is true, but the "try again" button is not scripted and can be pressed manually for none-script browsers. > > > the use of > > > font size=+2, > > > > Where did I do that? I try to use heading tags, not FONT > tags. Or did > > you mean the use of H1 at the start of each page? Other suggestions? > > On the main index page, you list 10 items, 6 of them use bold or > font+2, 6 of them use the work PicList with two different > capitalizations, 4 of them are FAQs. Oh, yeah. That page is a nightmare. I've tried a few times to organize it. Maybe the truth is that I'm not a good page editor . Please let me know if you have better ideas. > I'm never really sure if I want to go to the PIC FAQ, PICLIST > Mailing List FAQ, PICLIST Mailing List Archive, or the > PICList.com Source Code Library, each of which with varying > levels of emphasis. > Interestingly, I go to the PIC FAQ and then see that PICList > is the /ultimate/ PIC resource, which then brings me back to > the page I was just at. One more thing I notice is that the > top of the PIC FAQ page is title MicroChip Technologies, > which isn't even the capitalization that Microchip uses let > alone standard capitalization. Guilty, guilty. > Minor issues I would agree, but, of course, I enjoy reading > sites like http://www.theslot.com/sharp.html There are a lot > of small issues like that, which I would fix as I came across > them in a wiki, but wouldn't bother emailing anyone about. > (Present email excluded.) > :) > > I like a simply, clean, elegant interface (compare > www.google.com to www.yahoo.com), but I'm also no good at > creating much of anything attractive with HTML. I can write > it and copy/paste/modify other content, but I'm not much good > at creating a page from the ground up. > Back to the dead horse, the wiki takes care of most of the > appearance making content creation easier and automatic page > creation and accidental linking make organization easier. Hummm... Maybe HTML allows too much control? I could try for page templates... > As I said in a previous email, I'm currently trying to > implement a wiki within the company I work for. These > engineers don't know HTML. > I don't want to be the sole editor. I want hyperlinking. It > seems like a very nice solid foundation. > > Bradley > -- > http://www.piclist.com PIC/SX FAQ & list archive View/change > your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist