UI and interface changes needed for vRWOT

[noahgibbs]

We should replace the Gables logo with the RWOT logo.

Do we need to update the interface? At a minimum broken images should be removed or replaced.

When creating a chatter, we should go over the wording. Right now it's not at all clear that you're a conference attendee, creating an account to talk to other conference attendees.

In thin-auth, it all says Gables and talks about contacting SkotOS. Not sure we can 100% scrub all of that (like, in some error messages :-/ ), but we should review all the PHP pages. We definitely have to update names of everything in the JSON config files, but also copy in the login and user registration PHP pages.

[saraht45]

Some WOE objects to review/update for RWOT:

• Theatre:Theatres:Tavern - All basic settings for a Chat Theatre
• Theatre:Web:Theatre - Holds all the html for the character portal page
• Theatre:Web:StageStartStory - Holds all the html for the character Start Story
• SkotOS:Tips:Intro - A database of tips that are output with the @tip command. May want to add more or change wording for RWOT.
• SkotOS:HelpNodes:* - Tied to the @help command. May want to either flesh this out better or rewrite the @help command to link to the SkotosDoc page

[ChristopherA]

In particular, it feels like HelpNodes need to be plugin mergeable, i.e. some simple set for the "base" help nodes, then the ability to fold in the setting (RWOT or Gables) help nodes, any help nodes for specific plugins. I don't think the current architecture for help makes this easy (not sure).

I don't know that Tips needs to be mergable like HelpNodes. I think each setting (RWOT, Gables, etc.) defines their own.