There is no link back to the sample album's 'Home' page from the About page, I never put one in the template. You just click any of the links, like Jesrey or Lichfield to go to the other pages (those pages are where you would get to by clicking on the thumbnails, so it is just one click instead of two), from there you can click on an 'up' button to get back to that landing page.

If you really want a link back to the top level index then you could add one to each template.

Well Rob, I saw that problemen of the link back to the first index page in my skin which I did extend with your navigation.inc code.

I thougth that it was caused by the line which had been removed on your advice:

if(defaultShowSettings)

What was that statement doing?

It is worth remembering that with templates you can override the index page for any folder. For example you could add the About template at the root level but rename it to index.htt, with a title set to 'About'. When the album is made the index.html page becomes the About page and the top links take users to the different top level parts of your album.

Have a look at my Home page http://robm.jalbum.net/RobM/index.html as an example.

Copy your modified empty page to your skin, place it in folder called templates. Reload the skin and the modified template should appear in the page templates menu.

I called my empty page "Blank" just to differentiate it from the default empty page, which shows for all skins. However, skin specific templates, as in your attached screenshot, are grouped below the horizontal dividing line. That is how users can tell if they are using the jAlbum default empty page template or a skin's own set of templates.

FullSiteSupport is a skin property, it is listed in the Java API but is easiest to find in jAlbum with Tools, Skin Developer, Edit skin properties
I have added it to the skin properties documentation http://jalbum.net/help/en/Organization_of_a_skin


About and Contact are modified versions of Turtle's templates, the contact.png I used is from Turtle's skin. Sorry, I should have stated that, but you can use any image you want, just add it to the res folder.


Those icons are from the jAlbum application, I'm on my iPad and can't remember the exact location, skins or resources. You can modify the template to add another (url) field if you want, but since the site visitor is already on the site is it worth adding a link there?


I actually have all of my resources in the normal 'res' folder, but I move the folders contents to the parent folder's res directory when using a common resource folder. That meant having my own 'resPath' variable.


All of the templates have a single div using #pageContent, unless the user enters an id or custom CSS in the template interface. The CSS file containing the #pageContent selector attributes is generated by the template and saved to a file using the template's name. For example the About template creates a file called 'about_style.css' in the 'res' folder.

If the user wants to use a specific I'd, say '#content-page', then they can enter that. As there is no standard I tried to cover all conditions, skin specific, template specific and user generated CSS.

As there is only one div on each template using that selector an id is valid.


Not using the TemplateHeader should not stop it working, it allows the link to the CSS files to be placed in the 'header' section of the page, rather than in the body section.

The advantages, maybe none! It is intended to try to make templates work with any skin that supports templates and to prevent the UI from showing if the user switches to a skin that does not support templates.

It would be better if the templates could be prevented from running with skins that are not site aware, but I can't code for that. How well they work in other skins will depend on the user and the skin designer. If the skin designer documents the id selector they code specifically for a template, then the user can enter that I'd in the template. Otherwise the user uses it as is and hopes for the best, or they examine the skin code and/or write their own CSS. That is why I listed a set of id selectors for different skins that I have tried the templates with.


As above, it was based on Turtle, Laza presumably coded the size for aesthetic reasons, if left to the user I supose someone could use a really big image!

You are welcome, I hope some of it is useful and that the above helps.

Yes I know, but my question was: Why? Who is using it?

I understand, but I like to show a consistent UI to the album user. So if he can chose any picture and name in About.htt, he expects to handle the image in the same way in Contact.htt

??? I do not see that a 'about_style.css' is created in the 'res' folder!

I have now for my about page and about_album page a differtent style for <p>:

#about_album-page .texts p {
	line-height:1.5em;
}
#about-page .texts p {
	line-height:2.0em;
}

But if I use id pageContent for all templates, this becomes:

#pageContent  .texts p {
	line-height:1.5em;
}
#pageContent  .texts p {
	line-height:2.0em;
}

so both templates do get the same line-height.

Very usefull!