A METHOD OF ENABLING A THIRD PARTY TO CREATE A WEBSITE
BACKGROUND OF THE INVENTION
THIS invention relates to a method of enabling a third party to create a website.
The creation and management of a website can be particularly difficult for a person or organisation without the necessary skills. The present invention seeks to address this.
SUMMARY OF THE INVENTION
According to the present invention there is provided a method of enabling a user to create a website, the method comprising the steps of:
receiving, at a server, a request from the user to create a website;
forwarding client site builder executable code to a computer of the user via the Internet, wherein the executable code is adapted so that when it is executed on the computer of the user, it displays a plurality, of
website layouts to the user and allows the user to select at least one of the website layouts;
receiving, at the server, selection data from the user, the selection data representing at least one of the website layouts which the user has selected;
compiling web pages based on the selection data; and
populating the web pages with information submitted by the user for access via the Internet by a third party.
The method may further comprise the steps of:
receiving, at the server, a request from the user to insert information into the website;
providing the user, via the Internet, with a template for inserting the information;
receiving the inserted information from the user; and
storing the inserted information in a database.
Preferably, the method also comprises the steps of:
receiving, at the server, a request from the user to insert at least one of a site description, site keywords and a contact e-mail address for the website;
providing the user, via the Internet, with a template for inserting at least one of the site description, site key words and contact e-mail address;
receiving at least one of the site description, site key words and contact e-mail address from the user; and
storing the at least one the site description, site key words and a contact e-mail address in the database.
In addition, the method may further comprise the steps of:
providing the user with element manager executable code which allows the user to link pages and files appearing on their website to one another, the element manager further allowing the user to insert elements into the website;
receiving, at the server, a request from the user to insert links or elements into website; and
inserting the links or the elements into the website and storing these in the database.
The method may also comprise the steps of:
providing the user with advanced editor executable code;
receiving, at the server, a request from the user using the advanced editor executable code to format text in the website; and
implementing the formatting for the website and storing this in the database.
The present invention extends to a machine readable medium comprising instructions, which when executed by a machine, cause the machine to perform the method steps described above.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is an overview of the system of the present invention;
Figure 2 shows the client site builder of Figure 1 in more detail;
Figure 3 illustrates the site lay-out information section of the client site builder;
Figure 4 schematically illustrates the contents of a web plug-in;
Figure 5 illustrates the site colours section of the client site builder;
Figure 6 illustrates the site content section of the client site builder;
Figure 7 is a screen showing a first example of a content management page of the present invention;
Figure 8 is a screen showing a second example of a content management page of the present invention;
Figure 9 illustrates the image rescaler section of the client site builder;
Figure 10 illustrates the smart update section of the client site builder;
Figure 11 shows the server site manager of Figure 1 in more detail;
Figure 12 illustrates the flow upon receipt of a request to review the website; and
Figure 13 illustrates the element manager of the server site manager.
DESCRIPTION OF EMBODIMENTS
A computer-implemented system according to the present invention is designed to assist a user in setting up an online website without requiring the user to be able to program. The system allows the user to create and manage a fully unique and customizable website.
Referring to Figure 1 , the system employs a client site builder 10 which guides the user through a series of steps required for setting up and managing of the website. The client site builder 10 interfaces with a server site manager 12 to create and manage the user's database and cold fusion mark-up pages (CFM's) that form the customized website. The server site manager 12 creates the necessary database and/or entries and generates the cold fusion mark-up pages from a web collection. The user then utilizes the client site builder 10 and its accessories, which interface with the server site manager 12 to manage and manipulate the site. Essentially, the server site manager 12 processes and saves data and the client side builder 10 allows the user to input data and configure settings, which are then uploaded to the server site manager 12.
The client site builder 10 is an executable and/or active X application which is downloaded from the server site manager 12. In use, a user accesses the website of the server site manager 12 and registers with the server site
manager. The client site builder 10 is then downloaded to the computer of the user via the Internet.
This executable piece of code is then executed by the user on their computer and takes the user through several key steps. The modules of the client site builder 10 are shown in Figure 2.
Firstly, a login window appears. The user must enter their password, which is required by the client site builder 10 in order to decrypt the encrypted security key. Each user is provided with an encrypted security key, which contains all of the user's information. The client site builder will not function without the information contained within this security key.
When the correct password is entered, the user is taken to a welcome section which lists all the features of the current client site builder. If the user enters an incorrect password three times, he will be locked out from the client site builder, and an administrator will have to unlock the user's account by using the root administrative templates 48.
The user is then taken to a site layout information section, which allows the user to browse through the various web plug-ins 14. A web plug-in 14 or dynamic link library (DLL) contains files and information pertinent to a specific website layout. In one implementation, a web plug-in 14 contains style sheets, image colour mappings, HTML files, JavaScript files, flash files, images and plug-in information and functions. The user selects at least one of the website web plug-ins. The plug-in is loaded and plug-in information and a layout photograph are displayed to the user. This is illustrated in Figure 3.
The contents of a layout plug-in are illustrated schematically in Figure 4.
A site colours section allows the user to select the colours for their customized site. The colours range from font and link colours through to background, field and button colours.
The user is able to preview the layout and colour changes before they are finalized. Certain layout files are extracted from the web plug-in 14 and are modified based on the users settings. These modifications are then shown to the user using the Microsoft web-browser control 16 (in Figure 2). When the changes are saved, the site colours and layout specific files are stored in a data stream and are uploaded to the server site manager 12 where some of the settings are stored on the hard drive of the server and others in an SQL database. This is illustrated in Figure 5.
The client site builder 10 now takes the user through a site content section which interfaces directly with the server site manager 12 by using the Microsoft web-browser control 16. Thus, it will be appreciated that whereas for the previous information the selection occurred at the client site builder and was then uploaded to the server site manager 12, the site content input occurs directly during an on-line interface between the client site builder 10 and the server site manager 12. This is illustrated in more detail in Figure 6.
Using the site content section, the user is able to access various administration templates and tools available for management of the site. The user is able to create administrative accounts. The user can then assign permissions to the accounts restricting access to certain administrative templates and granting access to others. This allows the user to have a content team who could modify various areas of the site.
The user logs onto the server site manager and a list of the administrative templates are sent to the user.
The user selects an administrative template, which is then sent to the user. The user enters the necessary data and submits the template which is then processed by the server site manager and the submitted information is stored in a database which is accessed through the user's website.
Figure 7 shows one screen illustrating an administrative template, which can be accessed. All administrative templates are processed and created on the server site manager 12 and displayed in the client site builder 10. Referring to Figure 7, the user is given the option to deactivate the site using button 18.
The user is also given text field 20 for the site description and site keywords are put in text field 22.
In addition, an administrator e-mail field 24 allows the user to insert a contact e-mail address so that other parties viewing the website can get in touch with the site administrator.
Figure 8 illustrates another administrative template used to allow a user to add an article to their site.
The site builder 10 contains a built in visual article editor which is an executable and/or active X application. The visual article editor uses the Microsoft DHTML / MSHTML edit control which allows the client to insert hypertext markup language (HTML) components and manage them visually before they are converted to HTML code.
The user is provided with an element manager 66 tool which is loaded by the visual article editor and sometimes by the server site manager 12. The element manager constantly determines all the possible links and visual elements available in a user's site by interrogating the SQL database.
The element manager provides the user with:
• A link collection is a list of pages and files the user has created by using the administrative templates. This list gives the user flexibility when linking to information. These links are compiled into a list which is displayed to the user by either the visual article editor or in some cases it will be included in an administrative template. To insert a link, the user would click the insert link button located in the visual article editor. A drop-down list would then appear with a list all of the available links, the user would select a link and it would be inserted into the article.
• An element collection is a list of visual website elements created and/or configured by the user when using the administrative templates. The element collection consists of elements such as graphs, calendars, live feeds and imbedded pages etc. To insert an element, the user would click the insert element button located in the visual article editor. A drop-down list would then appear and list all of the available elements, the user would then select the desired element which would then be inserted into the article. Elements are inserted into articles using a tag based language. For example, an article which is created by the user could contain a line of code such as <MG_ELEMENT TYPE="graph" ID="34">. When this article is displayed on the user's site, the graph created and/or configured by the user will be inserted into this article in place of this code. The graph in this case has an ID of 34. ID's are incremental and are created automatically by the SQL database.
The visual article is activated by clicking the "Load advanced editor" button 26 and includes the following formatting functions:
Bold Indent Underline Align left Align center Align right Numbered lists Bulleted lists Decrease indent Increase indent Font colour Font type
ion, the following features are included in the editor:
Inserting tables with and without headings
Table conversions and repairs
Table cell modification and repair
Misc. table design options
Horizontal rules
Inserting of photographs
Inserting of email addresses and web addresses
Inserting of links from the link collection, generated by the element manager
Inserting of anchors
Inserting of visual elements from the element collection, generated by the element manager
Referring back to Figure 8, the heading of the article is inserted into a heading text field 28 and the article content is inserted into a text field 30. Buttons 32 allow a user to format the text.
An article output field 34 shows the user what the article content will look like when it is viewed on the site.
Layout option fields 36 allow the user to adjust the vertical position, article width and article order. An upload photo field 38 allows the user to insert a photo into the article.
An image rescaler section 40 allows the user to rescale or compress images before adding them to the site.
Finally, the date of the article expiration can be set using fields 42.
Figures 7 and 8 are just 2 examples of many administrative templates such as voting polls, administrative accounts, email accounts, export data to various formats, message forums, calendars, search engines, live feeds, menus, photo galleries etc.
Referring back to Figure 2, an image library 44 or dynamic link library (DLL) contains advanced functions that are needed for the modification of website elements in the form of images and photographs. The client site builder 10 and server site manager 12 load the image library upon initialization in order to utilize the functions. These functions include:
1. Rescale images
2. Overlay images with alpha settings
3. Create JPEGS, GIFS, BMP and various other formats
4. Conversion of one format to another
5. Replacement of colours in images
6. Dynamic creation of images based on client's setting.
This is illustrated in Figure 9.
The extras library 46 (Figure 2) or dynamic link library (DLL) is a resource library, which contains miscellaneous files and functions used by the client site builder 10.
A help file and demos 48 are deployed with the client site builder. The help file guides the user through all the procedures required to successfully manage the website. The demos are step-by-step graphical presentations of each of the administrative templates. The help file is stored in the Microsoft HTML Help format and the demos are in flash format. The help file is executed from the client site builder and the demos are displayed by using the Macromedia Flash control 52.
Referring to Figure 10, a smart update tool (not shown in Figure 2) is used by the client site builder to determine if newer versions of the client site builder 10, web plug-ins 14, image library 44, extras library 46, help and demos 48 are available. The smart update tool communicates with the server site manager 12 via the Internet. The smart update tool determines if newer versions exist by using CRC (Cyclic Redundancy Check). The smart update tool notifies the user and based upon their response, downloads a compressed archive and installs the newer versions on the user's computer. The compressed archive contains the newer files. These files are compressed using the Zip algorithm contained in the Zip library or dynamic link library (DLL), which is loaded by the server site manager and client site builder.
Figure 11 illustrates the server site manager 12 in more detail. The server site manager 12 is built with Flash, HTML, XML, CFML and JavaScript and runs on
Macromedia Cold Fusion Server and uses an SQL database 54. The preferred operating system is Microsoft Windows Server with an Internet information server and Microsoft SQL Server, but this system can be deployed on a Linux / UNIX platform, for example. The server site manager does not have to be programmed in CFML, other server side languages may be used.
The server libraries or dynamic link libraries 56 are libraries are used to perform tasks that the server side language (CFML) cannot.
The server libraries are used to:
1. Check files using CRC (Cyclic Redundancy Check) which is used during the smart update process.
2. Manage the web server.
3. Export data from the SQL database to various file formats.
4. Modify / create images.
5. Extract data from the web plug-ins.
6. Create security keys.
7. Create dropper files. The security key is combined with a deployment application which is used to install the security key on a user's system.
8. Create compressed data stream files. These files contain information which is loaded and used by the client site builder.
9. Compress and decompress files using the zip algorithm.
Root administrative templates 48 created for the root administrator, use the server libraries which are necessary for successful management of the server.
The root administrative templates are used to:
1. Create, edit and delete web sites
2. Create, edit and remove data sources
3. Start and stop services on the server
4. Stop and start web and ftp sites
5. Update the user administration menus
6. Configure application settings such as version number, administrator email, features, various administrative URL's, and storage and log paths.
7. Export user data to various formats.
8. Update FAQ's.
9. View log files.
10. Schedule server tasks.
11. Unlock users who have been locked out.
12. Send security keys to users.
13. Email users; files can be attached to emails.
14. Process requests for site creation from new users. New users can register on a registration site.
A log file directory 60 is created for each user. A new log file is created every month and a log entry is created for every administrative task that the user performs.
A web collection 62 contains a plurality of layouts, each of which corresponds to a particular web plug-in. A collection of layouts has been created, each of which contain several variations in order to give the user a wider variety of possible site layouts and styles.
Layouts, which are made up of Flash, CFML, XML, HTML, JavaScript, images and style sheets, are categorized. New layouts are constantly being created and added to the web collection. In order for a layout to be utilized and modified, the client must have the pertinent web plug-in. The web plug-in
contains settings, functions and files necessary for successful layout selection and usage.
A directory 64 is created for each user. All files, style sheets and images submitted by the user are stored in this directory. Referring to Figure 12, the user's website points to this directory as its entry point. When a visitor reaches the user's site, the website opens the default document for this directory and displays it to the visitor. This default document determines the user's settings by querying the SQL database. The selected layout is then loaded from the web collection and populated with information submitted by the user. Based on the layout - style sheets, images, XML and flash files may be loaded.
All information submitted by the user that will be available to visitors is stored in the SQL database.
Thus it will be appreciated that the present invention allows the user to create and manage a website without any technical programming skills.