Page 1 of 1
Best Way? Design of a Website + Registration System
Posted: Sat Aug 25, 2007 3:00 pm
by legend986
I'm actually planning to design a whole website with a registration system and thought of the following initially:
- It'll be complete Ajax Driven
Very Light Weight
Uses at most two libraries: prototype.js and scriptaculous.js
SDK used: IPB SDK to tie it up to my forum
What it contains:
- Maybe 15 pages of content
20 different registration forms out of which two or four have to have an option to upload a file
Tied up to my own forums using IPBSDK
The design of the content part is almost done and I"m now at the registration part. I wanted to know whats the best way to design a Registration System.
I thought of a few:
Because there are 20 different events under which one can register, I thought of making 20 different forms but that doesn't seem practical. So, as I'm already using Ajax, shall I add/subtract registration fields depending on the event selected and the further options that are selected?
Other than that could I expect anymore suggestions?
Posted: Sat Aug 25, 2007 3:34 pm
by feyd
legend986 wrote:Other than that could I expect anymore suggestions?
Make sure it works without Javascript.
Posted: Sat Aug 25, 2007 3:37 pm
by legend986

Almost forgot about it... In that case, no more Ajax is it?

Posted: Sat Aug 25, 2007 3:39 pm
by feyd
You can still use Ajax, you just need to make sure the pages can still work without it or Javascript otherwise you're excluding potential visitors/customers/whatever. .. .not to mention potentially illegal in certain regions/countries due to accessibility laws.
Posted: Sat Aug 25, 2007 3:40 pm
by legend986
May be I'm missing out on something but could you give me an example as to how I can make it work even without Ajax using Ajax? Sorry for the trouble though...
Posted: Sat Aug 25, 2007 3:58 pm
by s.dot
Instead of AJAX not reloading the page, make sure the forms still have a "regular" processing script and can be accessed normally.
Posted: Sat Aug 25, 2007 7:56 pm
by califdon
feyd wrote:You can still use Ajax, you just need to make sure the pages can still work without it or Javascript otherwise you're excluding potential visitors/customers/whatever. .. .not to mention potentially illegal in certain regions/countries due to accessibility laws.
Hey, feyd, tell me more about the potentially illegal issues in some countries. That's new for me. Can you give me a URL reference? Thanks.
Posted: Sat Aug 25, 2007 8:09 pm
by Benjamin
Posted: Mon Aug 27, 2007 7:33 am
by legend986
What about my post?

Posted: Mon Aug 27, 2007 7:55 am
by xpgeek
Start googlin by words: degradable Ajax
I hope it help.

Posted: Mon Aug 27, 2007 10:19 am
by jason
One method I've used it pretty simple and encourages simple HTML working pages is to work first from POSH. Get the PHP/HTML stuff working first. Then add in JavaScript without actually touching the HTML. Various frameworks easily allow you to do this, such as jQuery. While designing the PHP/HTML interface, I focus on creating simple interfaces in PHP, that way, when I add the Ajax, I don't need to rewrite anything. It simply integrates into the PHP easily. Most of this is a result of creating external include files that are easily accessible. So a example.com/api/add_user.php page is used by both the underlying PHP/HTML setup as well as the Ajax.
The key here is making sure the interface for adding a user is easily accessible by both systems. The benefit is you suddenly have a remotely accessible API for other people to interface with your site. Just be careful about security!