I've not done anything this way before but for a uni web design and development assignment, I've to firstly design a website with all the theory and how it will all come together.
Therefore, I'm wanting mine to be a little different from the generic kind and whilst I'm basing my subject matter on Tigers and the several species of, I'm creating an entrance page in fireworks that is the following;
I'm planning on sectioning up and placing hotspots around the interior of the tiger body, this will enable viewers to select and go to set pages like "about" "tiger zone" "contact" and so on.
However, I still need a traditional-ish homepage but I'm unsure how to make it that whilst people come in via the entrance page ( as above and the main url) whenever they've left this page to go in to the main homepage, they don't return via any of the main sites navigation menu / links back to this entrance page, is this possible in anyway?
I'm trying to get my own head around this and I have spent a number of hours researching this issue but I cannot find any resource that is anything like what I'm needing to do.
Thanks as always people.
You can have 2 'landing' pages. The initial one when your visitors click can be this one. From here on, any clicks will take them to content pages. From one of those content pages, the 'Home' will take them to the 2nd landing page. All this is fine. But, there is a possibility for your user to return and see the landing page again if they see their history or bookmark the initial index page, or, even notice the web url which you cannot hide.
I see a few ways of achieving it:
Let us see what others on this forum have to say. Their opinions will be very valuable, I'm sure.
Hi Sudarshan and thanks for the reply.
Yes, that was my main concern about people been able to return to the original first landing page. When you say a second landing page, you in effect mean what would be a traditional homepage right?
Regarding your two thoughts of a way around stopping the issue of a user been able to return to the first landing page, I have to be honest I wouldn't know where to start with either of the options, what would you rate the difficulty level of both options you mention for a DW user like myself who is only self taught and only learns what he needs to know at the time kind of thing?
As you say, others may well come up with other ideas too but I appreciate you replying with your message and thoughts.
I don't want to pour cold water on your idea, but your proposed design harks back to the late 1990s when "splash screens" were all the rage. You've correctly identified the problem that a splash screen is attractive the first time, but after that it becomes a hindrance. Take a look at this blog post that summarizes all the drawbacks: http://blog.silktide.com/2010/11/why-splash-pages-suck/.
Another idea might be to keep your large image on the main landing page, and put it in a sliding panel that can move it off the page, or bring it back if the user wants to view it again.
Yes, 2nd landing page will be the 'traditional' homepage.
This case, the tiger page will have to be 'index.php' so it'll load when your site is entered in a browser. Why PHP - we'll get to that in a bit.
Let us use, lets say a cookie to see if the user has already been on your index.php (which is your tiger page). If they already have, they will be taken to index2.html (the 2nd homepage - which doesn't have to be php as we aren't using any cookies/ sessions here).
Something like this should work:
// please note there is a dot prefixed in '.yourdomain.com':
setcookie('homepage', 1, time() + 365*24*60*60, '/', '.yourdomain.com');
// you could add more PHP code (if you require), but ensure this patch of code is right at the top of your tiger index page
This should be placed at the very top of your tiger index page which is your initial homepage when users enter your site.
This is how it works:
homepage - the defined name for this cookie
1 - enables the cookie
time() - expiration value for the cookie. The value suffixed with 'time()' is for 1 year - meaning the cookie will remain active for 1 year. If you want it to exist until the browser is closed, set it 0 like this:
setcookie('homepage', 1, 0, '/', '.yourdomain.com');
The / next to time is the areas within your domain that the cookie is available for. / denotes higher most domain path. This is useful if your index.php file (main splash page) is located within the main domain root itself. If not, if it is located somewhere like yourdomain.com/tigerhome, set that to this:
setcookie('homepage', 1, time() + 365*24*60*60, '/tigerhome/', '.yourdomain.com');
Please notice the trailing and prefix slashes for the folder value
yourdomain.com - is the main value of your domain itself. Please note the prefixed dot [.] before the yourdomain.com.
How the header works:
If the cookie called 'homepage' exists, then when the user is trying to load index.php, the header condition is read by the browser first. If it is true, the user is taken to another_page.html. If not, the user is allowed to continue viewing index.php page.
The reason we have this at the very top is because when the user attempts to load up index.php page, you dont want the content to be shown before redirect happens. Hence, the header condition along dependant on the cookie is first read by the browser.
If you want custom time setting - maybe 1 day, set it to this:
setcookie('homepage', 1, time() + 1*24*60*60, '/', '.yourdomain.com');
5 hours, this:
setcookie('homepage', 1, time() + 1*5*60*60, '/', '.yourdomain.com');
And so on...
Note: The cookie will expire if the user clears browser cookies manually!
But this is the basic way of getting a cookie set for getting what you want done.
Also, I've set up a test page on my domain for you - expires in 1 year from first visit. Loads on index.php and redirects to test2.html if the cookie is already set. Try it out for yourself here.
Trust this helps.
Firstly thank you for your replies, they're much appreciated.
In all honesty I know that's what a lot of people would think David but I have limited time to create this and I can't draft all the sketches, drawings and other elements of the theory aspect until I have an idea how I'm going to construct the site, the layout, the navigation elements and the content elements etc.
It is only to show a basic aptitude in the use of Dreamweaver and Fireworks for this coursework and hence I thought it would look different to what's already out there and add a little extra upon entering the site. It won't just be a splash page of old or like you still see with a simple image and then an "enter site" button and that's it.
I'm actually going to split up the tigers body in to sections and each section will have it's own URL link to the users desired section of the main site, if I can figure it out I'll also be placing some form of Rollover effect on each section, so when the user hovers their mouse over they can clearly see visually what that link will take them to.
However, I still see what you're saying and now I'm second guessing myself as your idea sounds a good one but I think "put it in a sliding panel that can move it off the page, or bring it back if the user wants to view it again." maybe currently above my knowledge base.
An intro page -- in this case your tiger image map -- is considered a splash page.
Experienced web developers don't use splash/intro pages for real web sites anymore because they hurt your chances for a good ranking on search engines. The domain name home page is the most important piece of real estate in the site. It's the first thing people land on when they come to your domain. If the index page lacks keyword rich content, it will never be recognized by search engines. That's a missed opportunity because search engines drive traffic to web sites.
I would like to see you build a compelling home page with real text inside headings and paragraphs. And, if you wish, an image map of the tiger. This will keep humans interested and at the same time give language translators, search engine bots and screen readers something to grab onto.
Thanks for your reply. That's the thing it's not a 'real' website, it won't be making it live to the internet, it's purely academic and as I mentioned to David it is just to show a pretty basic grasp of the theory behind what it takes to build a website such as;
Idea Mapping, Target Audience, Idea Sketches, Personas (User Profile), Accessibility, Navigation Diagram and so on Content Diagram.
Then we have to create our designs in Fireworks but leave them unflattened, so they can see how we've put all the layers to our designs together.
Then in the new year we actually implement our design and develop the site but again I reiterate it won't be a live site and is only for our assignment.
As I have mentioned previously, I know it's not the done thing now on the whole for splash pages but I couldn't think how else I can have a lush white tiger adorning the page that greets 'hypothetical' users, before they navigate to the main homepage.
Suppose I best go back to the drawing board, although times against me now for changing the whole design structure.
While I second that the concept of splash page will lead to lower search engine rankings, considering you've also clearly mentioned you're only doing this as an 'academic assignment', to achieve the 'one-time-only' splash page, my response in reply #4 should work for you. Did you try it?
Although it's an academic exercise, I think the weakness of your concept is that a visitor to the site will see the stunning image of the tiger only once. I like the idea of splitting the tiger's body into sections to reveal information, but you have a large amount of empty space on the left that could be turned into a menu. The tiger could be used as a background image, and the text in different pages or sections could have a semi-translucent background that allows the tiger's stripes to show through.
Don't underutilize your greatest graphical asset.