I run my Jalbum/Neptune albums in an embedded iframe on my webpage.
<td align="center" valign="middle" width="100%" height="1024">
<iframe src="Albums/9-7-2019 Longboard Classic/index.html" width="100%" height="1024"></iframe>
I am trying to determine how to force it to produce full screen slideshows as the slideshows currently do not fill the available screen space. Is there a way to configure either Jalbum or the Skin to produce full-screen slideshows?
On your site, even on a large monitor, I get vertical scrollbars within vertical scrollbars. Ugh. I hate to think of what a mess it must be on a mobile device. Even on an iPad, it's probably an ordeal.
Let the albums stand on their own, with a link back to your home page. I think your visitors can live without having the top navigation on every page. And you could scale down your logo a bit, and include it in the titlebar of the Neptune album.
Point taken. I am always open to improving the usability of my website. I read the link above and would like to further explore what the following quote refers to:
The better approach is almost always to let the album stand on its own, and use the navigation provided by the skin to let your visitor return to your own page. If you want to provide things like a custom banner or navigation menu, many skins provide ways to incorporate your own content into the album without resorting to the sledgehammer of an IFRAME.
As is the case with almost every current skin, if you enter the URL of your own page under Album > Settings > Pages > Link to homepage, the skin will automatically plant an icon on the main page of the album that leads back to that homepage. Use an absolute URL.
You can put your own custom CSS and HTML in the album on the Neptune > Code > CSS and Neptune > Code > HTML tabs, but you have to know what you're doing. The skin won't write the code for you. It also can't correct invalid HTML - I ran your current "Lighthouses" page through a validator, and it coughed up 130 errors and 7 warnings.
I couldn't resist having a little tinker, and came up with a couple of alternatives. Both of these albums come straight out of jAlbum. The logo header and navigation are part of the album project - no iframes, and all valid HTML5. The navigation links are all "live," and lead back to your site.
First, one that sticks closely to the style of your existing site:
Notice that the nasty double vertical scrollbars are gone, and when you click on a thumbnail, the image makes use of the entire viewport, rather than being jammed into an iframe.
A second experiment, but with the navigation positioned below the Neptune banner. Not as consistent, but maybe a better-balanced page:
What I'd really like to do is plant your logo in the Neptune header, but that gets very messy, very fast. And the biggest problem is that your big logo is not a transparent PNG file, so it would land on the banner image like a lead weight, I'm afraid.
I didn't try to replicate your bottom navigation, but since that's mostly a repeat of the top navigation, it seems like overkill.
I finally have some time available to address eliminating the use of iframe in my album pages. I am intrigued with your samples.
Is this using the Neptune skin, or another. And since I'm not a web expert I'm not sure how to embed my page header in the album page.
To make this even easier, I'm attaching a complete zipped-up project, but with just a couple of small placeholder images, and without the output.
The routine has several parts. First is to create a res folder in the album project (the name is critically important), and to add a couple of graphic files to it - your logo and the Facebook icon. In my zipped-up example, those are called Logo.jpg and findus-fb.jpg.
The next step is to head for Neptune > Code > HTML > HTML to be inserted after <body> opening tag. There, we enter the HTML for the logo and FB link in a header, then the navigation links to the rest of your site. You can see the HTML coding in the demo1 project. This is what it looks like:
You're going to need to straighten out your website structure. This may seem complicated, but it's not. Once you get it cleaned up, you'll find it much easier to maintain.
For starters, do not try to "name" your index pages (OK for things like your Shop, Biography, and Contact pages, but not for your albums).
Second, do not upload your albums to locations with long, complicated paths. Let the server directory structure take care of it for you.
Third, no iframes. Anywhere. Ever.
So, let's lay it out:
http://rjlabellaphotos.com - your home page http://rjlabellaphotos.com/Lighthouses/ - your Lighthouses album. Note, not Lighthouses.htm, or rjlabella.com/Albums/Lighthouses. http://rjlabellaphotos.com/Wildlife/ - your Wildlife album. Note, not Wildlife.htm, or rjlabella.com/Albums/Wildlife.
Now, menu entries. From your homepage, and also from the navigation on each of your albums, the links to the other albums become very simple. The link to your Lighthouses album is always:
The link to your Wildlife album is always:
This means that the code we're inserting into Neptune > Code > HTML becomes: