CMS server device and CMS server program

Abstract

To improve the efficiency of website operation and management. [Solution] The CMS server device according to the present invention includes a space setting means that sets a space which is a unit for managing a website, and sets one of the set spaces as a parent space and the spaces other than the parent space as child spaces to establish a parent-child relationship, a model creation means that creates a model that defines the content elements of a web page in the set parent space, and a model inheritance means that causes the model created in the parent space to be inherited as a model created in the child space.

Description

Technical Field

[0001] The present invention relates to a CMS server device and a CMS server program.

Background Art

[0002] Conventionally, a CMS (Content Management System) for constructing, managing, and operating websites is known. A typical CMS is provided with a user interface for directly editing content (hereinafter referred to as editing UI), and even if editors in respective management departments do not have sufficient specialized knowledge, they can edit (update, add, etc.) web pages without going through web designers or engineers, which enables efficient website operation under a division-of-labor system. In particular, since editors add and update web pages based on templates (design templates) designed by web designers, large deviations from the design and user interface intended by the web designer for each page rarely occur.

[0003] In a CMS, first, an engineer (developer) extracts a page layout configuration based on a page design comp (completed design sample) created by a web designer, and develops a modeled page layout model (content modeling) to facilitate management and editing in the CMS. More specifically, in the page layout configuration for one template, content elements such as title, subtitle, description, related links, main visual, body text, etc. are extracted, and editors directly edit the extracted content elements via the editing UI. Editors edit (update, add, etc.) the content elements that have been content-modeled along the editing UI, whereby web content that conforms to the design and user interface intended by the web designer is created (Figure 1).

