KR20050084999A - A customized life portal on the internet - Google Patents

Abstract

A user-created life portal for viewing and accessing content on the Internet and methods of implementing a life portal (102) are described. The platform, referred to as a life portal (102), is configured by the user to display only content that is of interest to the user, thereby reflecting the personality and life of the user. The content displayed in a life portal (102) is retrieved from websites and is not limited to sites licensed or maintained by the life portal service provider. Content is displayed as a view (110) or a magazine. Views (110) are stored in life pages (104). A content in a life portal (102) is specifically tailored to meet target interests and preferences of the user and is designed to exclude content not of direct interest to the user.

Description

A CUSTOMIZED LIFE PORTAL ON THE INTERNET}

FIELD OF THE INVENTION The present invention generally relates to Internet application software and website configurations, and more particularly to systems and methods for executing portal type websites on client computers that are optimized for specific users.

Numerous methods exist for creating custom or personal homepages in portals that are heavily accessed on the Internet, as well as in lesser known websites. For example, plain personal portals designed in a "top down" fashion such as "My Yahoo" and "My Excite" have been used for many years, among many other similar user tools and options on other websites and portals.

However, despite their use over the years, the use of personal home pages in widely used portals has not been widely accepted among the majority of Internet users. This is mainly a result of the relative complexity and sophistication required to construct, program and maintain personal and custom web pages. Moreover, even after overcoming the initial barriers to creating and organizing personal web pages, many users have found that the sites they create are not as individual and optimized as they expected. Many of them continue to have difficulty searching and displaying content that is truly focused on their interests, preferences and priorities.

Thus, for many users, the tools for creating personal websites do not meet their expectations or needs. For example, although a user may create a personal home page on a portal or portal type website, the user often still has to go through several web pages in order to reach content of interest to the user. One assumption is that users who want to check local high school sports scores or schedule information about community events may not be able to do so, or through the current personal website, or you may have multiple pages. Only after looking at it can you reach a page with relevant content. As such, the optimization level of the user homepage in many portals is not satisfactory.

Moreover, such content (eg, local news, sports, weather, specialized topics, etc.) may not be retrieved from an ISP or portal that manages a user's personal website. The range of available portals may be limited to content created or managed by the portal, or content made available to the portal (i.e., authorized by the portal or ISP), and may otherwise be a limited range of sources. have. Typically, portals and ISPs that provide personalized portal services are content aggregates. However, since most of the content on the Internet is not available in conjunction and therefore cannot be collected by third parties such as portals, the amount of content that can be collected needs to be limited. As a result, content collectors may not be able to provide a wide range of content that is required to fully satisfy the content that all potential users need, and each of the users will be interested in a unique and broad matter. Sources available to the portal are limited to sources authorized by the portal and may not have the content desired by the user, thereby limiting the level of optimization of individual web pages.

Moreover, portals using current meta-browsing technology to provide content to personal portals have serious drawbacks when considering the display of various types of content. In general, meta-browsing techniques do not tolerate crashes and errors that occur when manipulating content in a variety of formats and how websites execute or control content such as HTML and javascript. This restricts portals from providing content related to various aspects of their lives. In addition, current meta-browsing techniques do not allow users to view the full range of content on a web page. For example, current meta browsers can only allow users to view content restricted to a single table, but not to view the entire portion of a web page. Current technology also frequently maintains and does not continuously display tables in views via the current meta browser. In addition, meta-browsing techniques are not efficient for placing content that users may want to follow in the fashion of interest. After all, meta-browsing techniques are often difficult and burdensome to use, thus making the majority of non-technical users inaccessible.

What is needed is a personal website that can be created and maintained in a precisely optimized, efficient and intuitive manner. Accurate personal websites or portals that significantly reflect the user's life and who the individual is; That is, it is desirable to allow a user to create a web page that expresses the user and directly attracts the user's interest, as if looking at a magazine dealing with a website and a topic selected by the user.

Such a personal portal should be a unique set of content that reflects each user's personal interest collection, ie, a bottom-up optimized portal for the user, without undue limitation. In addition, it is desirable for the user to be able to create a user portal that represents unique content, and the user is interested in the content and exhibits interest through a user interface that facilitates information access and information viewing. In addition, it is desirable to create a life portal on a client computer without installing or downloading any applications on the client computer. The life portal user must be able to access his life portal from any computer with a browser and connected to the Internet. The content should also be displayed functionally without failures and errors. The life portal accepts content from sites that have not previously been visited or known to the service provider to modify the content so that the content is displayed without problems and generally. It must function consistently with the expectations of the user. This should also be done explicitly to the user and, therefore, should not be requested to interfere with the user in the process of modifying and displaying the content.

The present invention is better understood with reference to the following description, in which figures are added.

1 is a hierarchical diagram showing a life portal structure according to an embodiment of the present invention;

2 shows a relationship between a life portal service provider, a life portal user, and a third website that provides content to the life portal;

3 is an overall flowchart of a process of creating a custom life portal from a standard life portal according to an embodiment of the present invention;

4 is a display screen of a life portal and a life page showing a magazine and a view according to an embodiment of the present invention;

5A and 5B illustrate a display screen of a life portal showing an action menu that a user can perform on a screen, a magazine, and a life page according to an embodiment of the present invention;

6 is a diagram illustrating server-side execution of a life portal according to one embodiment of the present invention;

7 is a diagram illustrating a client side execution of a life portal according to an embodiment of the present invention;

FIG. 8 illustrates a logical representation of a sample data set or table that may be used to apply a rule to content before the content is displayed on a life page, according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

102; Life portal 104; Life page

106; A persistence panel

108; Portlet 110; Content or a view

202; Life portal service provider

204; Software and hardware component

206; Life portals 208a, 208b, 208c; Site

302,304,306,308; Step

602; Client computer

604; Life portal

606; View or parsed view

608; Life portal server

610; A third-party web site

702; Client

704; Life portal 706; Life page

708; Life portal server

710; Content source

In one aspect of the invention, a bottom-up user life portal on the Internet is described. The life portal has at least one living page and at least one screen included in the living page, the screen being content related to the user's interests. In another aspect of the user life portal of the present invention, one life page includes at least one magazine, the magazine including text and links to guide the user to articles related to the user's interests. By optimizing the content, including the screens and magazines contained in the life page, the life portal closely meets the user's unique interests and specific needs.

