KR20130040057A - System and method for producing homepage in saas environment, a computer-readable storage medium therefor - Google Patents

Abstract

PURPOSE: A homepage manufacturing system in an SaaS environment, a method thereof, and a computer-readable recoding medium including a computer program for executing the method in a computer are provided to implement WYSISYG type editing in a web browser for homepage manufacture and version change by performing widget type editing and design change. CONSTITUTION: Selectable domains are displayed on an expression layer(230). A homepage management server(222) changes and manages a homepage manufactured in a homepage construction server(221) according to the selection of a user. A core engine(223) processes data and commands used for processing various applications. An open-source frame network(224) provides an application framework based on an open source. A J2EE-based application server(225) processes and manages transactions and interlinks applications of different systems. A persistence layer(210) manages relational data. [Reference numerals] (211) File system; (212a) Design related information; (212b) Site related information; (212c) Widget related information; (221) Homepage construction server; (221a) Homepage planning module; (221b) Homepage design module; (221c) Homepage distribution module; (222) Homepage management server; (223) Core engine; (224) Open-source framework; (225) J2EE-based application server; (AA) Domain 1; (BB) Domain 2; (CC) Domain N; (DD) Operating a homepage; (EE) Widget HTML&CSS; (FF) Design theme CSS; (GG) Site page HTML;

Description

System and method for producing homepage in SaaS environment, a computer-readable recording medium having recorded thereon a computer program for executing the method on a computer, A computer-readable storage medium therefor}

The present invention relates to a system and method for producing a home page in a SaaS environment, and to a computer readable recording medium having recorded thereon a computer program for executing the method on a computer. Homepage production system and method in SaaS environment that provides information in Wizwig format and manages the resources and data belonging to the site by version to enable real-time conversion to various versions of the operation site. A computer readable recording medium having a computer program recorded thereon.

Recently, due to the development of the computer industry and communication industry and the spread of the Internet dedicated line, the number of homepages of companies and individuals is increasing exponentially. A homepage or webpage is a file produced in HTML (Hyper Text Markup Language) and is a generic term for image media stored in a server and displayed through a web browser.

A typical homepage consists of a design part consisting of a page name, menu, graphic or flash, and a program part for implementing various functions such as a member login, a bulletin board, a product search, a shopping cart, and the like. When design coding is sent to a programmer, the programmer must program the design coding to produce a homepage.

As a result, a large portion of the expenses (payments) paid to professionals such as web designers and web programmers involved in homepage production are significant. In addition, the frequent movement of professional personnel such as web designers and web programmers is causing a big obstacle to the sales and profit generation of agencies. This is a great burden for users who have requested the agency to produce a homepage.

Therefore, in the related art, in order to enable a user to easily create a home page, a portal service company such as Hihome, Freechal, Me2u2, Daum, Naver, etc. provides a homepage production / management wizard function for homepage production / management.

Nevertheless, the user needs to prepare various contents, images, contents, etc. for homepage production and management, and manage the user directly or through a web hosting company. There is a problem that additional costs are required because a lot of information is stored and managed in the hosting company's account.

As such, the homepage is not easy to be produced by ordinary Internet users without expertise or experience in homepage production. Therefore, the homepage is produced by a company specializing in homepage production.

At this time, the production cost of the homepage is determined by the components of the homepage, and the cost of manpower, time, content usage fee, etc. required for basic construction work is not small, and even a simple IR site is selected, vendor-specific communication, review, and testing. Procedural time is spent.

Because of this cost and time, even if you want to open a homepage for a private business or a small business place, it may be a burden for this reason, and even after the homepage is opened, registration of contents provided by Internet users when they visit the homepage There is a problem that is difficult to proceed with the continuous update.

Accordingly, an object of the present invention is to create a home page in a SaaS environment that enables not only widget-based site page editing and design change but also real-time conversion to various versions of an operation site by managing resources and data per site. And a computer readable recording medium having recorded thereon a computer program for executing the method on a computer.

Homepage production system in a SaaS environment according to an embodiment of the present invention for achieving the above object of the present invention, in the homepage production system that provides a homepage production service in conjunction with a user terminal device over a network, the user Providing the tools, various files and information necessary for the homepage production according to the request of the user, managing at least one or more websites created by the user by version, and applying the website of the version according to the user's selection It is characterized by consisting of a homepage production server operated by.

