KR100522186B1 - Methods for dynamically building the home page and Apparatus embodied on the web therefor - Google Patents

Abstract

The present invention is a web server; A homepage production module mounted on the web server; A database for storing selection information received from the user for generating a home page according to a user's request; Information about selecting the original file by using a text storage including a main page layout of the home page and a home page original file for each menu according to the style category of the home page, and a file repository constructed to be linked to the homepage production module. This information is related to how to create a customized home page by receiving this information. In particular, the homepage produced in the present invention is characterized in that it is produced to share the web style with the main homepage.

Description

Methods for dynamically building the home page and Apparatus embodied on the web therefor}

The present invention relates to a method for producing a homepage on the web, and more particularly, a user arbitrarily selects an original file of a webpage created by referring to a style guide so as to maintain a main homepage and a webstyle. It is about how to.

On the Internet, homepages are represented in hypertext. However, since this hypertext is defined in a language called HTML, it is recognized that HTML must be known in order to produce a homepage. However, with the development of a program called Editor, this idea is no longer correct. In other words, the editor can help you create a homepage even if you don't know this HTML at all. Users can easily create a homepage by mastering some features of the editor as if using a Hangul program.

Previously, these editors worked offline. Therefore, the user must involve uploading the home page created using this editor back to the Internet (typically uploading the file using FTP). However, this process has caused a new problem in that it is not familiar to the user.

It was developed by paying attention to such a point, and "Home Page Method" of Hi-Home Co., Ltd. (Registration No. 10-326425). HiHome's home page creation method starts by the user connecting to a server that manages the homepage and running the editor. The user simply finds and selects pages with different layouts (made in HTML) and edits them to create a single page. This process (the process of selecting and editing layouts) is produced several times in sequence for the pages used on the homepage. The homepage can be produced online by registering the created homepage on a server.

Accordingly, users can conveniently create a homepage online while solving the above-mentioned problems.

Meanwhile, with the development of the web production technology, the homepage networking has been progressed. That is, a new type of homepage production technique has emerged, in which a main homepage and subordinate sub-homepages thereof have an organic relationship with each other like a computer network. Institutions and corporations with large organizations needed homepages for each department (sub homepage), and this sub homepage needed to be organically connected to the main homepage of the entire group.

As a result, a new concept of 'web style' emerges, and this web style is about a homepage production technique that allows homepages to have independent subjectivity and to make users feel as if the homepages are connected to each other. Looking briefly at the development of style in the web agency market, it was the first time in Korea that the concept of style was introduced to the web. The web style of this period is the first-generation style. This first-generation style of static concept is to develop the main homepage and organize the style applied to the main homepage into a booklet (generally called a 'style guide'). This first generation style has been widely used in the market to date. Next comes the dynamic style, the second generation concept. This second generation web style is designed so that the web style of the homepage can be changed all the time, so that the service user can change the web style without any manual work, but only the style guide is dynamic, and the actual site production is a manual process. In other words, the style guide is composed of several sub-concepts, and these sub-concepts are automatically changed and combined by the user. However, based on the completed style guide, the web site is a manual process.

As mentioned briefly above, the traditional method used to incorporate web styles into sub homepages is to create style guides. In other words, if you make a booklet that summarizes the styles applied to the main homepage, and make a sub-homepage, refer to this guide to make a sub-homepage. Therefore, the cost of producing the sub homepage according to the main homepage is the same as or higher than the main homepage. As a result, a large homepage cost has been incurred in producing a sub-homepage in an institution or a company with many sub-organizations.

Meanwhile, at the time when the homepage production method of the high home was developed (before 1999), homepage production methods were developed with the intention of producing a single homepage, and the homepage production method of the high home was simply related to the production of one homepage. It just happened. Therefore, this homepage production method of the high home is very useful for producing a small homepage, such as a personal homepage, but is not preferable for producing a homepage of a network composed of a homepage having a multi-characteristic nature of a complex environment.

In particular, it is necessary to maintain a unified style between the main homepage and the sub homepage on the network homepage. However, the production method of the high home does not allow the sub homepage to reflect the style of the main homepage. According to the manufacturing method of the high home, the homepage is simply produced while sharing the layout of the pages within the same homepage.

Moreover, in creating the homepage of the network, the homepage should be created flexibly by reflecting various variables, not the style (the first generation webstyle). Since the homepage is created by editing the templated pages), it is possible to create a static web style and a homepage similar in shape to the pages used for a single homepage.