In one embodiment of the present invention, a user may create a pixel view, which is any portion of content selected by the user from web pages collected from a website. In another embodiment, a user may create a parsed view, which is the content constituting a table from web pages collected from a website. In another embodiment of the present invention, a user may create a magazine that includes text, such as the title or headline of an article about a particular subject selected by himself. Magazine content is derived from the life portal service provider that determines what titles should be represented in articles, clusters the subjects so that they are logically indexed, stores the subjects, and links to articles in the service provider database.

These content, regardless of the form of views, magazines, or other structures, are generally contained within portlets that are included within life pages. Content can also be stored in a container called a persistence panel in a life portal. Content is collected and collected from virtually any website on the Internet, and is not limited to websites that have prior relationships with service providers, such as licensing agreements or contracts, and are not limited to content created and created and delegated by service providers. Nor do. In another embodiment of the present invention, the life portal service provider provides a screen and a magazine pre-generated by the user on a subject that the service provider believes the service users will be interested in or contains high quality content. do.

In one aspect of the invention, one method of implementing a life portal on the Internet is described. When referring to client-side execution, the life portal applet is placed in a browser on the computer when the code needed to retrieve and parse the HTML for the life portal is first installed or created on the client. By being planted a life portal is created on the client's computer. The creation and use of the life portal should not require the client to download or install any application. While executing the life portal to the client, using the client's IP address, cookies, and the like, a request for content from the website is made from the client computer rather than from the life portal service provider. The applet performs some functions, such as analyzing content using an analysis engine, determining appropriate rules using a rule engine, and applying these rules to the content. In another embodiment, the life portal retrieves content from a site using Active X or similar control means and causes the content to be displayed on a life page. In this embodiment, no application or applet is interposed in the client or the client's browser.

In another embodiment of the present invention, the life portal service provider searches for content for a life portal user. The content is analyzed at the service provider server and the rule is applied to the content before being sent to the client computer for display as a screen in the life portal. When referring to server-side execution, the life portal service provider server performs most of the content processing, stores cookies and other user protection data, and uses its own IP address when searching for content. . The server also stores content from frequently accessed sites.

In both aspects of the present invention, a user can access his or her life portal from any computer with a browser and can access the life portal service provider site.

In another aspect of the invention, a method is described for modifying content such as HTML from a web page from an original site for display in a life portal. The applet or portal engine determines whether the domain from which the content was retrieved is listed in the domain table. If the domain is listed in the domain table, the corresponding rule set is identified. This is done by examining the domain / rule mapping table that associates domains with rules. The rule applies to content from a domain. In one embodiment, the content is HTML, and the rule modifies other code, such as the HTML and JavaScript, so that displaying a portion of HTML separated from the original document on the screen is problematic. Do not cause trouble. If no domain is found in the domain table, the default table of rules is applied to the web page. If the default rule does not cover all the problems caused by displaying the screen, then the new rule is attached to a set of rules maintained by the life portal service provider. The rule set is expected to grow as new domains are attached to the domain table. Applying the rule to the content in this manner enables the user to display HTML on the screen with little trouble and trouble when viewing the content on the screen on the life page.

The content of the invention is now described in detail in the preferred embodiment of the invention. Preferred embodiments are described in conjunction with the drawings. Although the invention is described in conjunction with the preferred embodiments, the invention is not limited to one preferred embodiment. On the contrary, it includes alternative technology, modification technology, and equivalent technology which may be included within the spirit and scope of the invention as defined by the appended claims.

The present invention encompasses the execution of the life portal and a user-created portal on the Internet referred to herein as a life portal. A life portal includes one or more storage containers referred to as a life page. A living page is a content storage area, which in turn stores information in the form of magazines or views, both of which are content specifically edited for the user. Magazines and screens are stored in portlets. Thus, a life page can have a plurality of portlets for storing content. The life portal of the present invention reflects the life of the user; Display specific interests defined by the user in selected aspects of the user's life. Life portals reflect a user's interests to a large extent and are limited only by content accessible on the Internet and other public and private networks such as intranets, virtual discrete networks, and the like. In the described embodiment, the Internet and browser are used as practical examples, but other networks, data sources, and user interfaces may be applied to the concepts and practices described herein for the present invention.

Methods and systems for using and creating life portals and their components, including life portals, are described in various forms. In a preferred embodiment of the present invention, a standard life portal is first given to a user. The standard life portal is customized by the user, displaying the content as a view and a magazine, most of which is retrieved from the Internet.

In another embodiment, the user is given an empty life portal from which the user can begin to create a life page and a persistence panel described below. The content is displayed as views and magazines stored in life pages categorized according to titles selected by the user. In another preferred embodiment, the user is initially asked a series of questions when creating a life portal. Based on the answers to the questions, the new user is given a pre-created life page containing screens and magazines that may be of interest to the user. The user is also given the opportunity to become familiar with the use and processing of life pages, screens and magazines. The answer to the question determines which category and title the user is given in the form of a life page. For example, if the user's interest is more about finance and business than entertainment or sports, then the selected pre-created life page reflects this broad category and will allow the user to further customize this category. Can be. Of course, the user can create and possibly create his own life pages, screens, and magazines that uniquely reflect the user's life.

A hierarchy of components comprising one life portal is shown in FIG. 1A. On the basis of this hierarchy, the life portal 102 on the Internet is viewed through the browser. There is one or more life pages 104 under the life portal. It is also a persistence panel 106, i.e. a special form of storage that stores content that, in principle, is not suitable for being stored in a life portal, and therefore in a life page, but which the user frequently watches or wishes to see. There may also be a container. The persistent panel always includes a screen and / or magazine displayed on the life portal. Below each life page is a portlet 108. There is content 110 in one portlet, especially at the bottom of the hierarchy, with views and magazines. The screens and magazines may be pre-created or uniquely created by the user.

The life portal of the present invention has a user interface designed to allow a user to navigate on the Internet through the portal and to create and retrieve contents effectively and intuitively. For example, in the described embodiment, life pages are represented by tab icons that resemble folder tabs. In another preferred embodiment another pictogram icon or design such as a button or menu may be used.

The life portal engine and its overall management and operation are under the control of the life portal service provider. As described in more detail below, content from the Internet is fetched. That is, as described below, HTML is typically retrieved and collected from various websites, in theory, any website on the Internet that can be accessed using a browser, using HTTP commands. In the described embodiment, the life portal service provider server stores text that is used to index magazine content.