At this time, the homepage production server exchanges data by interworking with the data storage layer and a data storage layer managing relational data generated, modified, deleted, selected, and retrieved by a user when the homepage is produced. And a service layer for processing business logic related to the homepage production, a presentation layer for displaying user selectable domains, and a presentation layer for inputting additional information required for a user request. Characterized in that made.

Here, the data storage layer includes a file system for maintaining and managing widgets, design themes, respective style sheets and HTML of site pages, and a database management system for storing design related information and site related information. Characterized in that made.

The service layer is used for homepage construction server in charge of homepage planning, design, and distribution, a homepage operation server for operating a homepage produced by the homepage construction server, and processing various applications required for the homepage production and operation. A core engine that processes commands and data, an open-source framework that provides an open source-based application framework, transaction processing and management, and application integration between other heterogeneous systems. Characterized in that it comprises at least one of the application server.

At this time, the homepage building server, a homepage planning module responsible for at least one of project creation, page addition, master layout setting, page editing, project copy generation, which is a unit of work for generating the website, design theme application, theme style And a homepage design module for at least one of editing and widget style editing, and a homepage distribution module for at least one of the project distribution and the project change.

In addition, the homepage planning module may provide at least one function of adding, deleting, resizing, or aligning a widget constituting a site page when editing a page, and defining an interaction for event processing of the widget.

In addition, the homepage planning module is characterized in that when the copy of the project is generated, copying the project for at least one version of the site configuration and design application to one project.

On the other hand, the homepage distribution module is characterized by generating a static file of the entire site page with the static and dynamic data of the project worked through the homepage planning module and the homepage design module.

The homepage planning module provides at least a project ID and a snapshot number when generating the project, a page number when generating the site page, a layout ID when applying a layout to the site page, and the site page. It is characterized in that for executing at least one of the function of giving a widget ID to the widget constituting the.

At this time, the snapshot number is a unit for distinguishing a design copy, and is characterized in that a new snapshot number is generated when a design copy is generated after the project is initially assigned.

And, the homepage planning module, when generating a copy of the project, characterized in that the information is stored according to the site page addition or editing in the current snapshot number of the project.

The homepage design module may be configured to assign a snapshot number and a theme ID to each design theme when the design theme is applied to the project.

On the other hand, the homepage operation server is characterized in that the database and the data sharing the resource file generated by the homepage building server.

The homepage operation server finds a static file of a site page generated by the homepage distribution module based on the project ID and the snapshot number and services the webpage through a web server.

The homepage production method in a SaaS environment according to another embodiment of the present invention for achieving the above object of the present invention, the homepage production server provides a homepage production service to a user terminal device through a network network In the method, a project, which is a unit of work for creating a website, is created, and at least one of adding a page, setting a master layout, and editing a page is performed, and at least one version-specific website is configured in the project. And a homepage planning step of generating a copy of the project for design application, a homepage design step of applying a design theme to the site page planned in the homepage planning step, and a static of a project produced through the homepage planning step and the homepage design step. And have dynamic data full Create static pages and files on the site, based on a project the user is applied to the selected version of the website operation services characterized by the deployment phase consisting of a website to distribute the homepage.

In this case, the method may further include a homepage operating step of searching for a static file of a site page generated in the homepage distribution step and serving the webpage through a web server.

The homepage planning step may include assigning a project ID and a snapshot number when the project is generated.

In addition, the homepage distribution step is characterized by changing the snapshot number of the project to which the homepage operating service is applied when changing to another version according to user selection.

Meanwhile, in the homepage planning step, at least one of adding, deleting, resizing, and aligning a widget constituting a site page is possible when editing a page, and defining an interaction for event processing of the widget.

According to another aspect of the present invention, there is provided a computer-readable recording medium recording a program for executing each step of the method for producing a home page in the SaaS environment.

According to the computer-readable recording medium in which the homepage production system and method in the SaaS environment and the computer program for executing the method are recorded, the WYSISYG is created in the web browser when the homepage is produced and the version is changed. By editing the widget method and changing the design so that the format can be edited, users who do not have expertise in homepage production can create their own homepage very simply and easily without the support of designers or programmers. .

In addition, the present invention manages all the resources and data belonging to the site by version by creating a copy of the project by creating and distributing several versions of the website in advance, the user can change the version immediately in real time, real-time homepage building and The version change time is shortened and the homepage development manpower is reduced, and the cost can be reduced, and any site version can be selected and the preview can be the same as the actual homepage operation screen.

