Add a new node

To add a new node to the site document tree one need to register in Smereka as an editor. After this editor panel should appear in the web page, which contains links to "View", "Edit" and others.

Please click the link "Edit" to put Smereka to edit mode. Here's the standard Smereka node editor described; node editors for specific sites may have different appearance and functionality.

Standard Smereka editor consists of an inspector in the left side of the window and the informator, which occupies the right side.

The inspector visually displays the node tree of the site. His look somewhat like a folder tree in Windows Explorer. Current node is highlighted by another background color. Attributes of this node appear in the informer, which consist of the fields for attribute values and group of command buttons at the bottom of the page.

To add a new node one should click one of four buttons on the vertical toolbar on the left of the inspector. The action buttons explained in floating hint. Using these buttons one can add a new node after the current one, before the current, as the latest in a siblings list, or as a child node.

The newly formed node loaded into informator. We should note that some of its attributes are set already: class and template of a new node are equal to the class and template of the base node, the access level is set to the current user access level, which protect the node from viewing by anonymous users, symbolic name becomes unique value formed with a node id (for example, 00001F2D).

Now one have decide whether the node class is appropriate for editor intentions. Since the class defines a set of node attributes, it is desirable to change it at the beginning.

To change the node class one should drop a list of classes and choose some value. This list consists of two groups, the first of which contains a standard Smereka classes and second (optional) – classes, introduced to this site.

After changing the class, one have save changes by clicking the button "Save" at the bottom of the informator. It will be downloaded with a new list of attributes and fields for editing, which corresponds to a given class.

Suppose that we are editing a node of standard Smereka Information class. In the first field – "Document title" – one can write, for example, "My first document", and in the "HTML code" field – the main page content, for example:

<p class="BT">
Eternal spirit of the chainless mind!
</p>
<p class="BT">
Brightest in dungeons, Liberty, thou art,
</p>
<p class="BT">
For there thy habitation is the heart,
</p>
<p class="BT">
The heart, which love of thee alone can bind!
</p>

Now one can see the results by clicking "View" toolbar link. Please be aware that each time you click on some link Smereka editor automatically performs saving changes in the document, so you do not worry click the button "Save". In particular, it is automatically saved when moving to another node or when switching to view mode.

There is the "Document title" attribute on the top of page, formatted with h1 descriptor, followed by HTML code. (Of course, the look of a page can vary greatly depending on the template; the described here page compiled with the standard Smereka Default template).

One can improve the look of a page, using all means are permitted in HTML format. One only need observe that all pairs descriptors will be properly closed, for example, that descriptor <table> necessarily correspond descriptor </table>, etc.

To finish editing the page, one can fill the attributes of "Window title" and "Description". Smereka uses the attribute "Window title" attribute to fill <title> element in the page, so the value appears in the header of your browser window. It should be understood that the attribute "Document title", unlike the "Window title", has no fixed purpose. Often it is used according to its name, but different templates can use it on its own or not use at all.

Smereka inserts "Description" attribute to the <description> tag of the page. Search engines, in particular, Google, happy to use this tag in its issue, so it required careful writing – this is the best way to explain search engine what is the essence of this page.

Finally, do not forget set readable symbolic names to pages, changing the mentioned above 00001F2D on MyFirstPage or ChillonSonet.

At the end of node attributes list typically placed four switches. What is their purpose?

"Hidden node". If the node is defined as hidden, it will not appear in the document tree (in view mode) and other navigators. Please understand that this attribute does not affect the availability of the node. For example, the this site node www.m-zharkikh.name/MailToEditor.html has the same hierarchical level and same accessibility as the www.m-zharkikh.name/News.html node, but the latter appears in the navigation tree on the site, but first not because it is marked as hidden.

So, hidden nodes is a way to unload visual navigation of the secondary elements, which can be accessed by other links on the page.

Please be aware that this setting is ignored in the editing mode when the editor of the site see all the available tree nodes, regardless of the attribute "hidden".

"Hide child nodes". If the node has this attribute, its child nodes (and even the nodes of its crown) will not be displayed in the document tree (in view mode) and other navigators. Other functionality is similar to the "hidden node" attribute: it just does not affect the availability of the top and just ignored in edit mode.

The main purpose of this attribute – unloading tree from navigating too deeply embedded nodes, which often only impedes the visual perception of the browser, rather than simplify it.

Example of use attribute "Hide child nodes" one can see in the gallery. Each gallery provides an independent mechanism for navigating the child nodes in a table of thumb images, so duplication of navigational information in the tree was considered superfluous.

"Smerecasheable. This attribute allows smerecaching this page. If the editor knows that this page contains frequently changing data, it can prevent its storing in Smerecash. In this case Smereka will perform full cycle of page generation each time it requested.

"Indexable. The action attribute this extremely simple: if it is set, the page indexing by search engines allowed. This corresponds to the value of a <meta name="robots" content="all">. Since this value is taken as the default, this line is omitted in the document.

If the switch is off, page indexing is prohibited. So, Smereka insert element <meta name="robots" content="none"> in the page. It is advisable to prohibit indexing pages that are not useful for reading text, for example, already mentioned MailToEditor.html page.