Larger forms of fetched content, i.e., a technique for gathering content required or selected from an entire HTML page from a website, are known to those of ordinary skill in the field of Internet application programming. The service provider is not a particular content collector specified or restricted to fetch content only from selected content providers or content contributors associated with the service provider; For example, the content in the living portal is not limited to the so-called "walled garden."

The user modifies the life portal by creating, deleting, and modifying life pages, screens, and magazines. The user may change the criteria used by the life portal application software to collect content from the service provider's database, thereby changing the screens and magazines in the life page and the persistent panel.

The relationship between a service provider, a life portal user, and a website that provides content on the Internet is shown in FIG. Life portal service provider 202 maintains software and hardware components 204 that power the creation and preservation of numerous life portals, such as life portal 206. For example, one of the software components 204 is a database containing content, such as news articles and other forms of content based on sentences, the content being a key word or concept known in each field. It is collected from the website and titled by the life portal service provider using techniques to determine the title from the collection technology and content, such as how to use it. As described in more detail below, titled content is often used to create magazines. The range of websites, such as sites 208a, 208b, 208c, is unlimited, as long as service providers are allowed to access the site and collect content, and content is collected from the site.

The content is collected from a third website and examined by the life portal service provider 204 to represent the title found in the content. This is done to edit the magazine. In the described embodiment, a magazine is included in one or more articles having a title that is directly related to the title of the magazine. As described below, content, primarily articles, are titled, clustered, and propagated to one or more service providers by a life portal service provider or other suitable entity capable of performing these functions. At this time, content suitable for a magazine may be identified and edited in a magazine form and displayed on a life page or a continuous panel. The magazine may be described as having a newsletter format. In particular, in the described embodiment, a magazine is included in one or more content descriptors, which may include the following items; The headline or title of the article, article abstract, article source, date and. Appropriate photo or picture, if available. In another embodiment, a magazine's content descriptor may have few information items or may have a huge number of information items. For example, in some cases, content descriptors may only have a title or article abstract. In another example, the content descriptor may have an important article, indicating the relevance of the article to the magazine title.

After the title of the content is determined and the content is clustered based on the title, it is distributed to the life portal 206 as magazine content. The service provider fetches the content without placing any self-limitation on the accessible site.

Thus, service providers are not limited to content that is hosted, licensed, or created by a content provider or content acquirer or other hosting or sponsoring entity. In general, the service provider will select a website that is accessed from any website available on the Internet. The user may request that the service provider access a particular site and fetch content of particular interest to the user. The service provider will determine whether to access the site in consideration of the request. In another preferred embodiment, a service provider may contact a site such as a pornographic site or refuse to access a site that contains content that is illegally obtained by the site, such as copyrighted content that is legally required to authorize. Reasonable restrictions may be placed on access to

3 is an overall flowchart of a process of creating a personal life portal according to an embodiment of the present invention. Before the process begins, the user goes to the life portal service provider's website on the Internet. In one scenario, the user's Internet service provider provides access to the life portal service provider registration page. For example, the life portal may be a tool or feature provided to the subscriber by an Internet Service Provider (ISP) and activated by the life portal service provider. In any case, once at the registration page, the user generates a password and completes other administrative steps as required by the ISP or life portal service provider.

In step 302, the user begins the process of creating a customized life portal. One of the main objectives of the present invention is to allow the user to create a portal that best reflects the various aspects of his or her life. Especially. In step 302, the user is represented by an empty life portal screen.

In another preferred embodiment, the user is provided with a pre-created life page when the user answers the question examined by the life portal service provider. In the described embodiment, the content of a pre-created life page includes a site that provides content that the service provider believes can provide high quality content or that it is likely to appeal to many users. do.

The present invention allows the user to dynamically build a bottom up life portal; That is, the user establishes a unique and optimized life portal that matches his interests or special needs. This is done by fetching content from a database of service providers, titled and clustered for inclusion in the magazine, and fetching content from an unlimited range of websites on the Internet for display. The user creates a truly unique portal that is optimized for him and reflects various aspects of his life. In the described embodiment, the life portal has only content that is of interest to the user, effectively selected by the user. In another preferred embodiment, the life portal may include some content not selected by the user, such as a life page containing content selected by the life portal service provider or affiliated ISP. However, the amount of such content is trivial and typically limited to one life page compared to the content selected by the user.

The content is collected from a wide range of websites by the portal engine, and with respect to the magazine, it is titled and clustered based on the content of the content. The portal engine may fetch content from the Internet or from any website accessible through a browser or another form of user interface accessible to a public or private network.

In the described embodiment, the portal engine takes a website and places the collected content in a filing cabinet. In another preferred embodiment, in addition to the Internet, various forms of data formats or other forms of textual languages may be collected from data sources. Content is collected from pages of sites with content that is updated regularly. Regarding the magazine, once the site is initially collected, the following content collection is directed to updated content and titles, for example, daily or weekly. Methods of collecting and retrieving content from a website are known in the field of internet application programming.

After the content has been collected, the life portal service provider examines the content and gives the content a title. For example, dominant phrases, words, etc. are identified or dominant concepts are identified and the portal engine gives one or more titles to the content or page. As more content is imported and collected, the number of titles maintained by the service provider is expected to increase accordingly. Titles are extracted and stored in the database with the content. In the described embodiment, a title does not exist in the database unless there is some content associated with that title. In another embodiment, a title may exist in a database without the content associated with that title. Each time the content is extracted from the database, the content title is likewise extracted. This is done using algorithms known in the field of computer programming. After the content is titled and before the content and its title identifier are stored in a database, the content is clustered with existing content based on the title of the content.

The newly collected content may have one or more titles, in which case the link to the content exists at one or more locations in the cluster hierarchy. New content is clustered with existing content using algorithms known in the field of computer programming. By clustering content titles, the portal engine can collect all content related to a particular subject. This process is used in article editing for magazines.