In addition, HiHome's homepage creation method relates to a static homepage production method that has a page already made in HTML and edits the page itself. Thus, the appearance of the home page can be modified within the range of the tools given in the editor and the pages given in the form of templates. Therefore, only a limited form of homepage can be produced.

In addition, the web style of the second-generation concept described above, the user of the web style itself captain arbitrarily, but the production of the homepage reflecting the changed web style has to be made by manual.

The present invention was devised to solve the above problems, and it is intended to provide the present invention that enables a homepage to be produced by a user's simple mouse click without sharing the style between the homepages in producing the homepage.

Another object of the present invention to produce a homepage, to provide a sub-homepage to the present invention to produce a sub-webpage in a variety of web styles.

Another object of the present invention is to provide the present invention that can directly operate the homepage according to the application of the account without having to perform a separate process on the homepage because the homepage is working on the web.

Another object of the present invention to produce a home page, the user is to provide the present invention that can create a home page by selecting the original file for each menu of various web pages that are simply provided, and creating a text to be used in the web page .

The present invention to achieve the above object, Web server; A homepage production module mounted on the web server; A database for storing selection information received from the user for generating a home page according to a user's request; And a file repository for storing the homepage original files for each menu according to the main body layout of the homepage and the style category of the homepage, and the file repository constructed to be linked with the homepage production module. (A) receiving a homepage account request from a user and registering the user's web account with the web server by the module; (b) The user may select style category selection information of the home page, the source file included in the selected style category, and selection information for specifying the source file according to the menu used for the home page and the text layout of the web page for each menu. Receiving from the home page basic information storage unit of the database; (c) Receives the text contents to be stored in the web page for each menu from the user and stores it in the text storage section for each page of the database, and generates the text file in a format that can be dynamically referenced by the original file. Recording on; And, (d) for each menu, parsing the home page original file to include the body content contained in the body file, and storing the web page in the user's web account;

Preferably, the database further includes a menu structure storage unit for storing menu information such as a menu name, a URL, and a depth, and optionally a menu from the menu structure storage unit according to the menu selected in step (b). Extracting information to construct a user-specific menu structure storage unit; And defining a moving path between web pages by referring to the menu structure storage unit, generating a URL file in a format that can be referred to by the generated web page, and storing the URL file in the web account.

More preferably, after performing step (b), referring to the homepage basic information storage unit, parsing the original file selected by the user and storing the webpage in the web account of the user; The web page of step (d) is stored as the new web page.

More preferably, the file storage further comprises the step of recording an image file, receiving the selection information of the image file in step (c), and including the selected image file in the web account.

In another aspect of the present invention, an apparatus for implementing the above methods is provided.

The present invention relates to a method for producing a homepage, and more preferably, to a method and apparatus for producing a homepage while maintaining a sub-homepage subordinate to the main homepage with the same web style as the main homepage. In particular, the present invention relates to a method for producing a home page without the process of creating a home page on the web and separately putting the home page on the web.

In the present invention, the web pages constituting the home page do not need to be produced by the user individually, and the web pages are provided by the producers in large numbers according to the category for each style of the home page. The user simply selects one of the styles and decides which menus to use on the home page. Web pages used on the home page are automatically created.

The present invention is very useful for producing a homepage of a large site. In particular, if there is an organization and the homepages of departments attached to the organization are produced in the same style as the main homepage, it can be more usefully used.

1 is a view showing the configuration of the present invention. With reference to this drawing, the structure of this invention is demonstrated in detail.

A system embodying the present invention includes: a web server (10) for processing HTTP requests over the Internet (200); Through the user interface produced by the web page illustrated below, information necessary for customizing and producing a homepage is received from the user and stored in the database 13, and the original file is selected with reference to the information. A homepage production module 11 for converting an original file into a webpage and storing the webpage into a user's web account of the web server; A file store containing an original file 121 necessary for producing a home page, an image file 122, and a menu script file 123 defining sources for the shape and operation of a menu that is used identically for each web page on the home page ( 12); A database 13 containing various information necessary for the production of the homepage; It is configured to include a user-specific web account 14 provided in the web server 10.

The user-specific web account 14 includes web pages generated from the original file, images used for the web pages, URL files, menu script files for user-selected menus, site titles and introductions. Such as title script files.

