- How to make a facebook web page with jalbum skin#
- How to make a facebook web page with jalbum full#
- How to make a facebook web page with jalbum code#
That folder will automatically be hidden so it's not visually included in the "album" you make, but the whole folder is copied to the final "album" (should be called "site", right?), and all resources within can be referred to via the $ variable, no matter where in the folder hierarchy you are. Put those files inside a folder you name "res" (stands for "resources") of your "album project". You also want to include other resources, like a custom logo, favicon, about-page image, css and such. All are bundled with jAlbum 10.4.Ī web site is not just about web pages and album images. So far, the following skins include site support: Turtle 3.0, Base 2.0, Galleria and Minimal.
How to make a facebook web page with jalbum code#
That code first checks if the user has added custom web pages to the top level of the album, and if so adds a navigation bar.
How to make a facebook web page with jalbum skin#
jAlbum provides code for a simple navigation bar, so a minimal code for skin developers to add can be: They should also provide custom "page-header.inc" and "page-footer.inc" files so that any extra pages made by users get the same look and feel and navigation that the album pages have.
How to make a facebook web page with jalbum full#
Skin developers can easily modify their skins to support full web sites by including a top-level navigation bar that links to the extra. The template for the empty-page.htt looks like this (double click to open):
To simplify creating these custom "About.htt", "Contact.htt" and "Blog.htt" files, jAlbum has a new context menu called "New page" that grabs an "empty-page.htt" file from the system folder. htt page includes a standard "page-header.inc" and "page-footer.inc" page provided by the skin (and ultimately generic ones provided by jAlbum if the skin lacks these files) To have consistent navigation added to the top of all generated pages, each. htt pages called About.htt, Contact.htt and Blog.htt (the last one simply containing an iframe towards a blog service). A user wanting to create a site looking like the example above would simply create sub-albums for each sub-section plus three more. This behavior mirrors how web servers treat the existence vs lack of an index.html file in a folder. With that one present, jAlbum will ignore the skin's "index.htt" file for that folder (that produces the thumbnail overview). A user can easily create a custom landing page as an introduction to his album by putting a custom "index.htt" file in the root image folder. htt files will get processed just like the template pages of skins, but they can contain any html, not just album specific html. htt pages (html template pages) along with images in their album projects. This is made possible by allowing users to mix. JAlbum is now generic enough to support the making of these types of simple portfolio sites (all but the blog). What you see is a typical photographer's web site, where the images are in focus but there are also links to about, contact and blog pages. I was passed a link to a website that has a particularly good album integration: JAlbum is now not only a tool for making awesome web albums.
0 kommentar(er)