Clustering is a process of organizing a plurality of pages from one or more sites in a hierarchy based on titles in the pages. Such pages or, more generally, the content are clustered contrary to the title. Thus, a group of pages, each page being one type of content, share at least one common title. The portal engine determines the title for each zone. The user creates a magazine by entering search criteria that define the subject of such a source, such as a magazine or, in another embodiment, a site from which a service provider collects content related to the subject of the magazine. The life portal service provider may also create a magazine for that user. Pre-created magazines are created in the same way as ordinary magazines, except that the service provider initially identifies each magazine source or website. For example, a ready-made magazine on professional basketball may have an NBA page on NBA.com, an ESPN.com website, or an NBA page on the FoxNews.com website. These three sources, among other sources, are content sources that can be used to create a magazine that is made available to the life portal user by the service provider. In the described embodiment, the service provider collects magazine content from sites determined to be used for magazine content. These pools of sources are expected to expand as time and methods increase. In a preferred embodiment, the user may have a life portal service provider or sponsor go to a particular website to obtain content for magazines about a subject of interest to the user and place these sites on a list of sites titled by the service provider. You can ask to be added. The service provider may make a final decision whether or not to take content from one or more sites requested by the user and collect and give a title. The service provider is expected to accept the user's request to add a new site as a source for practical and actionable magazine content.

The user has the ability to create screens for many lesser known sites that provide content that may not be available on many major portals and websites, such as Excite, MSN, or Yahoo. The user can also create a magazine that includes content on any subject of interest to the user. The magazine includes links to related content and textual content, such as news stories related to the topic selected by the user, titled by the service provider. In the described embodiment, the user can select content from pre-created screens and magazines created by the life portal service provider. These off-the-shelf screens and magazines include content that may be of high quality content that a wide range of users may be interested in and that the service provider believes will appeal to that user. In creating a magazine, the user initiates a search for content that has already been collected, titled, clustered and indexed by the service provider. The user is not limited to a so-called "walled garden", ie a limited set of websites, when searching for content. The user may also request to bring a particular website for content.

In step 304 the user begins to create a life page. In a preferred embodiment, the user is provided with an empty life page, which can be described as a canvas, where the user organizes and organizes content, screens and magazines. In another preferred embodiment, the initial life pages are categorized from a predefined list supplied by a service provider or supplied by a response to a request made by a service provider that effectively determines a user's interest. Is made by selecting. The user can essentially assign any name to the life page. The name is shown on a graphic or design depicted by a tab or other picture. In the embodiment described above, the name is always displayed above the life portal regardless of which life page is displayed.

In step 306, the user provides a criterion for supplying content to the life page. Users can supply life pages as desired without serious limitations imposed by the life portal service provider. The content may correspond to any topic selected by the user and may be a specific or ambiguous topic. This approach to delivering content to life pages reinforces the notion of building a life portal that uniquely satisfies each user's interests and priorities from the bottom up.

As mentioned, one kind of content is magazine. The user presumably selects a life page for a particular issue that corresponds to the subject of the life page and creates a magazine. The portal engine edits the magazine for the user by retrieving controversial articles from the themed content in the life portal service provider's content database. The user may suggest or request that content be collected from these sites and used for inclusion in the magazine.

In the described embodiment, the service provider determines which site is to be searched for content so that prohibited content cannot access the service provider's database. The most relevant portion of the content is located and collected on various websites to create a magazine. In either case, the headlines of news articles hyperlinked to different types of sites and other types of articles combine to create a magazine. Thus, the magazine is uniquely optimized for the user. In step 308, the user continuously supplies content to the life page by generating a screen. One screen is content from one website and allows a user to view a portion of a third party's website without leaving the user's life portal. In fact, part of the third website is a component of the user's life portal and is observable using a meta-browser. Views and magazines are stored in portlets. In the case of these screens, portlets allow the user to view the screen through a meta-browser, and a browser located within the user's browser is used to view content from another website. In the described embodiment, other types of content or tools, such as video or JavaScript, may be included in the portlet.

Once the user has created a magazine and / or screen for the life page, the process of initially supplying content to the life page is complete. The process then repeats for another life page in step 310. The user can show or hide a persistence panel in the life portal regardless of which life page is displayed.

One of the objectives of the present invention is to create a life portal using screens and magazines stored within life pages that closely reflect the unique nature, interests, preferences, and other aspects of a particular user. Thus, life pages, screens, and magazines of the personal life portal may vary.

 The life portal service provider may also allow the user to modify to some extent the look and feel of the life portal. One aspect of a life portal is to allow a user to view multiple screens and magazines simultaneously from different life pages. In the described embodiment, the user creates a life page as described in step 304 of FIG. Life pages can be described as folders for screens and magazines that share common themes or issues from the eyes of the user. The life page is given a title by the user, which may be any name the user desires, and is characterized by further emphasizing the concept of a life portal that reflects the personality, life, and interests of the user. Once a user has created a life page, for example a "MOVIES" life page, the next step is to create a screen and a magazine within the MOVIES. It is a container, or folder, and therefore is of no importance or useless if the content is unpopular In the embodiment described above, the content is a screen or a magazine.

Screens and magazines are generated for the topics selected by the user. In the movie life page, the user may create a screen that is content from a “Hollywood Reporter” website, and another screen that is content from other “Variety” websites. It is also possible to create magazines that contain headlines and are linked to articles about movies by specific studios, The content based on the articles and texts will come from various websites and, therefore, magazines are a suitable medium for this content.

The user can give an arbitrary name to the life page as well as the screen and the magazine. The life page may also be pre-generated by the service provider and may include pre-generated screens and magazines. Pre-generated life pages, screens, and magazines are components that the life portal service provider believes that many life portal users will be interested in because the content is particularly high quality and that the service provider will attract the attention of the users. This is the component you want. For example, a life page, named CURRENT EVENTS by a life service provider and predefined, is a predefined life page, such as a screen that displays part of the CNN website or the first page of a Wall Street Journal. Screen can be provided. Similarly, a life page may have a magazine created in advance. The user may decide to keep or delete a predefined screen or magazine and add his own screen and magazine in the life page. The user can also change the name of the life page from the current events (CURRENT EVENTS) to another name.

In the described embodiment, the user may perform certain functions or actions on screens, magazines, and life pages. For example, a user can add or delete screens, magazines, and life pages. The user can also edit screens, magazines, and life pages. Some editing functions for life pages include initialization, save, delete, recharge, and rename. Some screen editing features include pinning, moving, deleting, recharging, renaming, and setting automatic refill rates.

If the web page from which the content originates therefrom undergoes a change in form or configuration, such as inserting a table, the user can execute a fixed screen operation. If the fixed screen operation is selected, a new window appears and the user can adjust the screen as required.