As a result, the present invention allows the user to easily create and change the homepage without the help of professional personnel such as web designers or web programmers who are involved in the homepage production, and can easily switch to various versions of the operation site for easy accessibility. In addition, it has the effect of activating the homepage through inducing visitors.

1 is a view showing the overall configuration of a homepage production system in a SaaS environment according to an embodiment of the present invention,
2 is a block diagram showing a detailed configuration of a homepage production server according to an embodiment of the present invention;
3 is an exemplary view showing a page edit screen displayed during the homepage planning process according to an embodiment of the present invention;
4 is a diagram showing a data structure of a homepage planning module according to an embodiment of the present invention;
5 is a diagram showing a data structure of a homepage design module according to an embodiment of the present invention;
6 is a diagram showing a data structure of a homepage distribution module according to an embodiment of the present invention;
7 is a block diagram showing the configuration of a homepage production server according to an embodiment of the present invention;
8 is a flowchart illustrating a method of manufacturing a homepage in a SaaS environment according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

The present invention can be embodied as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and are also implemented in the form of a carrier wave (for example, transmission over the Internet). It also includes. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Referring to FIG. 1, a homepage production system in a SaaS environment according to an embodiment of the present invention may include at least one terminal device 100 capable of communicating through a network and a tool necessary for producing the homepage according to a user's request. Or providing various files and information to the terminal device 100, managing at least one or more websites created by the user by version, and operating the website of the corresponding version according to user selection. It consists of a homepage production server 200.

In this case, the terminal device 100 refers to a terminal of an individual or a company that has subscribed to the homepage production server 200 as a member in order to create and manage a homepage. A PC is generally used, but also through a network including the Internet. Any device capable of transmitting and receiving data may be applied to any device.

The terminal device 100 includes a desktop computer, a notebook PC, a smartphone, a tablet PC, and at least one or more portable terminals that can be carried and moved.

