In the "Writing fine-tuning" view, you can place a particular to the writing by pressing a "include" button of one of the particulars in the "writing particulars" list. A reference to a particular can be placed with a "ref" button. Numbers for captions are generated automatically (the presence of a particular type in caption is optional). The placement of an included particular can be changed by selecting a location in the text where it should end up and then Ctrl-clicking on the placeholder of the particular that you want to move. The fine-tuning adjustments for a particular can be accessed by selecting a placeholder of a particular (either by selecting it directly or by moving cursor on it with the arrow keys). From the particulars attached to a writing one can also select one "main image", which has its own separate adjustments.

In the project managing view, inline-editability is available for changing name for a collection of writings.

In the writing list view, inline-editability is available for changing dates.

In the "Solution writing editing" view the E and S symbols (from the words "end" and "side") next to writings that has a type of "area text" are used to including such writing either to the end of the writing or as part of the content. Tthere are buttons for detaching these in the same view below the writing adjustments and table listing attached particulars.

In the "Text editing" view, the table listing the writings has a feature to display a little more information about the writings in their own columns. Here can be seen some of them: Readyness, Availability, Lastedit and Updated.

In the "Text editing" view, the table listing the writings has a feature to display a little more information about the writings in their own columns. Here can be seen some of them: Writing type and Size. There is also Description, which is limited to 30 characters, so that it can be used, for example, to group writings by a short keyword or group of keywords. Writings can be deleted by clicking on an icon resembling a paper airplane.

In the "Text editing" view, Ctrl-clicking on the name of an entry in the list of entries gives access to a mode where the position of a writing in the list of writings can be changed by rolling the mouse wheel. Alternatively, you can click on the arrow icons that cause a writing to move one row at a time, which can accessed by pressing the "Adjust sorting order" button. Save with the "Adjust sorting order" button.

In some views, it is quite common that the height of the view becomes rather high due to space requirements of different panels and other elements and thus it recommended to use a mouse with a wheel to scroll the page. Sometimes even that is not sufficient to maintain usability, and that's why the visibility or space requirements of some parts of the view can be varied between the two options. Lever controls for this are available, for example, in the writing fine-tuning view. In the same group of levers, an lever has been added to be able to select and list also those writings and writing collections that has been marked as non-participating ones.

Writings may have several types of text parts, such as Introduction and Opinion. Their visibility to the author can be adjusted by making them visible or invisible by selecting them individually or using presets. If you disable a text part, this does not remove the text in the text part, which avoids damage. These settings do not affect how the text appears to the reader, as it is affected by whether there is content in certain text area and, in some cases, whether a separate visibility setting is turned on in the writing fine-tuning view. These settings affect both views in which the content text of a writing can be edited.

Sometimes you may have so much text, pictures and other attached particulars in one writing that you could move some of them to another writing. For just such a situation, there is a function in the menu that copies the selected area with all its particulars to a (special) clipboard, so that the user does not have to add all of it separately to a new writing.

Picture 1. An earlier screenshot, with only two functions in the Misc menu.

In the text editing view editor's font sizes etc. can be quickly switched between the alternative styles.

Picture 2. The Misc menu appears to have a number of functions to choose from. Certainly not a stabilized set of functions, but all of these are useful to have near the text editor.

Dragging files directly from the hard drive (or other storage device) of the computer you are using makes it easier to perform certain functions such as importing images of a certain type, converting Word documents and importing a zip package containing a backup of a single project. Drag zones are identified by the visual cue that appear in the form of a border and background change when a file, file or other qualifying element is overlaid on them. Visual cues aren't constantly present in the user interface as this would often be an unnecessary visual distraction.

In the project managing view, the cover image for a project can be changed by dragging an image onto related panel, which is then also displayed in the project list view. Alternatively, the image can also be selected from a file list provided by the operating system used (also works on mobile devices).

In the text editing view, you can generate a new writing by dragging a newer or older Word file onto a table listing writings, which is automatically converted to text that is stripped from stylings. Plain text files can also be imported in the same way, i.e. there is no need to open the file with an editor installed on the operating system, copy text on the clipboard etc.

In the importing view, there is an "upload multiple" drag and drop area, which allows serial import of multiple images.

Since there is no height specification for the images included in the writings, but only a width percentage, images can be swapped without having to be readjusted. A previous image can be replaced by dragging a new image onto the image element that is visible when the image details form is displayed. It exists in three different views: particular browsing, importing and item moving. Images can be moved from one container to another or attached to a writing (from one tab or window to another) while in a grid-like listing.

In the project list view, it is possible to import a single backup of a project by dragging the related zip package onto the project list panel.