For example, the user may select another table or segment from a page, or instruct the engine to use the seventh table instead of the sixth table on one page. By performing these operations, Life Portal Engine will control how and where the data is retrieved from the website. For example, a table on a web page may be moved, resized, or changed in some way. Many popular sites frequently restructure the page.

One sample magazine is shown in FIG. 4 in accordance with one embodiment of the present invention. The magazine is a list of headlines and links to those articles stored on the life portal service provider server and originally collected from third party websites. Articles and content for magazines are compiled from content collected from websites by a service provider. Various content is collected to form the text of the magazine article.

Likewise, screens are also unique to the user. Screens, in contrast to magazines, come from a single web page and represent content from only one page of the selected web site. However, the user instructs what will be on the screen and what content of the page will make up the screen. In the described embodiment, there are two types of screens: parsed views and pixel views.

In general, an analysis screen is content from a single table collected from web pages from one website. Many websites organize data within web pages into tables. The life portal engine analyzes web pages and separates them into tables.

The pixel screen originates from retrieving the entire webpage from the website and from allowing the user to display any portion of the page and does not include analyzing the webpage or identifying tables in the webpage.

A parsed view is created by analyzing and tabulating a website. As is known in the field of internet application programming, websites often use tables to describe and organize content on web pages. Many websites use tables in this way. The web pages are analyzed to separate the tables, each table containing a portion of the content of the website. The user selects which table includes the screen. In the described embodiment, when selecting a table, the user moves the cursor over the table after the page has been analyzed and clicks on the table of his choice. As the cursor moves over the table, delimiters that separate around the table change the indication that the user is in a new table. In other preferred embodiments, other HTML components such as DIV tags or SPAN tags may be analyzed.

A pixel view is the full web page offset behind what can be viewed through a portlet, that is, the pixel screen hides the portion of the web page that the user does not want to view. In generating the pixel screen, the portal engine does not analyze the web page. The entire page is loaded and configured such that the only content shown on the screen is the content the user wants to view, regardless of the table structure on the web page. The pixel screen is selected to use a cursor to define an area on the web page by which the user wishes to be the screen. The enclosed area may be dragged to any place on the page when defining the pixel screen. Once the area is demarcated, the content from the web page is placed in the portlet to the pixel screen.

In the described embodiment, the user can select whether one screen is to be analyzed or pixelated. In another embodiment, the infrastructure of the screen is determined by the life portal service provider. The fact that different types of screens exist is visually apparent to the user. However, if the content from the website is displayed as a pixel screen, the entire web page is delivered to the life portal. As a result, pixel screens may cause unexpectedly large data volumes to be delivered to the user's computer, thereby consuming significant bandwidth and causing processing speed degradation on the life portal. In contrast, the analysis screen is derived from generating content, that is, a table selected by the user.

Tables may be provided in other tables. In the described embodiment, after the service provider parses the HTML on the web page, the user selects the table using a pointing device to highlight the requested table. For example, when a table is highlighted, the background and text color can be converted, the image can be displayed in reverse shades, and landmarks that separate the analysis table like a red line are hatched or flickered. The user then clicks on the selected table and the table becomes the screen.

As described above, the screen may occur by analyzing a web page, the analysis screen may be a table, or may be generated by overlaying a portlet on the entire web page and displaying a portion of the page as a screen, a pixel screen, and other parts of the web. The part is hidden from the screen. In general, web pages consist of HTML code with different features and formats. Problems and unexpected results occur when HTML content is collected from the original site and sent to other sites, where content such as web pages is processed in different ways and displayed in the meta browser.

For example, at the originating site, the web page may have a window that displays and displays an advertisement, or may have a mechanism for presenting an error message to the user that may be undesirable in a life page. In another example, the table selected from the collected web page may reference code such as JavaScript, neither in the web page nor in the code for the selected table. Thus, there is a need to frequently modify the HTML and other code included in a web page so that the page content can be displayed as a screen on a life page or persistence panel.

The issues and issues described above are responsible for the implementation of the life portal and the life portal user is not required to download any application to the user's computer. Thus, a user can use all the features of the life portal of the present invention using a typical browser without having to download or install a single application from a life portal service provider or any other entity.

In a preferred embodiment, the user's computer, or client, is provided with an applet, which performs certain functions, such as analysis and rule engines (described below), enhances the life portal, Enable communication with the portal server. In another preferred embodiment, the client uses an ActiveX control or similar control in the client browser to fetch content or HTML from a website. In this embodiment, referred to as client-side execution, the client derives the collection of web pages from a third-party source on the Internet or from a life portal server.

In one embodiment, the life portal server, referred to as server-side execution, is responsible for retrieving content and sending the modified content to the customer for display as a screen. However, there is no request to download or install any anomalous application software on the user's computer in this implementation. Moreover, in both client-side and server-side performance, the user can access his life portal from any computer connected to the Internet. In client-side execution, the browser must be able to accept applets or cookies (typical default settings), or execute ActiveX or equivalent control. For example, one limitation is that ActiveX only works on certain operating system platforms or browsers.

In a preferred embodiment, the client browser collects content from a website using ActiveX control. Once the content is collected, client-side code is needed to collect the content and rules are applied to display the content on the life page. Active X controls developed by Microsoft, or equivalent controls or code developed by other third parties, only collect content in the form of web pages. The control or code may be developed by a third party or life portal service provider that performs the same or similar functions as the current Active X control. This potential future control can be used to perform the same functions as the current ActiveX controls. In the described embodiment, the code is embedded in the web page; That is, JavaScript is generated on the client in a web page in the browser and executed in the browser.

In the server side execution of the life portal, the client online only communicates with the life portal server and not the third party side. The life portal server retrieves the web page from the third site, parses the HTML (for screen analysis), and delivers the relevant HTML segment to the life portal on the client.

6 is a diagram illustrating server-side execution of a life portal according to an embodiment of the present invention. Client computer 602 executes life portal 604. The life portal 604 has a life page including an analysis screen 606. The analysis screen is used only for the purpose of explanation. The described process is also applied to the pixel screen. Using an analysis screen provides an opportunity to explain the role of the analysis engine in the overall process. When the life portal 604 is called or opened by the user, a request for each analysis screen and pixel screen (among other data) is transmitted from the client computer 602 to the life portal server 608 via the Internet. Part of the request for life portal server 608 is to retrieve content for screen 606.

