Forum Moderators: open
If i only have resource to make only one version of my website, at this moment, is it feasible to make a ajax-only website? For your user statistics, do you see that many users are still using non-ajax compatible browser?
Thanks a lot!
This has repeatedly been part of all ajax recommendations.
is it feasible to make a ajax-only website?
Feasible? YES!
Practical? Not in my opinion.
AJAX only sites, usually lack "Bookmarkable" pages without extra work on the programmers side. AJAX only sites are not easily indexed by SE's without a lot of extra work(think FRAMES and FLASH). AJAX only sites tend not to work with JavaScript is off.
I would suggest make logicial pages that users can bookmark and enhance the site with AJAX.
AJAX only sites, usually lack "Bookmarkable" pages without extra work on the programmers side. AJAX only sites are not easily indexed by SE's without a lot of extra work(think FRAMES and FLASH). AJAX only sites tend not to work with JavaScript is off.
I completely agree. With advanced javascript, hidden layers, ajax and some creative CSS, you could make an entire site without a single page reload.
The advantages would be the site would be faster, have a much better 'feel' for the user, and could utilise more visual effects.
Unfortunately, the bookmarkability and the search engine factors outweigh this. It's a shame really.
You could have a 'Bookmark this page' button but most users probably wouldn't think to use it, and that doesn't solve the SEO problem either.
en i said ajax-only website, i mean i'm going to make a webpage with some ajax-functions (like submit articles without reloading a page)
This is entirely possible. Lots of sites are now using AJAX for dynamic pages and form submissions, this is stuff you can't bookmark and couldn't be spidered anyways, so yes definately go that route. If you don't know how then all the better as this will be a good learning experience.
Unfortunately I can't advise you as I've not done AJAX myself yet!
But... also take note of what vincevincevince said, you should code the site for non-JS, then use unobtrusive JS to 'reconfigure' the page and any forms after it's loaded. This is a must.
But... also take note of what vincevincevince said, you should code the site for non-JS, then use unobtrusive JS to 'reconfigure' the page and any forms after it's loaded. This is a must.
Thanks for the reminder. Though I don't really know how to use JS to reconfigure the page, I'm going to make a try.
[webmasterworld.com...]
I wrote a quick example for another user, if you're familliar with JS you'll get the idea.
My knowledge on js at this moment can't help me understand the thread, but it's definitely a good hint for me to start. I'm going to read w3school's tutorial on javascript and hope a week later i will understand more.
off topic: It's really difficult to make a webpage in these days. When i was very young, most webpages were done with static HTML page and some SSIs. After a decade, I have to learn CSS, ajax, php to make a slightly more interactive website. It's really exhausting. :P