Meanwhile, the homepage production server 200 may include a data storage layer 210 that manages relational data generated, modified, deleted, selected, and retrieved by a user when the homepage is produced, and the data storage layer ( A service layer 220 for exchanging data by interworking with each other and processing business logic related to the homepage production, domains that can be selected by a user is displayed, and additional information required for user request is displayed. It consists of a presentation layer (230) for inputting.

In this case, the data storage layer 210 may include a file system 211 for maintaining and managing HTML and style sheets (CSS, cascading style sheets) of widgets, CSS for design themes, and HTML of site pages. And a database management system (DBMS) 212 that stores design related information and site related information of the home page.

In particular, the DBMS 212 includes a design related information DB 212a, a site related information DB 212b, a widget related information DB 212c, and a DB related to homepage production.

In addition, the service layer 220 is operated by changing the homepage building server 221 in charge of the homepage planning, design, distribution and the homepage produced by the homepage building server 221 by version according to the user's selection Homepage operation server 222, a core engine 223 for processing instructions and data used for processing various applications required for the homepage production and operation, and open source providing an application framework based on open source. It is composed of an open-source framework 224 and a J2EE-based application server 225 that is responsible for transaction processing and management, and application interworking between other heterogeneous systems.

Java is a kind of programming language. It is an object-oriented program that runs through a virtual machine called JVM. It is divided into J2SE, J2EE, and J2ME depending on the purpose.

In particular, the homepage building server 221 is a homepage planning module 221a responsible for project generation, page addition, master layout setting, page editing, and project copy generation, which is a work unit for generating the website, and design theme application. , Homepage design module 221b for theme style editing and widget style editing, and homepage distribution module 221c for project distribution and project change.

At this time, the homepage planning module 221a generates a sitemap when the page add function is executed, and creates and deletes a page belonging to the sitemap. When the master layout setting function is executed, a master layout applied to a site page is selected, and a default is applied to all site pages. If necessary, the layout of a specific page can be changed.

In addition, the homepage planning module 221a may add, delete, resize, or arrange widgets constituting a site page when editing a page, and define an interaction for event processing of the widget.

Here, the widget is a minimum unit constituting a site page, and should be developed according to a predefined extension rule as shown in Table 1.

Widget definition XML Define widget name, ID, description, etc. in XML, and create widget by reading information of widget definition XML when administrator adds widget Widget View File Widget view handlers or resource files (HTML, CSS, images, JavaScript, etc.) visible on the page Widget function program
Widget's business logic processing program

Table 2 shows the general structure of the widget directory, and Table 3 shows the widget types.

Directory structure Explanation / component / widget / {widgetID} / admin Widget Settings Manager Screen info Widget definition XML location lang Widget View multilingual file location skins Jet View CSS, image file location Of Program file location
You can create it according to your business structure

Widget type Explanation Widget example Generic widget Located in some area of the page screen,
Does not have a separate subpage Login, logo, post extraction, etc. Big Widget Located in the main area of the page,
May have subpages for logic processing Bulletin boards, site schedules, online voting, etc. Element widget Widget HTML elements INPUT, IMAGE, SELECT, etc.

These widgets are generated by an administrator according to a predefined extension rule, and the widgets thus generated are registered on the administrator screen. In this case, the widget definition XML data may be added to the widget related information DB 212c and the widget configuration file may be copied to a corresponding location of the server.

As illustrated in FIG. 3, the homepage planning module 221a may perform operations such as adding, deleting, resizing, repositioning, and aligning a widget in a page edit screen.

Meanwhile, the homepage planning module 221a copies a project for creating various versions of a site and applying a design to one project when a project copy is generated, and a snapshot number which is a unit for distinguishing a design copy when creating a project. Is initially assigned, and a new snapshot number is created when creating a copy of the design.

At this time, the design-related information DB 212a of the DBMS 212 stores information according to site page addition and editing in the current snapshot number of the project.

The homepage planning module 221a does not need to generate a project copy when using a single project version.

As such, the homepage planning module 221a can not only generate a copy of the project but also manage all resources and data belonging to a site by version so that various versions of the site can be directly converted to the homepage operation server 222 in real time. do.

Meanwhile, the homepage design module 221b applies a design theme to a planned site page, and manages and applies color, font, and background-style as basic design elements of the design theme.

In addition, the homepage design module 221b allows a user to change the default theme style applied to the site page when the theme style is edited, and similarly, when the user edits the widget style, Make it editable.

The homepage distribution module 221c includes all static and dynamic data of a project worked through the homepage planning module 221a and the homepage design module 221b, that is, information stored in a design related information DB 212a and a widget related information DB. Take the widget HTML and CSS and design theme CSS stored at 212c to generate static HTML and CSS of the entire site page.

In this case, in order to reflect the project to the homepage operation server 222, a static file must be generated through a publish process. The directory structure for generating the static file is as follows.

"/ sites / project ID / snapshot number / page number / HTML & CSS"

In addition, when the user requests to change the project applied to the homepage operation server 222 to another version, the homepage distribution module 221c changes only the snapshot number of the corresponding project in the site related information DB 212b.

Then, the homepage operation server 222 finds a static file of the site page generated by the homepage distribution module 221c based on the project ID and the snapshot number stored in the site related information DB 212b and the web server 310. Provides homepage operation service through

As such, referring to the data structure shown in FIGS. 4 to 6, the homepage planning module 221a, the homepage design module 221b, and the homepage distribution module 221c relate to the corresponding process as each process is executed. The processed data and reference data are processed in conjunction with the file system 211 and the DBMS 212.

On the other hand, the homepage production server 200 from the perspective of server implementation, as shown in Figure 7, the web server 310, WAS (Web Application Server) server 320, DB server 330, The web server 310 includes an Apache server 311, a file server, and a mail server, which are software for displaying various static contents on a web browser.

The Apache server 311 is an 'A Patch Server' and is known to have high performance and stability based on free software.

In addition, the WAS server 320 is composed of a Tomcat cluster. Tomcat is software used to process dynamic content such as Servlets, JSPs, and Java. In a general development environment, the Tomcat server 321 is used alone. Although used, the web site is mostly operated in conjunction with the Apache server 311.

In addition, the DB server 330 is composed of a MySQL cluster, which is an open source relational database management system (DBMS) that manages the storage and deletion of data through SQL, a query language. to be.

The MySQL cluster integrates a storage engine 332 called NDB into a general MySQL server 331 to access a computer and data including a MySQL server 331, a data node 333, and a management server 334. It consists of an application program.

Thus, when data is stored in the NDB storage engine 332, tables are stored in the data node 333, and each table is directly accessible from the MySQL server 331. So if you update some information in a MySQL cluster, it can be immediately checked on all other MySQL servers 331, the data stored in the data nodes 333 of the MySQL cluster can be mirrored, and the MySQL cluster will be able to mirror the status of each node, including aborting transactions. Handling is possible.

As such, the homepage production server 200 may be configured as a web server 310, a WAS server 320, and a DB server 330, and may be a web server, a WAS server, and a DB server operated independently through a network. In this case, an independent web server operates a website for providing a user interface to the terminal device 100.

In addition, although the homepage building server 221, the homepage operating server 222, and the application server 225 are each shown as separate servers, this is to more effectively understand the present invention. It may be integrated into at least one server.

Hereinafter, the operation of the homepage production system in the SaaS environment according to an embodiment of the present invention will be described in more detail with reference to the accompanying drawings.

8 is a flowchart illustrating a method of manufacturing a homepage in a SaaS environment according to an embodiment of the present invention.

Referring to FIG. 8, in the SaaS environment according to an exemplary embodiment of the present invention, the homepage production method may include generating a project, which is a work unit for creating a website, in the homepage planning module 221a, and generating a project ID and a snapshot in the project. Give a number (S1).

The homepage planning module 221a adds a site page to generate a site map and selects a master layout applied to the site page. The page layout is assigned to the site page and the layout ID is also assigned to the layout. (S2 and S3)

When a user requests editing of a page, widgets constituting the site page are added, deleted, resized, and aligned, and a widget ID is assigned to the site page widget (S4 and S5).

In addition, the homepage planning module 221a does not need to generate a copy of the project when only one project version is used, but generates a copy of the project when various versions of the site configuration and design are applied to a single project. (S6 and S7)

At this time, the unit for dividing the design copy is the snapshot number, and the information of site page addition and editing is saved in the current snapshot number of the project.

On the other hand, the homepage design module 221b applies a design theme to the project and gives the theme ID (S8). When the user performs theme style editing, the user refers to the design theme CSS as the default theme style applied to the site page. To change the color, font, background style, etc. (S9 and S10).

In addition, when the user performs widget style editing, the widget ID is read from the DBMS 212, and the widget style CSS is edited in the file system 211 to edit the basic style of the widget constituting the site page. (S11 and S12)

The homepage distribution module 221c performs a distribution process by generating a static file of all site pages with all the static and dynamic data of the project produced by the homepage planning module 221a and the homepage design module 221b. S13)

