Web Design - XHTML,CSS

  • strict warning: Declaration of context_condition_path::execute() should be compatible with context_condition::execute($value) in /home/gdzinene/public_html/sites/default/modules/contrib/context/plugins/context_condition_path.inc on line 62.
  • strict warning: Declaration of context_condition_node::execute() should be compatible with context_condition::execute($value) in /home/gdzinene/public_html/sites/default/modules/contrib/context/plugins/context_condition_node.inc on line 42.
  • strict warning: Declaration of context_condition_menu::execute() should be compatible with context_condition::execute($value) in /home/gdzinene/public_html/sites/default/modules/contrib/context/plugins/context_condition_menu.inc on line 48.
  • strict warning: Declaration of context_reaction_debug::options_form() should be compatible with context_reaction::options_form($context) in /home/gdzinene/public_html/sites/default/modules/contrib/context/plugins/context_reaction_debug.inc on line 27.
  • strict warning: Declaration of context_reaction_block::execute() should be compatible with context_reaction::execute() in /home/gdzinene/public_html/sites/default/modules/contrib/context/plugins/context_reaction_block.inc on line 524.
  • strict warning: Non-static method view::load() should not be called statically in /home/gdzinene/public_html/modules/acquia/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/gdzinene/public_html/modules/acquia/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/gdzinene/public_html/modules/acquia/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/gdzinene/public_html/modules/acquia/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/gdzinene/public_html/modules/acquia/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/gdzinene/public_html/modules/acquia/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home/gdzinene/public_html/modules/acquia/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/gdzinene/public_html/modules/acquia/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Non-static method view::load() should not be called statically in /home/gdzinene/public_html/modules/acquia/views/views.module on line 879.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/gdzinene/public_html/modules/acquia/views/plugins/views_plugin_style_default.inc on line 25.

We at GdZine follow the following steps for designing a web site based on XHTML and CSS.

MCOKUPS: We first design the mock-ups on Image Editors like Photoshop, GIMP, Illustrator or CorelDraw. Our designers create the mock-ups for client and then start finalizing it in a collaborative and iterative process via on-line collaborative tools.

SLICING: After finalizing the mock-up our coders start slicing the mock-up keeping the SEO, load-time optimization in mind.

REVIEW: When our developers finishes coding the initial version, our designers reviews it again and log issues in issue tracker if found. Then developers fixes the bugs and log it into the issue tracker. This process are iterative until our reviewers are satisfied with the quality.

PRIVATE-BETA: When our reviewers pass the site with their sign-offs and zero issue status in our issue tracker then we deploy it in our own demo server for review and UAT by our clients. Issue tracker is then opened for the client to log issues which in turns get fixed by our developers.

RELEASE: When our client are happy with the site we release the code base to the client or deploy it into the client’s server.