[0004] In recent years, a type of CMS called a headless CMS, which lacks a head or front-end (viewer), has also emerged (see, for example, Patent Document 1). A headless CMS is a system specialized in the management, editing, and distribution of content data, and displays websites by linking with a separately built front-end via an API. While headless CMSs are technically more difficult to implement than conventional CMSs, they excel in versatility, security, and design flexibility. Because the front-end and back-end are completely separated, system changes can be made without affecting each other, CMS functions can be added later, and there are advantages such as faster page display and reduced server load. Headless CMSs are also suitable for distributing data to various multi-channels with different front-ends, such as apps, smart devices, and digital signage, in addition to websites. [Prior art documents] [Patent Documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2024-178099 [Overview of the project] [Problems that the invention aims to solve]

[0006] In this context, even a single corporate entity often operates and manages multiple websites depending on its business type. A clear example is the food and beverage industry, where the same corporate entity operates different store brands across various genres. In such cases, the corporate entity needs to operate and manage multiple different websites simultaneously or collectively.

[0007] However, managing and operating multiple different websites requires multi-layered management (horizontal deployment), and maintaining the consistency and uniformity of the design and content intended by the web designer across all sites, as mentioned above, is not always easy.

[0008] This invention was proposed in view of the above points, and aims to improve the efficiency of website operation and management from one perspective. [Means for solving the problem]

[0009] To solve the above problems, the CMS server device according to the present invention is a CMS server device for managing a website, and includes a space setting means for setting spaces which are units for managing a website, and for relating a parent-child relationship in which one of the set spaces is designated as a parent space and the spaces other than the parent space are designated as child spaces, a model creation means for creating a model that defines the content elements of a web page in the set parent space, and a model inheritance means for inheriting the model created in the parent space as a model created in the child space. [Effects of the Invention]

[0010] According to embodiments of the present invention, one aspect is that the efficiency of website operation and management can be improved. [Brief explanation of the drawing]

[0011] [Figure 1] This diagram shows an example of a website creation workflow. [Figure 2] This figure shows an example of the network configuration of the CMS according to this embodiment. [Figure 3] This figure shows an example of the architecture configuration of the CMS according to this embodiment. [Figure 4] This figure shows an example of the hardware configuration of the CMS server according to this embodiment. [Figure 5] This figure shows an example of the software configuration of the CMS server according to this embodiment. [Figure 6] This diagram shows the space configuration according to this embodiment. [Figure 7] This figure shows the model screen below the space according to this embodiment. [Figure 8]This is a diagram showing a model creation screen for the "Top" page according to the present embodiment. [Figure 9] This is a diagram showing a model creation screen for the "Product Information" page according to the present embodiment. [Figure 10] This is a diagram showing a model screen under a space according to the present embodiment. [Figure 11] This is a schematic diagram showing the state of space and model creation according to the present embodiment. [Figure 12] This is a diagram showing space settings according to the present embodiment. [Figure 13] This is a diagram showing a subspace creation screen according to the present embodiment. [Figure 14] This is a diagram showing space settings according to the present embodiment. [Figure 15] This is a diagram showing model inheritance settings to a subspace according to the present embodiment. [Figure 16] This is a schematic diagram showing the state of subspace and model inheritance according to the present embodiment. [Figure 17] This is a diagram showing space settings according to the present embodiment. [Figure 18] This is a schematic diagram showing the state of subspace and model inheritance according to the present embodiment. [Figure 19] This is a diagram showing a content editing screen for the "Top" page in "Subspace_01" according to the present embodiment. [Figure 20] This is a diagram for explaining model inheritance to a subspace according to the present embodiment. [Figure 21] This is a diagram showing content creation and editing of a subspace according to the present embodiment. [Figure 22] This is a diagram showing content reference between a parent space and a subspace according to the present embodiment. [Figure 23] This is a diagram showing content migration between a parent space and a subspace according to the present embodiment. [Figure 24] This is a schematic diagram showing the state of subspace and model inheritance according to the present embodiment. [Figure 25]This figure shows the creation and editing of content in a space according to this embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the present invention will be described in detail with reference to the drawings. [Embodiment 1] <System Configuration> (Network configuration) Figure 2 shows an example of the network configuration of the CMS according to this embodiment. Figure 3 shows an example of the architectural configuration of the CMS according to this embodiment. The CMS (Content Management System) 100 according to this embodiment includes a CMS server 10, a system configuration terminal 20 owned by an engineer (developer) or web designer, and an editor terminal 30 owned by a content editor, and is connected via a network 50.

[0013] The CMS server 10 according to this embodiment is a server device for a SaaS (Software as a Service) type content management system for building, managing, and operating websites. The CMS server 10 performs tasks such as user management, various system settings, web page content generation via an editing UI, content data management such as documents and images, and website management. The front end of the website, built by engineers under the design supervision of a web designer, is made public to website visitors via a web server (not shown).

[0014] Furthermore, the CMS server 10 according to this embodiment is a headless CMS specialized in the management, editing, and distribution of content data, and therefore does not include a front-end on the CMS side. The front-end, which is built separately by engineers under the design supervision of a web designer, and the CMS server 10 cooperate via an API (Application Programming Interface) to display the website to visitors (decoupled architecture).

[0015] The system configuration terminal 20 is an information terminal device used by engineers or web designers to perform various system settings, such as creating parent spaces and subspaces (described later) and website content modeling. The system configuration terminal 20 is implemented as, for example, a tablet device or a personal computer, and has a predetermined application program (for example, a general-purpose web browser or a dedicated app) for accessing the CMS server 10 pre-installed.

[0016] The editor terminal 30 is an information terminal device for editors to create and edit web content. The editor terminal 30 is implemented as, for example, a smartphone, tablet terminal, or personal computer having display means, input means, and operation means, and has a predetermined application program (for example, a general-purpose web browser or a dedicated app) for accessing the CMS server 10 pre-installed.

[0017] As shown in Figure 1, the engineer (developer) first extracts the page layout structure based on the page design comp (final design sample) created by the web designer, and develops a page layout model (content modeling) that is modeled to be easily managed and edited in the CMS. More specifically, the engineer (developer) models content elements such as title, subtitle, description, related links, main visual, body text, etc., in the page layout structure of a single template, and the editor edits these content elements via the editing UI. By inputting content according to the content modeled content elements in accordance with the editing UI, the editor creates web content that meets the design and user interface intended by the web designer.

[0018] Network 50 is a communication network including wired and wireless networks. Network 50 includes, for example, the Internet, public telephone networks, Wi-Fi®, Bluetooth®, etc.

[0019] (Hardware configuration) Figure 4 shows an example of the hardware configuration of the CMS server according to this embodiment. The CMS server 10 includes a CPU (Central Processing Unit) 11, ROM (Read Only Memory) 12, RAM (Random Access Memory) 13, storage device 14, and communication device 15.

[0020] The CPU 11 executes various programs and performs calculations. The ROM 12 stores programs necessary for startup. The RAM 13 is a work area that temporarily stores processing performed by the CPU 11 and stores data. The storage device 14 stores and saves various data and programs. The communication device 15 communicates with other devices via the network 50.

[0021] (Software configuration) Figure 5 shows an example of the software configuration of the CMS server according to this embodiment. The CMS server 10 has as its main functional units a space setting unit 101, a model creation unit 102, a model inheritance unit 103, an access control unit 104, an editing unit 105, a content management unit 106, and a storage unit 109.

[0022] The space setting unit 101 has the function of setting spaces, which are the units for managing a website, and establishing a parent-child relationship among the set spaces, designating one space as the parent space and the other spaces as child spaces (subspaces).

[0023] The model creation unit 102 has the function of creating a model that defines the content elements of a web page in a set space.

[0024] The model inheritance unit 103 has the function of inheriting a model created in the parent space as a model created in the child space.

[0025] The authorization management unit 104 has a function to grant and manage model creation permissions on a space-by-space basis, as an authorization for whether or not models can be created in a space. In particular, in this embodiment, as will be described later, models can be created in the parent space, but not in the child space. It also has a function to grant and manage content editing permissions on a space-by-space, model-by-model, user-by-user, or user-group basis, as an authorization for whether or not content can be edited.

[0026] Editorial Unit 105 has the functionality to retrieve content elements defined in the model created in the space, generate an editing UI using the content elements as input content, and allow the user to edit the content according to the content elements via the editing UI.

[0027] The content management unit 106 has the function of managing user-edited content independently for each space.

[0028] The memory unit 109 has the function of storing various databases necessary for building, managing, and operating a website as a CMS in the storage device 14, such as a space management DB for managing space information set by the space setting unit 101, a model management DB for managing model information created by the model creation unit 102, and a content management DB for storing and managing content edited by users.

[0029] It goes without saying that these functional units are functional units according to the present invention, and that the CMS server 10 also has various other functional units necessary for building, managing, and operating a website. Furthermore, each functional unit is realized by a program executed on the hardware resources such as the CPU, ROM, and RAM of the computer that constitutes the CMS server 10. These functional units may be read as "means," "modules," "units," or "circuits." In addition, the various DBs of the storage unit 109 in the CMS server 10 can also be placed on an external storage device on the network 50. Furthermore, the above-mentioned computer program and application program may be stored on a storage medium that is readable by the computer.

[0030] The CMS 100 according to this embodiment is a SaaS-type content management system. Therefore, the system configuration terminal 20 and the editor terminal 30 are provided with the functional services of the CMS server 10 via, for example, a general-purpose web browser or a dedicated application. In other words, for example, a web browser receives display data from the CMS server 10, the web browser sends input data and operation data to the CMS server 10, and displays display data as response data on the web browser screen. On the other hand, if the system is configured as a standalone content management system rather than a SaaS-type content management system, the system configuration terminal 20 and the editor terminal 30 can also have the functional units of the CMS server 10.

[0031] <Examples of building individual store websites using parent and sub-space functions> In this embodiment, we assume a case where a single corporate organization operates three store brands in different genres, and we will describe an example of building a website for each store using the subspace function of the CMS server 10.

[0032] (Setting up the parent space and creating the model) Generally, website creation is achieved through a division of labor among various personnel, such as web directors, web designers, engineers, and editors. However, depending on the number of personnel and skills, web directors and web designers, or web designers and engineers, may sometimes share responsibilities.

[0033] First, the web director considers the overall structure and user flow of the website and creates a sitemap. Next, the web designer designs the web pages and creates design comps. In this embodiment, even if the stores are different brands, the goal is to build a website that is easy to operate and manage simultaneously or collectively, while maintaining the consistency and uniformity of the design and content intended by the web designer.

[0034] Figure 6 shows the space configuration according to this embodiment. The engineer uses the system configuration terminal 20 to access the CMS management screen of the CMS server 10, displays the space screen from "Spaces" 200 on the CMS management screen, and first creates space 110 by pressing "Create New" 201. A space is a unit for managing site elements such as content data, media files, models, and field sets. The space name can be set to any name, but here it is named "Parent Space".

[0035] The CMS server 10 stores information about the created space, including the space name, in the space management DB of the storage unit 109.

[0036] Next, the engineers extract and model the content to be managed by the CMS for each web page, based on the page design (design comp) created by the web designer. Then, on the model creation screen, they set the extracted content elements for each web page to create a model of each web page that has been content-modeled based on the page design created by the web designer.

[0037] Figure 7 shows the model screen under the space according to this embodiment. To create a new model in the created space 110, the model screen is displayed from the "Parent Space" 110 and 202 "Model" 202 in the CMS management screen, and the model creation screen is displayed by pressing the "Create Model" 203 button. In this embodiment, for example, models for web pages such as "Top," "News," "Sales Information," and "Product Information" are created.

[0038] Figure 8 shows the model creation screen for the "Top" page according to this embodiment. A model is a template for the content of a web page. It is defined by combining input fields. An engineer can set (define) the web page model by entering the same name as the page, for example, "Top," as the model name 204, selecting input fields (components) of the appropriate type for each content element from the input field list 205, and placing them in the page layout configuration field 206 using drop-and-drag operations, etc. Here, for example, input fields corresponding to content elements such as media, multi-line text, single-line text, content reference, delimiter, etc., are set.

[0039] The CMS server 10 saves the space name, model name, and information from the input fields placed and configured in the page layout configuration field 206 as the model for the "Top" page in the model management DB of the storage unit 109. Once the model for the "Top" page is created, editors can edit the values ​​of each content element on the "Top" page via the editing UI.

[0040] Figure 9 shows the model creation screen for the "Product Information" page according to this embodiment. In the same manner as for the "Top" page, the engineer enters "Product Information" as the model name 204, selects input fields of the appropriate type for each content element from the input field list 205, and places and sets them in the page layout configuration field 206 using drop-and-drag operations, etc. Here, for example, input fields corresponding to content elements such as single-line text, single-line text, multi-line text, content reference, media, flexible text, etc. are set.

[0041] The CMS server 10 saves the space name, model name, and information from the input fields placed and configured in the page layout configuration field 206 as a model for the "product information" page in the model management DB of the storage unit 109. Once the model for the "product information" page is created, editors can edit the values ​​of each content element on the "product information" page via the editing UI.

[0042] Figure 10 shows the model screen under Space according to this embodiment. The model list 209 displays a list of models for each page that have been created. In this embodiment, for example, models for the pages "Top," "News," "Sales Information," and "Product Information" have been created.

[0043] Figure 11 is a schematic diagram showing the space and model creation process according to this embodiment. Compared with Figure 6, Figure 11 shows that models for each page, such as "Top," "News," "Sales Information," and "Product Information," are created within the "Parent Space" 110.

[0044] (Subspace settings and model inheritance) Up to this point, under the main space, a page layout model has been created for the store website, such as "Top," "News," "Business Information," and "Product Information." Next, a subspace will be set up with this space as the parent space.

[0045] Figure 12 shows the space settings according to this embodiment. The engineer displays the space screen again from "Spaces" 200 on the CMS management screen and creates a subspace by clicking "Create Subspace" 222 on the previously created "Parent Space" 110.

[0046] A subspace is a space function that inherits the model definitions and space settings under the parent space and can manage separate content with the same page layout configuration as the parent space. In this embodiment, the store site layout model 111 (a bundle of page layout models for "Top," "News," "Business Information," and "Product Information") created in the "parent space" 110 is considered the layout template for the store brand site and is inherited by the subspace. Therefore, the store site layout models (page layout models for "Top," "News," "Business Information," and "Product Information") within each inherited subspace become the layout models for their respective store brand sites.

[0047] Figure 13 shows the subspace creation screen according to this embodiment. When an engineer creates a subspace, on the subspace creation screen, they confirm the name of the "parent space" from which it is inherited, and then enter, for example, "subspace_01" as the "space name" 225 of the subspace to be created. "Space LUID" 226, "group" 227, and "space icon" 228 are optional. "Space LUID" 226 is a unique identifier for managing the subspace in association with the "parent space" 224 from which it is inherited, and may be automatically issued if not entered by the user. If the subspaces are to be grouped, the same group is set for "group" 227. After entering all the necessary information, the engineer presses the "create" button 229.

[0048] Figure 14 shows the space settings according to this embodiment. Compared to Figure 12 before the creation of the subspace, Figure 14 shows that "subspace_01" 110a has been created as a subspace of "parent space" 110. Note that since the parent space and subspace (child space) have a parent-child relationship, "subspace_01" 110a is positioned under "parent space" 110 and displayed on the screen.

[0049] The CMS server 10 stores information about the created subspace, including the subspace name and parent space name (or unique identifier, etc.), in the space management DB of the storage unit 109.

[0050] Figure 15 shows the model inheritance settings for a subspace according to this embodiment. To inherit a model from a parent space to a subspace created from the parent space, open the target model (e.g., "Top") in the parent space, check "Show this model in subspace" 231, and click "Save" 232. This allows inheritance from the parent space to the subspace for the checked model (e.g., "Top").

[0051] In this embodiment, inheritance from the parent space to the subspace is permitted for all page layout models: "Top," "News," "Sales Information," and "Product Information." It is also possible to uncheck models that should only be displayed in the parent space and check only the models that should be inherited.

[0052] The CMS server 10 stores information such as the subspace name, parent space name, or model name inherited from the parent space in the model management DB of the storage unit 109.

[0053] Figure 16 is a schematic diagram showing the subspace and model inheritance according to this embodiment. Compared to Figure 14 before the model inheritance setting, Figure 16 shows that the layout model 111 of the store site in the "parent space" 110 (the page layout models for "Top," "News," "Business Information," and "Product Information") has been inherited by "subspace_01" 110a. In other words, "subspace_01" 110a was created by inheriting the layout model 111a of the store A site (the page layout models for "Top," "News," "Business Information," and "Product Information"). The contents of the model are the information of the input fields placed and set in the page layout configuration field 206 (Figures 8 and 9).

[0054] Furthermore, regarding the "editing permissions" for content, those of the "parent space" 110 (for example, the head office administrator) are inherited. However, in this embodiment, since the content of store A's site is created and managed by store A, the engineer should change the person with editing permissions for store A from, for example, the head office administrator to a store A staff member after setting up the model inheritance.

[0055] On the other hand, the CMS server 10 (authority management unit 104) according to this embodiment does not grant authority regarding the creation of models under a space to users such as the head office administrator or store A staff, but rather grants authority to the space type. That is, in a subspace, in order to reflect a model that retains the model definition of the parent space as is, that is, in this embodiment, while maintaining the consistency and uniformity of the design and content intended by the web designer, authority to create models is granted to the parent space, but authority to create models is not granted to the subspace. If models were to be created in the subspace, it would become difficult to guarantee consistency and uniformity.

[0056] Furthermore, if permissions regarding model creation are granted on a per-person basis, there is a risk that permission management will become complex for each space. For example, engineers and head office administrators might have permission to create models in the parent space, but permission to not create models in sub-spaces.

[0057] Needless to say, in order to ensure flexibility in the management and operation of layout models for each store site, engineers (administrators) can exceptionally and temporarily change their permissions to allow model creation even under subspaces.

[0058] Figure 17 shows the space settings according to this embodiment. Compared to the subspaces in Figure 14, Figure 17 shows that "Subspace_02" 110b and "Subspace_03" 110c have been created as subspaces of the "Parent Space" 110. Also, in this embodiment, since "Display this model in subspaces" is checked (Figure 15), all models are inherited from the parent space 110 to "Subspace_02" 110b and "Subspace_03" 110c, similar to "Subspace_01" 110a.

[0059] Figure 18 is a schematic diagram showing the subspace and model inheritance according to this embodiment. A "parent space" 110 is set up, and under it are "subspace_01" 110a, "subspace_02" 110b, and "subspace_03" 110c. "subspace_01" 110a, "subspace_02" 110b, and "subspace_03" 110c are spaces allocated for three store brand websites, respectively.

[0060] Furthermore, the layout models 111 for the store website (page layout models for "Top," "News," "Business Information," and "Product Information") created in the "Parent Space" 110 are inherited in the respective subspaces of "Subspace_01" 110a, "Subspace_02" 110b, and "Subspace_0" 110c as layout model 111a for store A, layout model 111b for store B, and layout model 111c for store C, respectively.

[0061] It is also possible to create each of the (parent) space 110, (sub) spaces 110a, (sub) spaces 110b, and (sub) spaces 110c first, and then configure the parent-child relationships between the parent and sub-spaces. For example, you can display the space screen from "Spaces" 200 in the CMS management screen shown in Figure 6, and create spaces 110, 110a, 110b, and 110c from "Create New" 201. After that, you can configure space 110 as the parent space and configure spaces 110a, 110b, and 110c as sub-spaces of space 110.

[0062] (Editing content in subspaces) Editors (for example, staff from store A, store B, and store C) can create web content by editing their respective web pages (inputting, updating, adding, deleting content, etc.) via the editing UI, following the page layout model inherited from the parent space to each subspace.

[0063] Figure 19 shows the content editing screen for the "Top" page in "Subspace_01" according to this embodiment. As an editor, a staff member of Store A accesses the CMS management screen of the CMS server 10 using the editor terminal 30. In the "Subspace_01" space of the CMS management screen, the editor selects the model they want to edit from the inherited models in the model list 311 from "Content" 310, and displays the content editing screen for the selected model. On the content editing screen on the right, the editor edits the content of the "Top" page by uploading media or entering text according to the input field 312 (corresponding to the page layout configuration field 206 in Figure 8). Here, for example, input fields corresponding to content elements such as media, multi-line text, single-line text, content reference, and separators can be edited.

[0064] <Subspace Functions> Next, the functions of the subspace according to this embodiment will be summarized and explained. (1) Model settings (definitions) created in the parent space can be inherited and created in the subspace. Figure 20 illustrates model inheritance to a subspace according to this embodiment. As shown in Figure 20, a subspace according to this embodiment can directly inherit the model created in the parent space (for example, the layout models for the "Top," "News," "Sales Information," and "Product Information" pages). As mentioned above, the model in the parent space is created based on the design and content consistency and uniformity intended by the web designer. Similarly, in the subspace, it is possible to easily create a model that retains the same model definition as the parent space, that is, while maintaining the same design and content consistency and uniformity intended by the web designer.

[0065] Furthermore, considering a case where a single corporate organization operates three or more store brands in different genres, as in this embodiment, it is possible to easily build websites that maintain consistency and uniformity in design and content across all store sites. In addition, by linking and managing the parent space and sub-spaces, the CMS server 10 can simultaneously inherit and reflect any updates, additions, or deletions to the model inherited from the parent space in the sub-spaces.

[0066] (2) Content can be created and edited individually in inherited subspaces. While subspaces inherit the model of their parent space, the content itself can be freely created and edited within each individual subspace.

[0067] Figure 21 shows the content creation and editing process for a subspace according to this embodiment. The subspace shown in Figure 21 inherits the layout models of the "Top," "News," "Business Information," and "Product Information" pages from the parent space. Although the page layout configuration of each page is fixedly defined, the content and media within the page layout (in the input fields) that embody the model can be individually and freely created and edited independently of the parent space via the editing UI, under the editing authority of the store site.

[0068] This makes it easy to build websites that maintain consistency and uniformity in design and content across all store sites, while also having content tailored to each individual store.

[0069] For example, in the case of Japanese, Western, and Chinese restaurant brands, while all store websites may use the same page layout model, it is easy to create websites that feature specific content and media tailored to each restaurant brand, such as "Top," "News," "Business Information," and "Product Information" (Menu).

[0070] Media refers to files uploaded by users, such as images, videos, and PDFs, which are incorporated as part of the content of web pages, blog posts, etc. Furthermore, the parent space model shown in Figure 21 is used as a template. That is, while each space inherits the model from the parent space, the content itself is left to be freely created and edited in each individual subspace; therefore, the parent space content shown in Figure 21 is empty.

[0071] (3) Content and media created between spaces can be referenced. Content and media can be referenced within each other's spaces, both between parent and subspaces, and between subspaces themselves.

[0072] Figure 22 shows a diagram illustrating content referencing between a parent space and a subspace according to this embodiment. The website content "Product Article B3" for store B site shown in Figure 22 is content created by referencing the website content "Product Article A3" and media "Product Image A3" for store A site. In this way, when creating and editing content between spaces, it is possible to reference content and media from other spaces and incorporate them as part of one's own content.

[0073] For example, if store B decides to offer a popular menu item from store A as a new menu item, and publishes it as website content on store B's site, the sub-space store B site can create this by referencing the website content "product article B3" of the other sub-space, specifically "product article A3" (for example, a description of the popular menu item from store A) and media "product image A3" (for example, a photograph of the popular menu item from store A). Furthermore, by linking the source and destination content, the CMS server 10 can simultaneously reflect updates to the destination content when the source content is updated.

[0074] (4) Content and media created between spaces can be transferred. Content and media can be moved (copied) between parent spaces and subspaces, and between subspaces themselves.

[0075] Figure 23 is a diagram illustrating the content migration between the parent space and subspace according to this embodiment. The website content "Announcement Articles All" for Store A Site, Store B Site, and Store C Site shown in Figure 23 is content created by migrating "Announcement Articles All" from the parent space.

[0076] For example, assuming a case where a single corporate organization operates three or more store brands in different genres, as in this embodiment, when the operating company publishes announcements as website content for all store sites, the sub-spaces of store A, store B, and store C can create their own website content "Announcement Articles All" in a format that migrates from the parent space's "Announcement Articles All". Furthermore, by linking and managing the content of the source and destination, if the content of the source is updated, the update can be simultaneously reflected in the destination.

[0077] For example, if store B decides to offer a popular menu item from store A as a new menu item, and publishes it as website content on store B's site, it is possible to migrate the "product image A3" (for example, a photo of the popular menu item from store A) from another sub-space website media and publish the migrated media "product image A3" from store A's site as "product article B3" on store B's website content.

[0078] [Embodiment 2] In this embodiment, an example of a corporate organization building its own corporate website using the subspace function of the CMS server 10 will be described. Figure 24 is a schematic diagram showing the subspaces and model inheritance according to this embodiment. The parent space is "Development Environment" 110, and under it are the subspaces "Content Editing Environment" 110a and "Production Environment" 110b. "Development Environment" 110 is allocated as a development environment for engineers to create models, "Content Editing Environment" 110a is allocated as a content editing environment for editors to create and edit content, and "Production Environment" 110b is allocated for publication to visitors.

[0079] Engineers create models for each web page of the corporate website, based on page designs created by web designers (for example, page layout models for "Home," "News," "Company Profile," and "Recruitment"). Then, the layout models 111 (page layout models for "Home," "News," "Company Profile," and "Recruitment") created in the parent space, "Development Environment" 110, are inherited in the respective subspaces of "Content Editing Environment" 110a and "Production Environment" 110b.

[0080] Figure 25 shows the content creation and editing process for a subspace according to this embodiment.

[0081] Engineers create some web content by editing web pages (inputting content, etc.) in the "development environment" 110, following the page layout model via the editing UI. Here, some web content refers to content that is not updated frequently, such as the "Top" and "Company Profile" pages and the web content in the "Media" section.

[0082] The engineers also migrate the content and media from the "development environment" 110 to a subspace in the "content editing environment" 110a. The "Top" and "Company Profile" pages and "Media" pages of the website content in the content editing environment shown in Figure 21 are content created by migrating the "Top" and "Company Profile" pages and "Media" from the development environment.

[0083] Next, the editor of the corporate website content completes the corporate website's web content by editing the remaining web pages (such as inputting content) in the "content editing environment" 110a, using the editing UI to configure the page layout model inherited from the parent space to the sub-space. The remaining web pages are those with a high frequency of content updates, such as the web content for the "News" and "Recruitment Information" pages.

[0084] Subsequently, the editor (or engineer) migrates all content and media from the subspace "Content Editing Environment" 110a to the "Production Environment" 110b, between the subspaces "Content Editing Environment" 110a and "Production Environment" 110b. The production environment website content shown in Figure 21 is the content created by migrating the website content from the content editing environment. The CMS server 10 manages the content of the source "Content Editing Environment" 110a and the destination "Production Environment" 110b by linking them together, so that if the content in the source is updated, the update is simultaneously reflected in the destination.

[0085] Note that web page editing (such as content input) is not performed in the "production environment" 110b. Only website content that has passed validation checks in the subspace "content editing environment" 110a will be published in the production environment.

[0086] In this embodiment, a model was created in the development environment under engineer privileges, and the model was then inherited by the sub-spaces, the content editing environment and the production environment. Subsequently, content was created and edited in the content editing environment under editor privileges, and only content that passed validation checks was published in the production environment. By dividing the roles of those responsible for each space, which is the unit for managing the website, it is possible not only to improve site quality but also to further clarify roles within the website management unit and improve the efficiency of website operation and management.

[0087] <Summary> In conventional CMSs, when an organization manages multiple websites, managing models and content for multiple media within a single management space can be complex, or separate contracts may be required for each media. However, with the space function according to this embodiment, multiple spaces can be set up, and one space can be assigned to each website within the organization for management. This makes it possible to manage the models and content of each website separately for each space.

[0088] Furthermore, with the parent space and subspace functions according to this embodiment, engineers only need to manage a single model in the parent space that consolidates the implementation of the site, eliminating the need for redundant management. Editors, on the other hand, can manage content and media independently in each subspace while maintaining the same model as the parent space. As a result, multiple sites under a subspace can be managed individually with content independent of the parent space, while maintaining a unified site layout configuration, design, and implementation created in the parent space through model inheritance. In addition, when creating content in a subspace, it is possible to reference and migrate some content and media from the parent space or other subspaces, making site management easier.

[0089] While the present invention has been described with specific examples based on preferred embodiments, it is clear that various modifications and changes can be made to these examples without departing from the broad spirit and scope of the invention as defined in the claims. In other words, the details of the examples and the accompanying drawings should not be construed as limiting the present invention.

[0090] (term) • Organization: A unit for managing and associating spaces with users. An organization owner can manage multiple spaces, and each space associated with the organization is assigned an owner for management purposes. • Spaces: A space is a unit for managing site elements such as content, media files, models, and fieldsets. • Subspace: A feature that allows you to manage multiple identical configurations by inheriting content created with the Space function. A model is a template for content. It is defined by combining fields. There are two types of models: a multi-type model that allows for the creation of an unlimited amount of content, and a single-type model that allows for the creation of only one piece of content. Since the layout of a web page is defined by its content elements, it is also called a layout model. Fields are a feature that allows you to add input forms to the administration screen. You can design content by combining multiple types of fields. • Content: This is a physical representation of the model. It corresponds to web pages, blog posts, categories, etc. It can be created by entering content into the fields defined in the model. • Media: Files uploaded by users to be incorporated into content. This can handle all types of files, including images, videos, and PDFs. • Parent space: The space from which the subspace inherits (e.g., space 110) • Sibling spaces: Subspaces that share the same parent (for example, subspace 110a, subspace 110b, and subspace 110c) • Linked spaces: Spaces that have a parent-child or sibling relationship (for example, space 110, subspace 110a, subspace 110b, and subspace 110c)

[0091] (Note 1) A CMS server device for managing websites, A space setting means that sets spaces, which are units for managing a website, and establishes a parent-child relationship among the set spaces, designating one space as the parent space and all other spaces as child spaces (space setting unit 201, Figure 6, 12-14). A model creation means (model creation unit 102, Figure 7-10) creates a model that defines the content elements of a web page within a set space. The parent space is configured to allow the creation of the aforementioned model, while the child space is configured not to allow the creation of the aforementioned model. (Authority management unit 104) A model inheritance means that inherits a model created in the parent space as a model created in the child space (model inheritance unit 103, Figures 15, 16, 20) A CMS server device characterized by having the following features.

[0092] (Note 2) An editing means that retrieves content elements defined in a model created in a space and allows the user to edit content corresponding to those content elements, (Editing section 105, Figure 19) Each space includes a content management means for managing the content edited by the user, (Content Management Unit 106, Figure 21) The CMS server device according to Appendix 1, characterized by having the following features. [Explanation of Symbols]

[0093] 10 CMS Servers 20 System Configuration Terminal 30 Editor terminals 50 Networks 100 CMS 101 Space setting section 102 Model Creation Department 103 Model Inheritance Section 104 Authority Management Department 105 Editorial Department 106 Content Management Department 109 Storage section

Claims

1. A CMS server device for managing websites, A space configuration means that sets up spaces, which are units for managing a website, and establishes a parent-child relationship among multiple spaces, designating one space as the parent space and all other spaces as child spaces. A model creation method that creates a model defining the content elements of a web page in a set parent space, A model inheritance method that allows a model created in the parent space to be inherited as a model created in the child space, A CMS server device characterized by having the following features.

2. An editing means that retrieves content elements defined in a model inherited by a child space, and allows the user to edit content corresponding to those content elements, A content management system for managing user-edited content for each space, The CMS server device according to claim 1, characterized by having the following features.

3. A permission management system that allows model creation in the parent space but prevents it in the child space, The CMS server device according to claim 1 or 2, characterized by having the following features.

4. The aforementioned content management means is To make content managed in the first space accessible from content managed in the second space. The CMS server device according to claim 2, characterized by the above.

5. The aforementioned content management means is To make it possible to move content managed in the first space to the second space. The CMS server device according to claim 2, characterized by the above.

6. On the computer, A space configuration means that sets up spaces, which are units for managing a website, and establishes a parent-child relationship among multiple spaces, designating one space as the parent space and all other spaces as child spaces. A model creation method that creates a model defining the content elements of a web page in a set parent space, A model inheritance method that allows a model created in the parent space to be inherited as a model created in the child space, A CMS server program to enable this functionality.

Images