The web server 10 is typically a device that operates as a server that allows the homepage to be operated on the web. A server operating program (eg, a Windows 2000 server program) is installed in the web server, and the server setting is performed by using this program so that one or more websites can be operated. Typically, servers are functionally divided into a plurality of independent units, for example, a web server that processes HTTP requests, a database server that manages information, and an application server that stores programs. Each module and database is preferably designed as such an independent unit.

The homepage production module 11 is functionally composed of a homepage conversion module 111 and a data management module 112,

The homepage conversion module 111 converts the original file 121 contained in the file storage 12 into a web page and stores the original file 121 in the user-specific web account 14 built in the web server 10.

The data management module 112 is a component for editing a record of a database such as reading, writing, updating or deleting records recorded in a database, and inputting a query to the database 13 to perform a necessary task. Do this.

In the present invention, the database 13 is the user information storage unit 131, the homepage basic information storage unit 132, the menu structure storage unit 133, the user-specific menu structure storage unit 134, body content storage unit 135 And a title information storage unit 136.

The user information storage unit 131 is information used for issuing a web account to the user with the identification information, including identification information such as ID and password.

The home page basic information storage unit 132 stores information necessary for producing a home page customized by a user, and includes category selection information, style selection information of the home page, and menu selection information used in the home page. The category selection information and the style selection information are information for selecting a category of an original file provided in a category for each style selected by the user (eg, graduate category and style A), and the menu selection information is information about menus used on the homepage. In particular, in the present invention, the original files are provided in groups according to the style-specific categories, and each group includes the original files corresponding to all menus available on the homepage. The selection information of the menu is directly used to select the original file.

The menu structure storage unit 133 stores information about menus used in the present invention, and includes information about a menu name, a URL, and a depth of the menu.

The menu structure storage unit 134 for each user includes menu structure information on a menu selected by the user in the menu structure storage unit 133 according to the user.

The body content storage unit 135 stores the body content used in the web page. Separate body content is stored according to each web page, and is divided according to the user.

The title information storage unit 136 stores a site name used in the homepage, an English name, an administrator, a keyword to be used for a search, an article describing the homepage, and a footer. Of these, the site name and footer are processed as variables of the title script file and stored in the user-specific web account.

On the other hand, the original file is distributed by the producer, such as the homepage production module 11, the file storage 12 is built to be associated with the homepage production module (11).

In the present invention, the original file 121 is provided grouped according to the category-specific style and the menu available on the homepage. Preferably, each original file is also provided according to the layout of the text used in the web page. Therefore, the user selects a group, selects an original file, and selects a menu to specify a web page to be used on the home page. The above-described classification of the original file is an example and may be classified into various formats.

On the other hand, the original file is preferably written in XSL (extensible style language) language, the source file contains information about the layout of the web page, the location for the content constituting the web page generated from the original file Contains information.

With reference to the accompanying drawings the process of producing a homepage online using the apparatus 100 of the present invention configured as described above will be described in detail below.

The homepage manufacturing method of the present invention can be largely described in four steps as shown in FIG.

Firstly, the user's web account is created in a web server (S100); Next, collecting selection information related to the home page to be produced from the user (S200); Creating a web page based on the selection information, recording the web page in the web account generated in the step (S100) and uploading the home page to the web (S300) and editing the text used in the web page for each web page It is described in step S400.

The step S100 is a process of creating a sub homepage account in the web server 10, and the production module describes a process of receiving a homepage account application from the user and creating a web account of the user in the web server. In one example, when the domain of the main homepage is 'www.sogood.co.kr', the domain of the sub-homepage (homepage produced according to the present invention) is generated as www.sogood.co.kr/~user.

The step S200 describes a process in which the module 11 receives selection information necessary for constructing a web page from a user in order to produce a web page constituting a home page. In the present invention, the web page is created using the original file, which is distributed by the producer and is built in the file repository 12.

The step S300 describes a process of generating the original file as a web page by using the above-described original file and the selection information collected from the user, and recording the original file into the web account.

Finally, the step S400 describes a process of producing a text for each web page used in the web page generated in step S300.

Hereinafter, an online embodiment for producing a homepage using a user interface provided by the present invention while a user is connected to the web server through the web will be described.

Prior to the description, it is assumed that the user's web account 14 is created in the web server 10. The setting process of the web server for issuing the web account 14 to the user can be easily performed by those skilled in the art. have. Therefore, detailed description thereof is omitted.

First, FIG. 3 is a flowchart illustrating a process of selecting a source file of a web page for use by a homepage in detail, and FIG. 4 illustrates a user interface used in this process.

