Loading Profile...
A great title? "The Catcher in the Rye"
OK, this may be look at as lame but,,, A colleague of mine has a PBWiki ("jeffanesthesiology.pbwiki") and he has asked for my collaboration with another PBWiki. I have made mine ("anesthesiologyboards.pbwiki") because I want to get a "sense" of how to do this before we combine our Wiki pages to the residents we train. Finally to my question: I am trying to get my Wiki to look like his and I cannot seem to find the "skins" setting to get the "olive coloring, buttons, &c". Has that been taken out in the PBWiki v2? Or can I change the look of my Wiki to his some other way?
I’m silly
1 person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
To be clear, we're letting folks change the coloring to one of about a dozen different visual themes for free. That should work for your Catcher in the Rye wiki. Paying customers have complete control over coloring and can upload a logo - PBwiki will take the colors in the logo and automatically apply a logo-appropriate color theme for 2.0.
(Paying customers will also be able to fully override our CSS, but this is a great way to shoot yourself in the foot and we will not support layout issues in a customer's wiki with overridden CSS. We also don't offer skins that change the layout/DOM.)
Note that we do have on our roadmap making a "republishing API" available. It may surprise some to know that www.pbwiki.com is actually just such a "republished" wiki. Letting customers have a fully-skinnable read-only view of their wiki should solve most of the skinning requests.
Your feedback on the above is welcome.
The company and 1 other person say
this answers the question
-
Inappropriate?V2 does not have "skins". You cannot make a V2 wiki look like a V1 wiki. (Well, if you are a CSS expert, upgrade to Premium, research and learn the undocumented CSS for V2, then create a super-l33t style sheet, I suppose you could, but the average user cannot easily accomplish this).
I’m missing V1 features left and right
1 person says
this answers the question
-
Inappropriate?We're going to be offering at least a few different color schemes for free users in the near future, but the layout will be the same, so we're not going to have different "skins" other than the ones users create for their own wikis.
Vu
-
Inappropriate?Thanks, Vu. I've updated the PBwiki Missing Features Wiki to reflect the loss of skins in V2.0.
I’m sad that all the wikis look like clones
2 Comments Add a comment
This answers the question
-
I am also disappointed that all the wikis look like clones, and to be sure - as a teacher I don't really have time to go through all the steps that you mentioned in your previous post in order to have some customization on my wiki. I realize that we can change colors (although a tiny little note says that color customization will only be available for premium accounts in the future) and maybe add a picture, but what if we want something that is truly reflective of our individual personalities? I don't like the 'corporate-everybody-do-the-same-thing-and-have-the-same-look' idea. It makes me grumpy. -
Their feeling is that, if you want personalization, get a MySpace page. PBwiki is for paying corporate customers (gotta pay those 22 people somehow).
-
Inappropriate?To be clear, we're letting folks change the coloring to one of about a dozen different visual themes for free. That should work for your Catcher in the Rye wiki. Paying customers have complete control over coloring and can upload a logo - PBwiki will take the colors in the logo and automatically apply a logo-appropriate color theme for 2.0.
(Paying customers will also be able to fully override our CSS, but this is a great way to shoot yourself in the foot and we will not support layout issues in a customer's wiki with overridden CSS. We also don't offer skins that change the layout/DOM.)
Note that we do have on our roadmap making a "republishing API" available. It may surprise some to know that www.pbwiki.com is actually just such a "republished" wiki. Letting customers have a fully-skinnable read-only view of their wiki should solve most of the skinning requests.
Your feedback on the above is welcome.
The company and 1 other person say
this answers the question
1 Comment Add a comment
This answers the question
-
Arg. This *should* be free and we have a change request internally (#682) to let users pick one of our preset color schemes for free that I assumed was fixed when posting without actually checking it. Sorry; we'll get on this.
-
Inappropriate?This is more of a personal opinion. I realize that PBWiki may be just starting out and version 2 is upgrading of the software and business model of version 1. My colleague and I are both physicain educators, somewhat "feeling our way" into this "Wiki thing" (yeah, you guessed it we're both old). What I need from your company, for my collegue and I to continue to use your service (i.e. free would be ideal for us but paid would be ideal for you), is a way to have a "couple of Wikis" that we could manage that would be identical in appearance so our sites look seamless.
I know we could combine the sites into one but by having more than one we can:
1. divide up the administration tasks
2. have control over our particular subspeciality areas
3. not have to constantly meet or notify each other of the changes we have made to the site(s) as only one person will be in charge of the membership, organization, and administration.
jeffanesthesiology.pbwiki has a very nice appearance and I really don't have the time to be, not only learning CSS, but having to code a CSS to match his site which is where the skins question came about - i.e. for people to just quickly get a "site template" (skin) to quickly set colors, buttons, heading fonts, &c. to a limited set of pleasing appearances.
I know many web sites have web site templates people can choose, it would be nice to see that being available in version 2. Thanks.
I’m ok
EMPLOYEE
EMPLOYEE