In the "Catalog images" section of a writing opened in the "Text editing" view, it is possible to attach an image dragged from the "Particular browsing" view. From the view being open in another window, that is. Alternatively, of course, you can also use the "Attach catalog image" function.

In the adequates view, a single opened adequate approves images dragged from the particular browsing view. From the view being open in another window, that is. Alternatively, of course, you can also use the "Add image particular" function.

Possibility to make backups is always available

In the project managing view, there are project-specific backup functions that allow you to backup everything or something to be kept somewhere else or to be exported to another project a moment later.

A whole project with its writings, images and other stuff can be wrapped in a zip package with a single button press and if needed, the same zip package can be dragged to the project list in the project list view, where a new project is generated from the contents of that zip package. Please note that this will also regenerate all the image catalogs used by the project, i.e. no attempt will be made to combine the new project with any existing image catalogs in the service.

To be honest, the ability to put multiple projects in a single backup without the backup containing the image catalogs used by those projects multiple times is already available, but the user has to enable such functionality separately due to the potentially high server load. Backups generated in this way can be drag'n'dropped into the project list view as usual (image catalogs would not be duplicated even if multiple projects use the same ones).

Just the writings as JSON data

If you don't need to backup the whole project, but just want to copy collections of writings from a project so that they can be used in another project, you can copy these writings as JSON structured data, which can be passed as input in the importing view of another project. The item moving view would not allow the moving of writings beyond the boundaries of a single project.

Publishing a solution elsewhere (only to those, who have experience in making web pages)

It is possible to export the work contained in the project in to a zip-packaged file, so that the contents of that zip-package can be copied via FTP or SCP to a directory on a server of one's choice and be made publicly viewable in a browser. A work exported this way wouldn't have differences in its outlook, but the contents would be completely "static" (not generated separately at every page load). The images in the work can be distributed via a CDN service or retrieved directly from that another server by the browser. This feature is under consideration and may be disabled.

If necessary, the project list view has a function to generate an index list of published works, but if the user wants to edit the index list in the HTML editor, some know-how about building websites might be required. In practice, generated index.html file contains all images as base64 encoded data with CSS stylefiles/JavaScript libraries included.

A reader of writings of a work might want to "dose their reception" by not just scrolling up and down through a visibly open collection of writings, but instead give some time to each writing and then move on to another with as little link navigating as possible. For such there's an adjustment in the work-specific settings and which is meant to hide/show links to all writings of the writing collection that currently visible writing belongs in.

When you produce several works, you may want to create one-directional references between them, rather than copying an entire text from one work to another and maintaining them both. These redirect links are created in the text editing view in the same way as regular texts. The effect can be seen in the table of contents of a work using a "plain structure" type of table of contents. These links can redirect only to pages of works in the same instance of the publishing application and it should be noted that the functionality of these links is not checked when the project or part of the project to which the link refers is removed or when the project in which the link is located is exported, removed and then re-imported. It is possible that the import of a project will be accompanied by some kind of visual reminder that the imported project contains redirection links.

Each blog-type work has its own RSS page, which can be used in RSS aggregator applications, i.e. those that produce a browsable list of the work's content using the metadata of the writings. You can also set a caching period for these.

The publishing application can be used with multiple views open at the same time on several different tabs or browser windows, but it can also be used simultaneously on several different devices. On one device, or more precisely, on one browser, user first have to log in with a password, after which user is presented with a login session code, which can be used to log in to the publishing application with the same username on an unlimited number of browsers. When a view of the user interface of the publishing application is just open and visible, it is not using server resources at all.

This can be useful, e.g. when writing on one device, such as a laptop, while at the same time holding a tablet-type device in portrait mode with some notes visible on it. An alternative to just that would be to use one login and an extended desktop with e.g. a monitor connected to the HDMI connector. Or maybe user want to have two different devices with the publishing app ready to use, but uses only one device at a time. One log out is sufficient. No need to do it on every browser/device.

Kuvat ovat eräitä tietynlaisista, joissa voi käyttää sekä tavallisen tyylittelemätöntä selitetekstiä, että automaattisesti attribuuttimaisena käytettävää tekstiä. Attribuuttimaisuus saadaan käyttöön, kun jokainen selitetekstin rivi on sellainen, missä kahden kaksoispisteen molemmilla puolin on jotain tekstiä, mistä sitten seuraa, että vasemmanpuoleinen teksti näytetään attribuutin nimenä ja oikeanpuoleinen sen arvona. Allekkain päätyvinä näitä voi käyttää monenlaisten tietynlaisten esim. luonnehdintaan tai toisistaan erotteluun.