Referring to the figure, the user accesses the web server via the web 200 and receives the web page as shown in FIG. 4a to display the web page with a browser mounted on the user's terminal (generally, a personal computer).

Then, the user selects the selection item 601 of the web page with the mouse, clicks the confirmation button 602, transmits the selection information of the category, and receives a new web page as shown in FIG. 4B. Similarly, display a new web page.

On the other hand, the selection information of the category selected by the user in step S210 is transmitted to the web server 10 via the web 200, the data management module 112 receives it and the homepage basic information storage unit of the database 13 ( 132) (S210).

The user can use the basic information used in the homepage produced in the web page of FIG. 4B, namely, the site name of the reference number 611, the English name of the homepage of the reference number 612, the homepage manager of the reference number 613, the search keyword of the homepage of the reference number 614, Information necessary for each item, such as an article introducing the homepage 615 and a footer, is filled in a box, and the confirmation button 616 provided on the web page is clicked to transmit title information to the web server 10. Then, the data management module 212 receives title information selected and input by the user from the web page shown in FIG. 4B and records the title information in the title information storage unit 136 (S220). In addition, the homepage conversion module 111 that receives the title information processes the site name and the footer among the received title information as variables to generate a title script file that the original file dynamically refers to, and the user-specific web account 14 To be included. Preferably, such script files may be written in JavaScript format, but the present invention is not limited thereto.

Hereinafter, the data transmission between the web page and the web server which are repeated in the same manner as described above for each step will be briefly described.

Next, when a user selects a style of a homepage using a web page as shown in FIG. 4C newly received and viewed through a browser, style selection information of the homepage is also stored in the homepage basic information storage unit 132 (S230). ). Here, the style of the homepage is provided in advance by the producer according to the category of the homepage selected by the user in FIG. 4A, and an example of each style is selected and used from the image files included in the file storage 12. Therefore, the image file is classified in the same form as the original file and stored in the file storage 12.

In step S240, the user receives a web page as shown in Figure 4d, the user selects menus used in the homepage to be produced using this user interface, the selection information of the selected menu is transmitted to the web server 10 The homepage basic information storage unit 133 is stored (S240). In addition, the home page conversion module 111 selectively copies a menu script file corresponding to the menu selected in the step from the file storage to a user-specific web account.

