Technical Architectureīased on the solution sketch, which provides an orienting roadmap for this work, we will design the back-end platform for the project. Frequently, we add additional load balanced servers during launch to handle a larger-than-normal amount of web traffic.Īfter the launch period has passed (usually a few days), we move the site into hosting, support, and maintenance. Following the launch, we have several developers monitoring the site to be sure that there are no problems. So, we test the site again.Īt the launch time, we move the site to the production server. This server is a copy of the production environment. When the site has passed testing, we move it to a staging server. There are frequently areas to adjust or change once they are seen live on the site. We follow the content and functionality design concept.įollowing the migration, integration, and functionality development, we perform testing and revision. But it could also include dynamic content areas, featured content, custom integration, CiviCRM functionality, syndicated content, and so on. This includes search and contact forms at a minimum. In this way, a set of content can be merged with just a handful of templates to create a site that has hundreds or thousands of pages.Īfter this is complete, we create all the server-side functionality required. Each new page instantiates a template and a content type. As this process progresses, the site "builds out" from a set of just a few placeholder templates to a full site. Once this is complete, the designs can be seen (again, looking just like the designs) on the Drupal site.Īfter the templates are in Drupal, we can migrate the content into the site. Drupal's templates are considerably more complex than simple HTML templates, so it takes some careful work to add those HTML templates to the site in the proper way. Once the HTML templates are complete, we integration them into the Drupal website. We use HTML, CSS, JavaScript, jQuery, and other client-side (browser-side) tools to create these templates. This includes development of all the on-page interaction, e.g. These HTML templates will look exactly like the visual design (something we pride ourselves on). For each visual template, we will develop an HTML version. One input is the visual design templates. So, there are many inputs to this component. The development phase of the work combines work streams from several areas.
0 Comments
Leave a Reply. |