In server-side execution, life portal server 608 forwards the request from client 602 and retrieves the content from its own database (“stored” content) or from third website 610. The content, which is a web page standardized for each screen, is retrieved and processed by the life portal server 608. The process includes an analysis for the analysis screen. The modified HTML is delivered to client computer 602 and displayed as screen 606 in life portal 604. In this implementation, client computer 602 performs a minimal process. The rate at which the client 602 accesses the modified HTML and other content from the life portal server 608 is the type of connection between the client 602 and the Internet, namely dial up, broadband, etc. Depends on In the described embodiment, life portal server 608 has a high-speed connection with the Internet, such as a broadband or T3 connection. This is expected to be an acceptable implementation because the server 608 can simultaneously search for content for numerous life portal users, especially all web pages.

A request is an HTTP request from life portal 604 to server 608 and is related to a screen, such as screen 606, and more particularly, an inline representing the screen 606. frame), that is, a request from a frame. The request includes all the parameters needed by server 608 to collect and advance the HTML content for screen 606 and life portal 604. Life portal server 608 may be storing the content in its own database server. When life portal server 608 goes to websites and collects the HTML, it analyzes the code and extracts the table needed for a parsed view 606. In the case of a pixel screen, the web page is not analyzed and the entire page is delivered to the life portal 604.

Although server-side solutions are advantageous, for example, when the client is an Internet supporter, a so-called "thin" client, there are aspects in which it can be canceled under certain circumstances. For example, some very connected sites are sensitive to the same IP address being accessed too often. Too many connection attempts is a legitimate interest in many popular websites and can slow down or crash web servers. When an operation problem occurs, the third web server may simply refuse to further access that particular IP address.

Another problem with server-side execution is the confirmation of all users. Certain sites require user confirmation to access the content. Once the visitor is verified, the site typically stores a cookie on the client computer 602 by entering a username and password. This eliminates the need to log in again if the user returns to the site within a predetermined time, such as per hour, referred to as the expiration time for the cookie after leaving the site.

However, storing cookies for the user on the life portal server 608 is burdensome and poses a safety issue with respect to the user's login name and password. Another issue that may arise from server-side execution is a third party who suspects that life portal sites are collecting that content and consequently attract more users and are better known. The third party may not be favorable to the life portal site because the life portal service provider is accessing the content and effectively redisplaying it, and the original site may not display advertisements that rely on revenue. . This operational limitation is responsible for the client side execution of the life portal shown in FIG. In a preferred embodiment of life portal execution, client computer 702 plays a greater role in retrieving and progressing HTML for life portal 704. The life portal 704 still makes a request to the life portal server for each screen, which is similar to the request made in the server side execution. However, server 708 returns only the data that client computer 702 needs to retrieve the content directly from the third party. Life portal 704 retrieves the entire webpage from content source 710 using these parameters related to the screen. In some cases, the webpage may be stored internally in a browser on client computer 702. These parameters include data relating to displaying the screen and retrieving content, such as a URL for the content, and other data relating to the screen and rules for analysis (described below).

The client computer 702 advances the web page using the applet it obtained when the user initially created the life portal 704. The Java applet is embedded in a web page read by the browser on the client 702 during the initial life portal creation process. As is known in the field of Internet application programming and in accordance with W3C guidelines, applets are part of the standard HTML component. Applets can be run within a page using standard HTML tags as defined by the W3C. Thus, the applet is downloaded without serious interference from the user. Typically the user follows a predetermined step of approving the applet by clicking a button telling the user to accept the step.

Considering creating a screen within a life page, the links used to initiate the screen creation process are components of the page (not necessarily limited to the life page) in the life portal, rather than being embedded within the page. These links are attached to your browser's "Favorites" toolbar. In the described embodiment, the links execute JavaScript. In the described embodiment, the user selects a button in his browser to perform a function in the life portal, such as generating an analysis screen or a pixel screen. Such buttons or icons, which may be included under the "Favorites" menu of the browser, have inherent client-side code. This intrinsic script or button can be referred to as a bookmarklet (an industrial language for bookmarks that execute client-side scripts). Typically, this type of button is a link to another web page by default. For example, at a particular website, a user can decide whether to want to create a screen in his life portal from that site. The user opens the bookmark list in his browser and selects the "Create Screen" button, a bookmarklet in the list.

By doing so, the underlying client-side script to create the screen is called. By invoking the script, the client computer connects to the life portal server and passes the URL of the site that the user wishes to create a screen from. Upon receiving this data, Life Portal Server delivers the only configured page to the browser, allowing the user to continue creating screens on the life page.

In addition to using bookmarklets to create screens, users can also create unique controls that can be downloaded to a client computer and installed to complete the same task. The value of doing so is that more control can be gained from the installation and the buttons look and feel in the user's browser.

       The user simply follows the instructions for creating a life portal and downloads the applets and other components needed for the portal in the process. Downloading applets during the installation of any type of application or tool via the Internet is common sense and generally evident to the user. In server-side execution, the user follows the same steps to create a life portal, except that the applet is embedded in a browser. However, applets can still be introduced in server-side execution for future use (ie, if the user decides to connect to the client-side execution) and can be done explicitly to the user.

The user can suppress the browser from accepting the applet, in which case the life portal can be run using server-side execution. Applets on the client 702 run the analysis engine, rule engine, and other functions on HTML. The functions operating on client 702 in client-side execution also generally operate on life portal server 608 in server-side execution.

In the client-side execution of the life portal, the client 702 is responsible for collecting third sites for web pages associated with the screen. In this practice, for a third website that requires confirmation and uses a cookie to reenter the site, the cookie from the site is stored to the client 702 and thereby to all users who use the site. Can be confirmed. By having the cookie for client 702, life portal server 708 does not need to store cookies or any other protected data associated with the user. In the client-side implementation, client 702 makes a request for HTML to a third site. Thus, a crowded site will not see the same IP address, i.e., the IP address of the server 708, in some way collecting content from them.

By using client-side scripts to process HTML on the web page, it is not allowed to restrict the browser in a limited way, allowing the web developer to edit and manipulate content mounted in the user's browser from other domains. To do this, the client 702 needs an applet. For example, one browser may use connecting HTML on a third site, but cannot modify the HTML within the browser using JavaScript from another site. The applet may be displayed as a screen, allowing the browser of the client 702 to collect, process, and parse HTML, if necessary. Web pages are requested through Java components within applets using standard techniques known in the field of Internet application programming. In a preferred embodiment, the service provider determines the appropriate applet for the client 702 based on the client equipped, i.e., Java Virtual Machine, such as Microsoft JVM or Sun JVM, and the Java class (Java send the appropriate applet to the client that the applet needs to run. As a result. The user does not need to download any application to upgrade or to modify the applet and can therefore coexist with a specific JVM.