There are three choices for the maximum width of the text in a writing ("rather narrow", "widish" and "very filling") and a writing can also have an oversized type of main image. Included particulars scale according to the maximum width of the writing.

In the text editor menu, there is an option to translate the selected text into English. The selected area can contain any of the styles that a writing is allowed to use. After about one second of text translation, the style will still be as before, only the language of the text have changed for the selected part. The text translation uses the DeepL service directly from the browser, i.e. the server of the publishing application is not used in between. A free user account for DeepL is required to obtain an "apikey", which is set in the user-specific settings of the publishing application.

User-specific settings also include settings for external services. Only the CDN address is required and necessary, the others are completely optional. The aim is to select external services that provide a real added value to the use of the publishing application and for which no payment is necessary. The image shows only a couple of external services for which an API is required, but there are a lot possible services to be used.

To avoid unnecessarily taking responsibility for external services that users may have paid for separately, apikeys are primarily stored to cookies in user's browser. If user wishes to save the apikeys to a database on the server, an alternative "Save apikeys to database" button is displayed, when pressing the Ctrl key. Apikeys are only stored in one of two places, either in the database or locally as cookies, i.e. when saving them to cookies they get removed from the database and vice versa.

In the adequates view, a great help in data collection is the retrieval of additional information from the content behind a link, immediately after the link address has been entered in the Url text field and the user has made that text field unfocused by clicking elsewhere in the same modal window or by using the tab key to move to the next visual element. The title of the page behind the link is then automatically retrieved and the corresponding text field in the form is filled. At the same time, a "'sort of" short description of the textual content of the page is generated, but not stored anywhere. The "sort of" here refers to the fact that this summary text and the mentioned page title have been retrieved using a third-party API, and it can not be given much more parameters than the desired length of the resulting summary text. This API is only free of charge up to a certain limit (per month).

In the text editing view, a great help in data collection is the retrieval of additional information from the content behind the link/id. This information is retrieved using an additional service, e.g. the service provided by the YouTube that outputs information in oEmbed format. A query returns structured (i.e. machine-readable) information, e.g. on the length, author and height in pixels of a video (in the case of an online video). Some of this information is not visible to the user at any point, but is used in other ways.

The device on which the publishing application is used may lack a physical keyboard with modifier keys (e.g. a Shift key), or perhaps the working posture favours doing things one-handed. There are some user-spesific settings to choose from, one of which causes one or more switches to appear in certain views, where the choice made is taken into account in certain situations. Other user-specific HID settings include preventing changing order of particulars already attached to a writing and particulars that are attachable to picture shows, since on some mobile devices, providing such functionality would make it

Picture 1. difficult for a third-party software component to operate well.
Picture 2. The particular browsing, item moving and importing views can show two switches for use instead or in additition to Shift and Ctrl/Meta keys.
Picture 3. In the two most typical text editing views, a switch is displayed to allow re-placing a placeholder element without having to press Ctrl/Meta at the same time. In the "Writing finetuning" view, the switch is near the group the other switches.

Each separate view (e.g. "item moving") is divided horizontally into 1 to 3 groups, depending on how wide the browser window is. If less wide, some views will hide the rightmost group of panels etc. and if the width is less than a certain pixel width, all groups of panels and elements will be put on top of each other, making the view oblong in shape. Such a feature or possibility may be useful when keeping several different views open in several different browser windows, or if the goal is to limit only slightly where you want to focus your attention (e.g. in the text editing view, you may sometimes want to hide the particulars group).

Picture 1. All three horizontal groups in the text edit view visible. Under the text fields, there might be additional (unhidden and optional) text fields.
Picture 2. In the text editing view, writings of one collection of writings and an opened writing.
Picture 3. All horizontal groups put on top of each other, when the minimum width of the browser window is below a certain limit.

Some views may have other or additional width triggers, which then affects how the elements on the page are arranged. The particular browsing view is one where there are several such triggers, and in its case this is due to the aim of providing a quick way of presenting multiple images using different layouts without having to go to some buttons to select a layout.

Errors and parts of the text that need correction in a written writing may sometimes be better noticed by printing out the text in the editor and making notes and markings on paper. In this case, the printout will not contain any particulars at all, but just the text with minimum styling.

A logged-in user can do reviewing on writings by going to the works page displaying a writing (or a collection of writings) and pressing the Shift key to enter edit mode. This allows you to immediately type (in red) and strike-out text (by holding down the left mouse button and swiping over the text). To erase the markings made, hold down the Ctrl key and mark the area to be erased with the mouse. Press the Shift key a second time to exit edit mode. These entries are not saved anywhere, so reloading the page will reset the situation.