The homepage distribution module 221c is changed to another version in real time by changing only the snapshot number of the corresponding project when the user wants to change the project applied to the operation site by the homepage operation server 222. (S14 and S15)

Accordingly, the homepage operation server 222 finds a static file of the site page generated by the homepage distribution module 221c based on the project ID and the snapshot number stored in the site-related information DB 212b and the web server 310. The homepage will be operated through.

As such, the present invention enables a user who does not have professional knowledge related to homepage production without the support of a designer or a programmer to independently make a homepage by allowing the user to edit the WYSISYG format in a web browser when the homepage is produced and the version is changed. Make it very simple and easy to build.

In addition, the present invention is to create and distribute several versions of the website in advance by creating a copy of the project, the user can change the version immediately in real time when the user wants to shorten the time to change the homepage and version development and to reduce the website development personnel The cost can be reduced.

It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. It will be possible.

The present invention relates to a system and method for producing a homepage in a SaaS environment, and to a computer readable recording medium having recorded thereon a computer program for executing the method on a computer. In order to make this possible, we provide tools, various files and information necessary for homepage production in Wizwig format, and manage homepage resources and data per version so that real-time conversion to various versions of the operation site is possible. A system and method, and a computer readable recording medium having recorded thereon a computer program for executing the method on a computer.

100: terminal device 200: homepage production server
210: data storage layer 220: service layer
230: presentation layer 211: file system
212: DBMS 221: homepage building server
221a: homepage planning module 221b: homepage design module
221c: homepage distribution module 222: homepage operation server
223: Core Engine 224: Open Source Framework
225: application server 310: web server
320: WAS server 330: DB server

Claims (20)

