Custom structure

Description of the function of project configuration

Project configuration is needed to create complex structures with minimal effort and time.

This will increase your chances of avoiding the site from search engine ban and just improve navigation and usability to its visitors. All that is required from the user - it is to describe the desirable structure of the site and choose the keywords which should be distributed.

In the left pane is the current structure of the project in which you can select those items and categories that you wish to participate in the process of configuration. In the right - the future configuration of the project that you first need to describe. To do this using the context menu categories and the combined record are created. Combined records - the records in which will be posted all texts from small records that are suitable by chosen keywords, it means that the result is the creation of one large group of small records.

Under the window with the description of the structure there is control field of separate entry of this particular structure:

• Title - name of the future category or of the combined records

• Keywords- patterns of keywords on which articles will be defined in a specific category. If a pattern starts with ^ - then it means that the text must begin with the words going after this symbol (useful for creating an index, such as on a screenshot).

• Search field - Exactly where the program should look for keywords

Top of the post for combined input - a separator of articles that will be present at the beginning of each record.

For example, if you have the resultant record will consist of 3 records the names of which "Record 1", "Record 2" and "Record 3", and settings of header are the same as shown on the screenshot, the source record will look as follows:

1.<h3>Record 1</3>
2.... Text of a record 1 ...
3. 
4.<h3>Record 2</3>
5.... Text of a record 2 ...
6. 
7.<h3>Record 3</3>
8.... Text of a record 3 ...

After creating the configuration and filling in all fields, click the button Analyze - which will conduct the preliminary estimates and will show how many articles in which category falls after application.

The principle of distribution

In order to make it easier to understand how and where your articles will go after configuration process, we need to describe the principle on which the program works:

• First of all, the selected entries in the left window are distributed between the first level of the future structure. If a record is suitable for several categories, then it falls into that category, which consists of less records. This allows to get an equal distribution

• Then all records in each category are distributed between the first-level child elements (in the distribution involves only those records that fallen to the parental category in the previous step). If there are records that do not fit for any of child, then these items will remain in this category.

• The next step is the distribution of records between the elements of lower levels on the principle that was described above.

Insert categories / records from the buffer

It's all very simple, records in the buffer should be in this format:

1.Title;Keyword;Search field
2.Title;Keyword;Search field
3....
4.Title;Keyword;Search field

The last two are optional.

If you insert this:

1.Title;Keyword
2.Title;Keyword
3....
4.Title;Keyword

Then Search fields for all of these records will be "By the name of the article".

And if you insert so:

1.Title
2.Title
3....
4.Title

Then there will be no keywords

Distribution setting

Structuring allows the user to define some criteria for the selection of posts to obtain more accurate results. For each of the record types (categories and the combined record) there are setting of maximum and minimum number of entries. If using custom settings program reach over the border - then it begins to manipulate with "search field" settings in order to achieve more sustainable results. You should know that due to the fact that an exhaustive search of all possible options is very resource-intensive and time-consuming, because the algorithm for finding the optimal variant is designed in way not to take a lot of time and still have acceptable efficiency.

If the program go out of bounds of minimum or maximum value, then it changes the "search field" settings on the following principle:

1. If the value is less than needed - the "search field" changes to the previous (the one above) from a user defined list of "priority of search fields"

2. If the value is more than you need - the "search field" changes to to the following (the one below) from a user defined list of "priority of search fields"

From this it follows that the "Priority of search fields" must be such that the fields that will bring more entries were above, and those that smaller - below.