Wiki challenge!

[Mark]

I'd probably not have left my bed in the last 20 years!

Does she have a sister?

 

[Kristian Serrano]

5th question: What's the status on new visual themes for ENworld? White-text on black background is not working for me, certainly not for browsing/editing a Wiki.

JSYK, you can choose skins for the wiki under "My Preferences".

It's independent of the EN World skins. I set mine to Modern it's much easier on the eyes.

 

[Fifth Element]

So I see - super! I respect and admire you!

For the record, I have no problem putting all OGC I've ever published in the wiki - it's rather easy when you work from the source files.

 

[Morrus]

For the record, I have no problem putting all OGC I've ever published in the wiki - it's rather easy when you work from the source files.

Yeah, I'm quite happy to do similar - it's just finding the time!

 

[jmucchiello]

On a related note, while I admire these projects, I have to say that I have a personal distaste for wikis, specifically with regards to their editing and markup. I don't understand why wikis insist on using obscure and nonstandard markup rather than creating a WYSIWYG that creates standard XHTML. Even Google Docs, Google Sites, and Google Page Creator do this. It's for these reasons that I also don't understand why wikis are so popular.

Like most things on the Internet the answer is in the past. Wiki's first appeared long before WYSIWYG JavaScript editors were popular (or even good). They rolled their own markup because parsing HTML sucks and XHTML had no mindshare at the time. Modifying HTML by hand is also a chore and since being easily modified is the whole point of a wiki, that was another strike again HTML. The benefit to using their own markup was that they could easily validate the input and they avoid all the issues of javascript injection since they control the translation from wiki-code to HTML.

The real problem with wikis is that wiki-code is completely unstandardized. What makes text bold in one wiki denotes a H4 tag in another wiki.

 

[jmucchiello]

The first line of your entry should read [item name] is a [item type] from [product name] published by [publisher name].

Isn't this a violation of the OGL? You can't reference upstream contributers without written permission. That's why the OGC project Wulf referred to was only doing OGC from voluntary publishers.

11. Use of Contributor Credits: You may not market or advertise the Open Game Content using the name of any Contributor unless You have written permission from the Contributor to do so.

 

[Morrus]

Isn't this a violation of the OGL? You can't reference upstream contributers without written permission.

You are correct. My fault entirely. I will remove the references to the publishers and products (well, except the ENP stuff because, well, I want it there and I give myself permission!; plus the Fifth Element stuff, because he added it himself and presumably gives himself permission!)

 

[Fifth Element]

You are correct. My fault entirely. I will remove the references to the publishers and products (well, except the ENP stuff because, well, I want it there and I give myself permission!; plus the Fifth Element stuff, because he added it himself and presumably gives himself permission!)

I'll think about it.

And well spotted, jmucchiello.

 

[Jackelope King]

Morrus, is this challenge for bulking up only for D&D-compatible material, or d20 material in general, or open gaming material in general?

 

[Morrus]

Morrus, is this challenge for bulking up only for D&D-compatible material, or d20 material in general, or open gaming material in general?

Any open gaming content.