As mentioned, technical problems may occur when displaying a screen within a life page collected from a third website. The content, the main HTML code, responds and functions sensitively to failures or unexpected behavior when separated from its original context in a web page or similar larger context. In order to prevent failures or malfunctions when displaying single or multiple screens on a life page, the life portal applies a set of rules to web content before being displayed.

In the preferred embodiment, the rules are applied to web pages according to the domain / rule set mapping table. In client-side execution, these rules are applied by the applet. The domain / rule set mapping table comes from two sources: a list of known domains and a set of rules. The list of known domains includes the name of the website for which the life portal service provider wants to establish broader rules for collecting content. Typically, these are domains where content is collected regularly and frequently. The list is expanded to include the sites requested by the life portal user, from which content is collected (either by the client or by the life portal server), and a rule mapping is derived for it.

FIG. 8 illustrates a logical representation of a sample data set or table that may be used to apply a rule to content before the content is displayed on a life page, according to an embodiment of the present invention.

The table shown in FIG. 8 illustrates the concepts and data organization after applying rules to content. Substantial performance and programming of these logical structures can take various forms and can be accomplished by one of ordinary skill in the computer programming arts. A list of known domains is shown as Table 1. Each domain has a unique identifier that corresponds to it. Table 2 lists the rules and parameters used by rule engines installed in applets or portal engines to prevent unexpected behavior or failures when editing and displaying content as screens. Examples of this rule are provided below. The unique resolver, preferably having a different format than the only resolver used to identify the domain name in Table 1, is associated with each rule in Table 2.

Each rule is responsible for one issue or problem that may arise when displaying content as a screen on a life page. However, most of the problems that are typically derived from JavaScript code in the web page may arise from other forms of code. Initially, the life portal service provider anticipates many problems that may arise and derives a rule or set of rules to cover each problem. It is expected that unexpected problems will arise when handling new sites or new types of content. When this happens, the service provider derives a solution to the issue and materializes it as the rules in Table 2. Thus, Tables 1 and 2 are not fixed lists, but rather lists that are expected to grow as the number of life portal users increases and the content types of web pages vary.

Using the knowledge of tables 1 and 2 of the life portal service provider whose rules should be applied to each known domain, the service provider generates mapping of domain names to rules. The service provider may also anticipate and detect problems that may occur previously and derive rules to account for them. However, although one rule can be applied from a particular domain to a web page to make it work as expected, however, applying the same rule from another domain to a page will produce undesirable results. By applying a rule across pages from all of the domains listed, certain pages can be pinned but other pages can be damaged or unaffected. Therefore, it is important for the service provider to apply the rules to each domain by maintaining the existing scheme. Table 3 illustrates the domain name / rule mapping table for performing these tasks. The life portal service provider determines which rule or rules, if any, need to be applied to each website from which the service provider will collect content.

For example, a failure may occur when a portion of the HTML representing the screen ("screen HTML") is analyzed from a web page containing JavaScript. The web page has HTML, but only a portion of it, like a table, is needed for the display. Part of the need may include HTML that is dependent on JavaScript or HTML that does not exist in the screen HTML. As a result, when the screen HTML is executed on the life portal, the user sees an error message caused by the invocation of code not present in the screen HTML. The rule or parameter to handle this issue may be to modify a tag in the screen HTML so that no error message appears and the user can continue to work without interruption. Another possible rule may be to include the dependent HTML or JavaScript with screen HTML. The rule or rules are selected by the life portal service provider, inserted into Table 2 and associated with one or more domains. This relationship is inserted in Table 3.

When a web page is collected from a new domain, either by a client or by a life portal server, the analysis engine examines the entire page to determine which of the existing rules need to be applied to the page, and sends relevant rules to the page. Apply. If the service provider decides that existing rules will not be responsible for problems resulting from the screen HTML, the service provider derives additional rules and adds them to Table 2.

In the preferred embodiment, rules are derived by the rule engine in the client applet that associates the domain with the rules as shown in Table 3. In this embodiment, only rules that need to be applied to the page are applied. Before the rule is applied to a page, the rule engine determines the domain of the web page. For example, the engine detects that the web page is from CNN.com, checks the domain / rules table, and determines which rules will apply to the CNN.com domain identifier. The rules are collected and applied to the page thereby potentially modifying the webpage in several ways. The analysis engine then analyzes the page. When the engine detects that a subsequent web page is from another domain, another set of rules will apply, even if the rule (s) is the same as the CNN.com domain.

In order for the extracted screen HTML to work as smoothly as the screen of a life page, most web pages are expected to require some modification. For this reason, the identification and application of the above rules and parameters to web pages is necessary to minimize disruption and unexpected behavior when utilizing screens in a life portal. Furthermore, applying the appropriate rules to known domains in advance, such as modifying them to be in perfect harmony with the HTML and other code before displaying the screen on a life page, allows for efficient and efficient use of the life portal.

As webpages are collected, the domain / rule mapping table is consulted to see which rules apply. As a life portal service provider adds a new domain, it checks the web page from the domain to determine which existing or new rules are needed to account for potential failures and problems in displaying screen HTML from the new page. Decide The rules and domain listings are expected to grow over time and as life portals have more users. Life portal users can also request web pages from domains not listed in Table 1. In the described embodiment, there is a set of default rules of rules that are applied to the new domain when the optimized ruleset has not yet been elicited. The default set of rules is determined empirically, that is, from experience in addressing issues with various types of HTML, JavaScript, and other code of service providers. The default rule set is expected to cover most but not all of the problems. This is particularly reliable as websites become more complex and less commonplace. If the problem persists after the default rule set is applied, the service provider checks the HTML and devises a new rule to take care of the remaining problems.

Applying rules to web pages can have undesirable effects on the functionality of the page, particularly screen HTML.