In the homepage production system providing a homepage production service in conjunction with a user terminal device through a network,
Providing the tools, various files and information necessary for the homepage production according to the user's request, managing at least one website created by the user by version, and managing the website of the version according to the user's selection Homepage production system in the SaaS environment, characterized in that consisting of the homepage production server operating by applying. The method of claim 1,
The homepage production server,
A data storage layer for managing relational data generated, modified, deleted, selected, and retrieved by a user during the homepage production;
A service layer which interacts with the data storage layer to exchange data and processes business logic related to the homepage production;
A homepage production system in a SaaS environment, characterized in that domains that can be selected by a user are displayed and a presentation layer for inputting additional information required for a user request is included. The method of claim 2,
The data storage layer,
A file system that maintains and manages the widgets, design themes, style sheets and HTML for site pages,
Homepage production system in a SaaS environment comprising a database management system for storing design-related information and site-related information. The method of claim 2,
The service layer is
Homepage building server in charge of the homepage planning, design, distribution,
Homepage operation server for operating the homepage produced by the homepage building server,
A core engine for processing instructions and data used for processing various applications required for the homepage production and operation;
An open-source framework that provides an open source-based application framework,
Website processing system in a SaaS environment, characterized in that the transaction processing and management, including at least one of the application server responsible for the application interworking between different systems. 5. The method of claim 4,
The homepage building server,
A homepage planning module in charge of at least one of a project generation, a page addition, a master layout setting, a page editing, a copy of a project, which is a unit of work for generating the website;
A homepage design module responsible for applying at least one of design theme, theme style editing, widget style editing,
Homepage production system in a SaaS environment, characterized in that it comprises a homepage distribution module responsible for at least one of the project distribution and project changes. The method of claim 5,
The homepage planning module provides at least one function of adding, deleting, resizing, and arranging widgets constituting a site page when editing a page, and defines an interaction for event processing of widgets in a SaaS environment. Homepage production system. The method of claim 5,
The homepage planning module is a homepage production system in a SaaS environment, characterized in that the copying process of the project for the application of at least one or more versions of the site configuration and design to a project when creating a copy of the project. The method of claim 5,
The homepage distribution module is a homepage production system in a SaaS environment, characterized in that to generate a static file of the entire site page with the static and dynamic data of the project worked through the homepage planning module and the homepage design module. The method of claim 5,
The homepage planning module,
At least give a project ID and a snapshot number when creating the project,
Give a page number when creating the site page,
Assign layout ID when applying layout to the site page,
And at least one of a function of assigning a widget ID to a widget constituting the site page. 10. The method of claim 9,
The snapshot number is a unit for distinguishing a copy of a design, and a homepage production system in a SaaS environment, wherein a new snapshot number is generated when a copy of a design is generated after being first given when the project is created. The method of claim 10,
The homepage planning module is a homepage production system in the SaaS environment, characterized in that the information stored according to the addition or editing of the site page in the current snapshot number of the project when creating a copy of the project. The method of claim 5,
The homepage design module,
When the design theme is applied to the project, the homepage production system in the SaaS environment, characterized in that the number of the theme and the theme ID assigned to each design theme. 5. The method of claim 4,
The homepage operation server is a homepage production system in a SaaS environment, characterized in that sharing the resource file and the database data generated by the homepage building server. The method according to any one of claims 9 to 13,
The homepage operation server finds a static file of a site page generated by the homepage distribution module based on the project ID and a snapshot number, and services the homepage in a SaaS environment. In the homepage production method for providing a homepage production service to a user terminal device through a network in the homepage production server,
Create a project, which is a unit of work for creating a website, and perform at least one function of adding a page, setting a master layout, and editing a page, and applying a website configuration and design application by at least one version to the project. To create a copy of the project
A homepage design step of applying a design theme to a site page planned in the homepage planning step,
Homepage distribution that generates static files of all site pages with static and dynamic data of the project produced through the homepage planning step and homepage design step, and distributes the homepage based on the project to which the user selects the homepage operation service. Homepage production method in a SaaS environment, characterized in that consisting of steps. 16. The method of claim 15,
A homepage production method in a SaaS environment, characterized by further comprising a homepage operation step of finding a static file of a site page generated in the homepage distribution step and serving it through a web server. 16. The method of claim 15,
The homepage planning step is to create a homepage in the SaaS environment, characterized in that the project ID and snapshot number assigned to the project generation. The method of claim 17, wherein
The homepage distribution step is a homepage production method in a SaaS environment, characterized in that for changing to a different version in accordance with the user selection to change the snapshot number of the project to which the homepage operating service is applied. 16. The method of claim 15,
In the homepage planning step, when editing a page, at least one of adding, deleting, resizing, and arranging a widget constituting a site page is possible, and creating a homepage in a SaaS environment, characterized in that an interaction for event processing of a widget is defined. Way. A computer-readable recording medium having recorded thereon a computer program for executing a method of producing a home page in a SaaS environment according to any one of claims 15 to 19 on a computer.

Images