Accordingly, the selection information of the original file (that is, the selection information of the web page created according to the user's request) required for generating the web page used in the home page is the homepage basic information through the above-described steps S210, S230, and S240. In addition to the storage unit 133, reference files for elements commonly used in the homepage are also included in the user's web account.

The homepage conversion module 111 may selectively search for and parse original files selected by a user from among a plurality of style categories of original files included in the file storage 12 with reference to the homepage basic information storage unit 133. To be stored in the user's web account 14 as a web page.

For example, if the user has made a selection as shown in Figs. 4A to 4D, the menu selected by the user in the path of the file storage 12 in which the original file corresponding to the style 1 of the university category is stored, That is, the original files corresponding to the default layout corresponding to home, university guide, department introduction / history, course information, faculty, and graduation requirements are parsed and stored as web pages in the web account 14 assigned to the user. do. At this time, the title script file generated by processing the site name and the footer as variable values with reference to the site name and the footer among the information contained in the title information is stored in the web account. Meanwhile, the generated web page is missing a text to be recorded by the user, and a process of including text contents necessary for the web page will be described later.

The links between web pages are broken in the current homepage. Hereinafter, a method of connecting links between web pages generated according to the present invention will be described with reference to FIG. 5.

The original file that creates the home page contains a script that handles links between web pages, as described below. Thus, by defining a URL file (which defines a link between web pages) that the script can reference, links between web pages are created.

In the menu structure storage unit 134 of the database, data defining menu names, URLs, and depths are stored according to the style of each category. Preferably, the menu structure storage unit 134 is distributed by the producer as the original file.

In addition, the homepage basic information storage unit 132 stores selection information of a web page for each menu used by a user through the user interface of FIG. 4D.

Accordingly, after the web page conversion module 111 generates the web page from the original file, the same menu is stored in the menu structure storage unit 133 with reference to selection information of the menu included in the homepage basic information storage unit 132. The information about the field is extracted and stored in the user-specific menu structure storage unit 134 (S310).

The web page conversion module 111 stores information (URL and menu name) stored in the user-specific menu structure storage unit 134, and generates a URL file that can be referred to by the script to generate a user's web account. Write to the designated path of 114 (S320, S330). The URL file may be written in an XML format and included in a user's web account, but the present invention is not limited thereto.

The web page generated by the home page converting module 111 contains a menu script for implementing a menu interface as described above, and a code referring to the title script described above (see the original file creation example below). Here, the script may be JavaScript, but the present invention is not limited thereto. When the web page is transmitted to a web browser via the Internet, the menu script and the URL file and title script it refers to are loaded into a memory area referred to by the web browser, and the menu script is loaded as soon as the web page is loaded. Output the interface as a graphical interface. And, the link code for each menu is set as a factor of page movement when a mouse click event occurs. In the header and footer areas of the web page, code referring to the title script reads the title script and inserts a site name in the title tag and a footer in the footer.

Accordingly, when the user clicks a menu on the home page generated from the original file, the user can move to another web page by referring to the URL file.

In the above, step S200 and step S300 described above have been described, and step S400 will now be described.

Optionally, before creating the text, the user can edit the structure for the menu selected above. 6 illustrates a user interface used by a user to edit the structure of a menu.

The user clicks on buttons 711, 712, 713, and 714 provided on this web page with a mouse to correct the position 71 of the menu. Accordingly, the correction information of the menu, that is, the correction information of correcting the depth of the menu, is generated and transmitted to the web server. Then, the data management module 112 modifies the index of the depth of the menu included in the user-specific menu structure storage unit 134 with reference to the modified information, and changes the above-described URL file to the modified user-specific menu structure storage unit ( The new URL file is updated with the new URL file by creating a new one referring to 134).

Similar to the editing of the menu structure described above, in the present invention, it is also possible to add or delete menus. Modification information generated by adding or deleting menus is transmitted to a web server, and the data management module 112 transmits the modified information. For reference, the menu selection information of the user included in the homepage basic information storage unit 132 is modified. In addition, accordingly, information of the menu contained in the user-specific menu structure storage unit 134 is also modified, and the URL file contained in the user's web account is also updated.

7 is a flowchart illustrating a process of creating a body used in a web page for each menu, and FIG. 8 illustrates a user interface used to create a body, and FIG. 8A illustrates a web page corresponding to a one-depth menu. FIG. 8B is a user interface for editing a body of a web page (lower page dependent on a menu) corresponding to two depths.

As can be seen from the attached user interface, the text editing of each web page in the present invention is performed in the same way. That is, the layout of the web page is determined, an image used in the web page is selected, and a text is prepared.

First, in FIG. 8A, the user selects an item of a menu to be edited in the menu selection window 91 on the right (S410). The user interface for editing the selected menu item is then displayed on the user's terminal.

In this web page, the user clicks on the layout selection item 92 of the body with a mouse to determine the layout (S420). Then, select an image file (S430) to be used here. When the browse button is clicked, an image file that can be used is shown among the image files 122 included in the file storage 12, and any one of the image files is selected. Specify the image to use. Then, when the body content is input to the window 94 for inputting the body content (S440) and the input button 95 provided on the web page is clicked, the layout, selection information of the image file, and the body content are displayed on the web. It is transmitted to the server 10 (S450).

Then, the data management module 112 inputs a query for recording the body content in the database 13 and stores the body content received in the body content storage unit 135 according to the user and the web page (S460). At the same time, the body content is generated as a body file in a format that the original file can refer to, and the body file is stored in a place defined in the web page (S470). The body file is stored in an XML format in one example, but is not limited thereto.

In addition, the data management module 112 searches for a selected image among a plurality of image files included in the file storage 12 according to the image file selection information, and records the selected image file in the user's web account (S480). ).

Finally, the layout selection information of the received text is used to specify the original file. That is, the selection information of the original file included in the homepage basic information storage unit 132 through the above-described process includes only the menu. By the way, the original file is a category by style; A menu used in the homepage; The layout of the web page body for each menu; is provided in a hierarchical grouping. Therefore, when the menu is selected, it is only defined as a default, and the original file is specified according to the selection information by receiving the layout selection information.

FIG. 8B shows a user interface for creating a body used for a web page for each two-depth menu, except that there are only differences in menu hierarchies, and data processing is performed in the same manner, and thus detailed descriptions of the drawings will be omitted.

However, if the present embodiment is configured to select the layout of the body even at two depths, there is only a difference that the original file is specified when the selection information is received through Fig. 8B.

Accordingly, the selection information necessary for specifying the original file is preferably input from the user, and the selection information is stored in the homepage basic information storage unit 132. In addition, the user-specific web account 14 has completed the preparation of the text files of the text that the specified original files refer to.

Finally, the webpage conversion module 111 calls the original files stored in the file storage 12 by referring to the selection information contained in the homepage basic information storage unit 132, parses them, and stores them in the body file. Include the text and save it as a web page in your web account.

Accordingly, when a newly created homepage is requested, the requested webpage is extracted from the web account and transmitted to the terminal used by the requester. Then, the browser interprets and displays the received web page according to HTML grammar, and completes the web page by reading content (text content, image, script file, etc.) to the address defined in the web page.

Example of making original file

The source file below is an example written in XSL (extensible style language) language. The source responsible for the menu part is defined to be common to all web pages using JavaScript. In addition, the movement between web pages is composed by referring JavaScript to "menu.xml" which contains the menu items and the URLs of the items, and defines the movement between pages. On the other hand, the body content is not contained in this original file, but only contains information on where the body file containing the body content exists (i.e., a specific location in the file storage), so that the browser is created from this original file on the terminal. In the process of loading and reading web pages, text files are retrieved from the location.

<html>

<head>

<title>

<xsl: value-of select = "page / title" />

</ title>

<LINK rel = "stylesheet" type = "text / css">

<xsl: attribute name = "href">

  / wsl2 / designs / siteSkin /

<xsl: value-of select = "/ page / siteDesign / siteSkinId" />

  /site.css

</ xsl: attribute>

</ LINK>

<LINK rel = "stylesheet" type = "text / css" href = "page.css" />

<LINK rel = "stylesheet" type = "text / css" href = "logo.css" />

<LINK rel = "stylesheet" type = "text / css" href = "user.css" />

<LINK rel = "stylesheet" id = "menuCss" name = "menuCss" type = "text / css" href = "" />

<script src = "/ wsl2 / js / wsl2.js" language = "javascript" />

<script src = "/ wsl2 / js / searchForm.js" language = "javascript" />

<script src = "/ wsl2 / js / loginForm.js" language = "javascript" />

<script src = "/ wsl2 / js / quickLinks.js" language = "javascript" />

<script src = "/ wsl2 / js / control.js" language = "javascript" />

<script src = "msg.js" language = "javascript" />

<script src = "/ wsl2 / js / menu.js" language = "javascript" />

<script> var menu = new treeMenu ("menu.xml"); </ script>

</ head>

<body>

<script language = "javascript" src = "header.js" />

<DIV class = "WslFirstPageContentArea">

<!-WslFirstPageContentArea

->

<xsl: attribute name = "style">

  background-image: url (

<xsl: value-of select = "/ page / bgImage" />

  );

</ xsl: attribute>

<xsl: apply-templates select = "page / banner0" />

<xsl: apply-templates select = "page / content" />

<div style = "font-size: 10pt; height: 10pt;" />

<table border = "0" cellpadding = "0" cellspacing = "0">

<tr>

<td width = "256">

<xsl: apply-templates select = "page / extServices / extService [extServiceId = '100' and subInfo = '0']" />

</ td>

<td width = "22" />

<td width = "256">

<xsl: apply-templates select = "page / extServices / extService [extServiceId = '100' and subInfo = '1']" />

</ td>

</ tr>

<tr>

<td colspan = "3" height = "5" />

</ tr>

</ table>

<div style = "font-size: 10pt; height: 10pt;" />

<table border = "0" cellpadding = "0" cellspacing = "0">

<tr>

<td width = "260" valign = "top">

<table cellpadding = "0" cellspacing = "0" style = "border: 1pt solid # c3c3c3;">

<tr>

<td align = "left" style = "background-color: # edf5fc; border-bottom: 1pt dotted # c3c3c3; padding: 2pt;">

<img hspace = "4">

<xsl: attribute name = "src">

  / wsl2 / designs / siteSkin /

<xsl: value-of select = "/ page / siteDesign / siteSkinId" />

  /bullet.firstpage.cgi.gif

</ xsl: attribute>

</ img>

<span class = "WslFirstPageCGITitle"> Photo Bulletin </ span>

</ td>

</ tr>

<tr>

<td>

<iframe width = "100%" height = "150" frameborder = "0" leftmargin = "0" topmargin = "0" scrolling = "no">

<xsl: attribute name = "src">

  /wsl2/ListPhotos.do?serviceId=

<xsl: value-of select = "page / serviceId" />

& view = firstPage

</ xsl: attribute>

</ iframe>

</ td>

</ tr>

</ table>

</ td>

<td width = "13" />

<td width = "260" valign = "top">

<table cellpadding = "0" cellspacing = "0" style = "border: 1pt solid # c3c3c3;">

<tr>

<td align = "left" style = "background-color: # edf5fc; border-bottom: 1pt dotted # c3c3c3; padding: 2pt;">

<img hspace = "4">

<xsl: attribute name = "src">

  / wsl2 / designs / siteSkin /

<xsl: value-of select = "/ page / siteDesign / siteSkinId" />

  /bullet.firstpage.cgi.gif

</ xsl: attribute>

</ img>

<span class = "WslFirstPageCGITitle"> Question </ span>

</ td>

</ tr>

<tr>

<td>

<iframe width = "100%" height = "150" frameborder = "0" leftmargin = "0" topmargin = "0" scrolling = "no">

<xsl: attribute name = "src">

  /wsl2/VoteForm.do?serviceId=

<xsl: value-of select = "page / serviceId" />

& view = firstPage

</ xsl: attribute>

</ iframe>

</ td>

</ tr>

</ table>

</ td>

</ tr>

</ table>

<div style = "font-size: 10pt; height: 10pt;" />

</ DIV>

<script language = "javascript" src = "footer.js" />

<script src = "/ wsl2 / js / loginForm2.js" language = "javascript" />

</ body>

</ html>

</ xsl: template>

<xsl: template match = "banner0">

<xsl: if test = ".! = ''">

<img>

<xsl: attribute name = "src">

<xsl: value-of select = "." />

</ xsl: attribute>

</ img>

<br />

<div style = "font-size: 5pt; height: 5pt;" />

</ xsl: if>

</ xsl: template>

<xsl: template match = "content">

<xsl: if test = ".! = ''">

<table width = "533" style = "background-color: # edf5fc; border-top: 3pt solid # 5277c2">

<tr valign = "top">

<td>

<div class = "WslMenuLevel0Content">

<xsl: if test = "/ page / embededImage! = ''">

<img>

<xsl: attribute name = "src">

<xsl: value-of select = "/ page / embededImage" />

</ xsl: attribute>

<xsl: attribute name = "border"> 0 </ xsl: attribute>

<xsl: if test = "/ page / embededImageAlign = '0'">

<xsl: attribute name = "align"> left </ xsl: attribute>

</ xsl: if>

<xsl: if test = "/ page / embededImageAlign = '1'">

<xsl: attribute name = "align"> right </ xsl: attribute>

</ xsl: if>

</ img>

</ xsl: if>

<xsl: value-of disable-output-escaping = "yes" select = "." />

</ div>

</ td>

</ tr>

</ table>

</ xsl: if>

</ xsl: template>

<xsl: template match = "extService [extServiceId = '100' and subInfo = '0']">

<xsl: if test = "serviceURL! = ''">

<iframe width = "100%" height = "110" frameborder = "0" scrolling = "no">

<xsl: attribute name = "src">

<xsl: value-of select = "serviceURL" />

& view = firstPage

</ xsl: attribute>

</ iframe>

</ xsl: if>

</ xsl: template>

<xsl: template match = "extService [extServiceId = '100' and subInfo = '1']">

<xsl: if test = "serviceURL! = ''">

<iframe width = "100%" height = "110" frameborder = "0" scrolling = "no">

<xsl: attribute name = "src">

<xsl: value-of select = "serviceURL" />

& view = firstPage

</ xsl: attribute>

</ iframe>

</ xsl: if>

</ xsl: template>

<xsl: template match = "extService" />

</ xsl: stylesheet>

As described above, although the present invention has been described by way of limited embodiments and drawings, the present invention is not limited thereto and is intended by those skilled in the art to which the present invention pertains. Of course, various modifications and variations are possible within the scope of equivalents of the claims to be described.

According to the present invention, it is possible to solve the above-described problems to easily produce a sub-homepage in the same style between homepages. In particular, the user can build a home page by customizing the original files provided in a group according to a menu used on the home page. In addition, in the case of editing the home page, only the relevant part can be easily edited without having to call up and edit all the web pages unnecessarily.

The following drawings attached to this specification are illustrative of preferred embodiments of the present invention, and together with the detailed description of the invention to serve to further understand the technical spirit of the present invention, the present invention is a matter described in such drawings It should not be construed as limited to

1 is a block diagram showing a computer system for implementing the present invention.

2 is a flowchart illustrating the overall flow of the present invention.

3 is a flowchart illustrating a process of selecting an original file of a web page to be used by a user in a homepage.

4 is a diagram illustrating a user interface used in the process of FIG. 3, FIG. 4A is a user interface for selecting a category of a homepage, a user interface for inputting basic information to be used in the homepage of FIG. 4B, and FIG. 4C is a homepage. 5D illustrates a user interface for selecting a menu to be used in the homepage.

5 is a flowchart illustrating a process of generating a link between web pages used in a home page.

6 is a user interface used by a user to edit the structure of a menu.

7 is a flowchart illustrating a process of creating a body used in menu-specific web pages.

FIG. 8 illustrates a user interface used to create a body, and FIG. 8A illustrates a user interface used to create a body of a web page corresponding to one depth of a menu, and FIG. 8B illustrates a web corresponding to two depths of a menu. User interface used to create the body of the page.

* Brief description of the major symbols in the drawings *

10: web server 11: homepage production module 12: file storage

13: Database 14: Web Account

Claims (9)

A web server; A homepage production module mounted on the web server; A database for storing selection information received from the user for generating a home page according to a user's request; The homepage web is stored using a file repository constructed to link the homepage original file (hereinafter referred to as an “original file”) for each menu according to the main page layout of the homepage and the style category of the homepage. About how to make (A) receiving a homepage account request from a user and registering the user's web account with the web server by the module; (b) The user may select style category selection information of the home page, the source file included in the selected style category, and selection information for specifying the source file according to the menu used for the home page and the text layout of the web page for each menu. Receiving from the home page basic information storage unit of the database; (c) Receives the text contents to be stored in the web page for each menu from the user and stores it in the text storage section for each page of the database, and generates the text file in a format that can be dynamically referenced by the original file. Recording on; And, (d) parsing the home page original file for each menu, including the body contents contained in the body file, and storing the home page as a web page in the user's web account. The method of claim 1, The database further includes a menu structure storage unit that stores menu information such as menu name, URL, depth, and the like. Constructing a user-specific menu structure storage unit by alternatively extracting menu information from the menu structure storage unit according to the menu selected in step (b); And, Defining a moving path between web pages by referring to the menu structure storage unit, generating a URL file in a format that can be referred to by the generated web page, and storing the URL file in the web account; Way. The method of claim 1, After performing step (b), referring to the homepage basic information storage unit, parsing the original file selected by the user and storing it as a web page in the user's web account. The web page of step (d) is a home page production method characterized in that the stored as the new web page. The method according to any one of claims 1 to 3, The file store further contains an image file, And receiving the selection information of the image file in step (c) and including the selected image file in the web account. The method of claim 1, The home page original file is generated according to a web style guide for maintaining a web style between a main homepage and a sub homepage. The method of claim 1, The original file is a file produced in an extensible style language (XSL) language, and the body file is a file produced in an extensible markup language (XML) language. Of a device for making a homepage on the web, A web server equipped with a production module for processing an HTTP request and producing a homepage online; A file store for storing information about a layout of a web page, and storing an original file containing location information of contents constituting the web page; And It is configured to include; database for storing a variety of information required to produce a homepage, The database, A user information storage unit for storing identification information such as an ID and a password to issue a web account to the user with the identification information; And, And a homepage basic information storage unit for storing homepage category selection information, basic information, style selection information, and menu selection information used in the homepage, thereby allowing a user to create a customized homepage. The module, Receive the homepage account application from the user and register the user's web account on the web server, The database by receiving the style category selection information of the home page and the source file included in the selected style category, and the selection information specifying the source file according to the menu used for the home page and the body layout of the web page for each menu. In the basic information storage of the homepage, Receives the body content to be stored in the web page of each menu from the user and stored in the body storage unit for each page of the database, Generate the body contents into a body file in a format that the original file can dynamically refer to, and write the contents to the file repository; For each menu, parsing the home page original file to include the body content contained in the body file, and storing the web page in a user's web account as a web page. The method of claim 7, wherein The database further includes a menu structure storage unit for storing menu information such as a menu name, a URL, and a depth, The module may alternatively extract menu information from the menu structure storage unit according to a menu selected by the user, further construct a user-specific menu structure storage unit in the database, and refer to the user-specific menu structure storage unit to link between web pages. And a URL file in a format that can be referred to by a web page and stored in the web account. The method of claim 7, wherein The file store further contains an image file, The module is characterized in that for receiving the selection information recorded by the user of the image file, and the image file selected according to the selection information to the web account.