For illustrative purposes, we may assume that life portal users do not want an advertisement popup window to appear on the screen. To meet this expectation, there may be a rule in Table 2 that prevents advertisement pop-ups from appearing on the life page. The HTML of the web page causes the pop-up message to appear. More specifically, it is the standard javascript function or method of the web page that acts to invoke the pop-up window and the rule acts to suppress the popup window. This is done by overriding the "open" method of standard JavaScript that exists by default in the browser. So instead of calling the browser to open a pop-up window, JavaScript is turned into a method that does nothing. In this example, the life portal service provider adds a dummy or functionless method to JavaScript. If there is an "open" method in JavaScript, the new method is called; if there is no "open" method, the new method is not called.

However, if another web page from another domain has a button or other icon in the screen and shows the user the text in the pop-up window when the screen is activated, the text on the screen may be useful or decisive information for the user. have. By applying the rules mentioned above to this web page, the execution of all pop-up windows, regardless of their content, will be suppressed. By applying this rule, the buttons on the screen will not function, which compromises the usefulness of the screen. By running Tables 1, 2, and 3 using the rules engine, the rule is applied to the first web page where the pop-up window is used for advertising, and the second web page with a button to display the information pop-up window It is possible to selectively apply rules so that they do not apply.

When generating an analysis screen, the analysis engine retrieves all the HTML from the page, including any form of document reference, JavaScript reference, and the specific HTML you want to see (most often in a table, but not necessarily included). And return these components back to the portlet. If none of the rules apply to a web page, there may be cases where you refer to HTML elements on the screen that existed previously in the page but were removed during analysis. An error will occur when the JavaScript is executed. Because this error is caused only by modifying the HTML content of the original page, the user would not expect this error. Therefore, it is important for Life Portal to suppress these error messages. This is done by applying rules that suppress all JavaScript errors. This example illustrates the assumption if a JavaScript error occurs; In another hypothesis, JavaScript errors also occur, but this rule suppresses those errors regardless of the assumption that they cause the error.

In the described embodiment, the Internet is used as the basic medium through which content and other data are delivered, and the web site is used as the basic content sources from which content is collected and viewed in the life portal. In another preferred embodiment of the present invention, it is apparent that the content source and media are not limited to web sites and the Internet.

Another form of electronic data distribution can be used to gather information; Information may be collected from various electronic sources in addition to the website; It can then be progressed and displayed via a user interface on visual aids other than Internet browsers (ie, handheld devices, computers with built-in computers, etc.). All such preferred embodiments are within the scope of the present invention.

Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it is apparent that certain changes and modifications may be practiced within the scope of the appended claims. Furthermore. It should be noted that there are alternative methods of implementation for both the processes and tools of the present invention. Accordingly, the embodiments of the invention should be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but rather may be modified within the same scope as the appended claims.

According to the present invention, the user can search and display content that is truly focused on the personal interests, preferences, and priorities of Internet users, and can be created and maintained in a precisely optimized, efficient and intuitive manner for the individual. You can create a personal website that you have. Accurate personal websites or portals that significantly reflect the user's life and who the individual is; That is, the user can create a web page that expresses the user by using the content and directly attracts the user's attention, as shown by a magazine dealing with a website and a topic selected by the user.

Claims (26)

(a) creating a life portal on the client computer with a life portal applet interposed in a browser on the client computer; (b) the request is forwarded from the client computer to the third server and the view data is passed from the third server to the client computer to execute the life portal on the client computer; (c) using the screen data to collect content from a third website; (d) displaying the content in a life portal on a client computer. The method of claim 1, The step of creating a life portal further comprises the step of creating a life page in the life portal to accommodate one of the view (view) and magazine (magazine). The method of claim 1, And delivering the life portal applet from the third server to the client computer while the life portal applet is delivered and intervened in the browser in a manner apparent to the user, while creating the life portal on the client computer. How to run a life portal on the Internet. The method of claim 1, And the request includes data related to the screen in the life page. The method of claim 4 wherein the third server is Receiving the request; And And retrieving data associated with the screen, sufficient to cause the client computer to retrieve the screen and present the screen on the life page. The method of claim 1, Processing the content on a client computer using a life portal applet prior to displaying the data in the life portal. The method of claim 6, The content processing step further comprises applying a rules engine to the content to make the content suitable for display on a life page. The method of claim 1, A method of running a life portal on the Internet, wherein only applets are delivered to client computers to run the life portal. The method of claim 1, Using screen data to cause content to be collected from a third website by a client computer. At least one life page; At least one screen contained within at least one life page; Wherein the at least one screen is a bottom-up user life portal on the Internet, characterized in that the content is related to the user's interests. The method of claim 10, And at least one magazine contained within at least one life page, the at least one magazine being content in the form of headings and linked to external content related to user interests. A user life portal characterized by the above. The method of claim 10, And the at least one screen is a pixel view generated by displaying a portion of the web page selected by the life portal user. The method of claim 12, And the content is titled by a life portal service provider and used to edit the at least one magazine. The method of claim 13, And the content is clustered by a life portal service provider and used to edit the at least one magazine. The method of claim 10, A user life portal further comprising at least one first portlet to accommodate at least one screen. The method of claim 12, And at least one second portlet for accommodating at least one magazine. The method of claim 10, And the at least one screen is a pre-created view created by a life portal service provider. The method of claim 10, The content for at least one screen in the user life portal is retrieved from a plurality of websites on the Internet, wherein the plurality of websites is not limited to a pre-determined set of websites. Life portal. The method of claim 12, The content for the at least one magazine is retrieved from a plurality of websites on the internet, the plurality of websites being not limited to a pre-determined set of websites. A life page that can accommodate a portlet that can accommodate one of screens and magazines related to the user's interests, wherein the life portal is created to satisfy a plurality of user interests Life portal. The method of claim 20, A plurality of screens and a plurality of magazines can be viewed simultaneously in the life portal user life portal. The method of claim 20, And said screen is a pixel view so that content including said pixel screen is any portion of an underlying web page. Determining whether the first website is on a domain table list; If the first website is on a domain table list, identifying a rules set corresponding to the first website in the domain / rules map table; Applying said rule set to content, thereby creating content suitable for display in a life portal of a second website, How to modify content from the web page of the first website for display in the life portal of the second website. The method of claim 23, wherein And applying a default rule set to the content, wherein the content is modified from the web page of the first website for display in the life portal of the second website. The method of claim 24, Creating a mapping between a rules set stored in a rules table and the first web, the first website for display in a life portal of the second website; How to edit content from your web page. The method of claim 24, Adding a new rule to the rules table when the default rule set fails to properly modify the content for display on the second website. How to modify content from web pages of the first website for display.