Obviously, a div can be fixed but the problem is applying it to every page. There are two possible solutions: either use _template but you will have to copy all code to all sections of the website or (as I have done), if you do not use one of your nav elements, put the code in your side or top menus.

I do not use side so I have placed the code here:

 [[image http://onlinecv.wdfiles.com/local--files/admin%3Acss/feedback-corner.gif link="start:feedback"]] 

And in your custom CSS, use the following:

 #side-bar{ position:fixed; bottom:0; right:0; width:81px; height:81px; padding:0; margin:0; } 

Then, on your feedback page:

 [[=]] Any comments or suggestions are welcome. [[module MailForm to="{your-username}" title="Wikidot Feedback"]] # name * title: Name * rules: * required: true * hint: Required # email * title: Email * rules: * required: true * hint: Required # affiliation * title: Institute/Organization/Company # message * type: textarea * title: Message * rules: * maxLength: 1000 * required: true * hint: Max Char. 1000, Required [[/module]] [[/=]] 

Remember to change {your-username} in the MailForm module.

And here is the result: HaveMyCV.com

If you decide to deploy this on your site, please copy the image to your site: I may change it and the design may no longer fit with your pages.

Hope this helps, feedback welcome :)

Neste espaço você deverá discutir sobre as suas observações quanto ao site do WikiDot, lembre-se de informar os sites juntamente com os comentários. É necessário que você aluna, abra uma conta no Site WikiDot, isso facilita seu acesso nos outros portais.

Example:

• list by skill level: beginner, intermediate, advanced

Listpages must be able to list the pages from beginner to advanced.

What ingenious solution can you think of?

— hartnell

I need the iatkos 1.0 software or a another workinkg
Software for my IBM T30. My Problem is: I can't find an
Working Downloadbutton from the old OSX86
I think only tiger is working
please help

mfg larfus

I'm getting ready to start a new wiki. I don't particularly want to use the forum capabilities for this one. I want it to be more like a traditional wiki, that grows serendipitously and can take multiple directions. Do you have any advice for me as far as the organization of such a site? Should I just start out with one page and allow the natural instincts of users to build the structure as they add new pages and suggest new topics? Are there any good examples of sites like this? Particularly, the site I want to build will be a knowledge base site for a college, a place where any and all constituents of the college can add pages, create new categories, and be free to add their knowledge to the site.

What do you think about paying a software developer (Wikidot in this case) to develop a certain feature you need?

If you need an already planned feature you could pay to have it done sooner. Or you may need a feature not in the the developer's to do list at all and pay to have it.

Once paid for and implemented, the new feature would free remain for everyone else.

This suggestion may give rise to concerns like these?

• wouldn't a lot of minor significance features make it into the product and turn it into bloatware?;
• wouldn't developers give up work on the really important stuff then?;
• how could developers make a planned feature "sooner" when they are already working full speed?;
• would someone be willing to pay at all?

I think I've provided the answers in another suggestion of mine, found in this file. It's actually several suggestions including elements from the previous posts on the topic of business models, all packed into one file. You can download the reader for the file here.

I'm especially interested in wikis that integrate the new blog function with a "conventional" wiki, but I could also use some general inspiration for nifty layouts.

Good support can really make everyone happy - users do their work faster; developers receive quality feedback and focus their efforts at improving what needs to be improvemed most; users are happy that their problems are addressed and become eager to spread the word. I think that quality support is one of the best marketing tools for software/ web services and maybe one of the least utilised.

But it's not only that - I think support is underutilised as a revenue model, too. I am far from the notion that it can be the main revenue stream but it could be one. I am also far from the idea that users should not have a large portion of it for free.

What I am suggesting is that Wikidot could charge for instant, over the phone (or Skype) support while keeping everything else (that is the non-instant support on this forum) free.

The rationale is that the value of support can be determined by how urgently one needs it. The sooner one needs it the greater probability she would be willing to pay for it. (Actually a user might be disappointed to see no paid support available when he needs it as soon as possible and is ready to pay.)

Of course support should not pervert the idea behind a product - developers must remain focused on improving their product and making money from that rather than charging for support of a crappy product bound to require a lot of support. (Fortunately this can happen in monopolistic services only.)
Thus a basic principle in a revenue model based on support should be: the less support needed the more money made. In practice this could translate to, for instance: the more time support takes the less be charged for it.

How it can be implemented in Wikidot is another story. Questions may arise such as:
- what if the user who pays for support is not happy with the service, shoudl he pay then?;
- how could it be determined if the issue was really resolved?;
- how exactly is the payment is going to take place?;
- what if the support team can't find a solution?;
- will the solutions be entered in a database for reference to everyone else, for free?;
- should Wikidot need to hire staff specifically for this or Wikidot users would be offer paid support, too?

These are technicalities and I have a ideas about them and I'd gladly discuss them. But first, what do you think about the suggestion as a whole?

My first suggestion is very simple: no matter how good, how clear, how colourful, how intuitive handbooks we make for first time users, most of them will always prefer someone to save them the reading, "chew it for them" and explain it on the spot (or over the phone/ VoIP).

So why not offer this option for new users and make money from it - paid support for first time users over VoIP, priced in "packs" of 5 hours, 10 hours, 20 hours, etc?

Wikidot may even not need to hire employees for this. Just make a "marketlpace" for Wikidot lessons and retain some percent from the prices.

_________

Following posts:

http://community.wikidot.com/forum/t-103612/wikis-wikidot-and-business-models-2
http://community.wikidot.com/forum/t-130398/wikis-wikidot-and-business-models-3

[[http://www.teach-nology.com/worksheets/misc/centers/electricity.gif
]]

Introducing the Seo Dojo moderated by yours truly Whane The Whip <— Actual SEO industry professional and Wikidot Guru.

I'm just getting started on the site and you can expect some deep content relating to SEO methods and information even the experts don't know about (yet). But for now, and assuming that most wiki whackers (yeah, good term so I'm borrowing it) are unfamiliar with SEO, I've written a brief SEO Guide just for you.

If you are an SEO pro, or a budding SEO enthusiast, I invite you to join the site and add content if you wish. Contributers will eventually share PR. Don't know what PR is? Then you better start reading…

P.S. Site content has not yet been perfected, but the guide still contains accurate and priceless information. I will be improving the site and adding content throughout the next few months.

Why do you think this is?

— Shawn

— Shawn

Why use a wiki rather than any other kind of website?

— Shawn

— Shawn