The new website was designed as a single-page architecture and a common main page was created for both the desktop application as well as the mobile version. The main pages were designed so that they loaded other Sitefinity pages dynamically as content. The relevant markups and scripts were added to both main web pages. This allowed content to be edited for different devices, thus giving the system the ability to load the content both asynchronously as well as dynamically. Responsive Design was the ideal solution because of its ability to combine a single-page architecture with the relevant markups and scripts.
As far as content was concerned, Responsive Design was ideal insofar as it allowed content to be managed in Sitefinity lists that could then be expanded using custom fields, giving the user the ability to centrally manage his or her content. Within that process, some custom fields were developed, others were customized. In addition, that solution was used to reduce the number of potential errors to a minimum, thus maximizing usability.
Another objective was to develop custom controls accordingly, which generated content based on the lists on the Sitefinity pages. Within that process the page structure was reproduced using Sitefinity pages. The custom controls that were developed in an earlier step were integrated as placeholders on every page as a way to generate and present content. Having in mind the above mentioned reason and in order to be able to allow increased flexibility, the custom controls were equipped with selectors (e.g. page selectors).
Then, the Java script functions of the single page were customized so that all of the Sitefinity pages could be loaded dynamically and asynchronously into the main page (single page architecture).
That structure made it possible for every device to use the same page, which could then generate its content dynamically on demand.
A web service needed to be implemented for the content of the start page, which could then communicate with the Sitefinity lists and dynamically read the images for the start page. What required special attention here was finding a way to assure that the content of the start page would not be identical with other lists, because at that point only images were used. The Sitefinity lists combined with custom fields made it possible to implement that solution flawlessly. Because of the different workflows, it became necessary to modify the Sitefinity preview mode. Having in mind that the single page architecture was required, the preview mode needed to be customized. Within that process, the roles as well as the status and the lifecycle of the various CMS elements were taken into account.