The default JSP files and CSS files are functional, but they're not very pretty. [I|JanneJalkanen]'m a total klutz when it comes to doing something beautiful, so if you have any ideas or better yet, concrete code, CSS files or whatever to make JSPWiki look prettier.

Note that the Wiki should still be kept simple, fast, and [functional across browsers|JSPWikiBrowserCompatibility].

As of JSPWiki 1.9.2x (to be 2.0 someday), you can easily write your own JSPWikiTemplates.  I would also like to add a couple of choosable templates to the JSPWiki distribution.  We'd need one CSS-based template (with user-switchable skins), and then perhaps something else (something suitable for a weblog?).

--[JanneJalkanen]

----
There should be some default templates here in different languages (see my comment [TemplateDiscussion] "Making Live easier - Use String-Variables within each JSP-File for Language-Translation!
")
----

Look at [TableTemplate] for an example of a facelift.
 --[Mortena]

I simply love the look of Docbook Wiky. What about doing something similar? --[Gabridome | http://outerthought.net/wiki/Wiki.jsp?page=Gabridome]\\

;:Want to contribute? ;-)

Totally agree! Is this finished yet? Who is working on it? -- [rsc] 22.8.3

----

I added a little CSS and a sort of aqua theme. Have a look: [Roller Weblogger WIKI|http://rollerweblogger.org/wiki]. --[DaveJohnson]

Dave, would you be willing to package it as a zip file and upload to ContributedTemplates? --JanneJalkanen

That's a pretty clean-looking template, Dave.  Of course, I might be biased since I'm an OS X user, too.  I concur with Janne, please upload to the ContributedTemplates page if you are willing to share.  As a side note, Janne, I think JSPWiki might become a bit more popular if it had a cleaner, more polished default template (keeping cross browser limitations in mind, of course).  A lot of people judge things by first impressions and looks and, while the current template is completely functional, it looks a bit stale.  [Pic/smile.png]  --MichaelGentry

----

A minor thing that always bothers me: in my personal use, I tend to get long pages, and as inspiration for additions hits, I have to hunt the ''edit this page'' link from somewhere way up in the menu.

If you're OK with CSS, it saves the day again. Add this to your webapp's ''.../templates/default/jspwiki.css'' (make sure that's the one you're using - depends on your template, and on your JSPWiki version!):
{{{
div.leftmenu {
  margin: 0;
  position: fixed;
  top: 6em;
  left: 4px;
}
}}}

Then, in the same directory, edit ~ViewTemplate.jsp. Find the spot where ~LeftMenu.jsp and ~LeftMenuFooter.jsp are included, and surround the appropriate section with <div class="leftmenu">...</div>. In the default template, this would be the contents of the surrounding ''TD.leftmenu''.

Voila. Hovering menu. A word of warning - make sure your left menu isn't very long. The dynamically sized ''referred by'' list could cause problems. Adjust your margins and positions to suit your site; these happen to work for me. Also, <hr> tags within this div seem to cause havoc in the default template - if someone sees what's wrong with that, let us know.

(Feel free to streamline this, if you find a cleaner solution.) --[ebu]
----

It started as a joke, but I think some might like it. have you worked with a 3270 emulator? you'll never forget it.
[JSPWikiFaceLift/3270ScreenShot.gif]
I don't think this is a new template, as it emerged from MichaelGentry's [Contributed Templates Mrg]. 
--AlfonsoMartinez

----
Hi all.  I want to contribute to the css effort as I think I have some talents I can offer.  Is there a CVS?

[thomas]
----
I uploaded a new skin based template called [ButtonMenuTemplate], thats pure CSS and allows users to switch the skins on the fly.  Each skin is basically a reference to a CSS file and I have created 3 CSS files (we can add more).  Currently, the user cannot change the skins from wiki UI (I still haven't started playing with the wiki source code... but should be pretty easy) but has to update the link to stylesheet in one JSP file. 

On a side note, shouldn't we distinguish between JSP and JSP-fragment. Currently everything has a .jsp extension this is a problem for pre-compilation of JSPs.  We should have *.jspf extension for JSP fragments.

''Good idea! --MikeMorris''

Suggestions/Comments/Feedback???

--[BaldeepHira]