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. 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. Hovering over those kind of writings animates the color of the name of the writing they are related to if they are shown in the same table. And the same the other way round. It may also be advisable to name (ending)areatexts in such a way that it is possibly to tell from their name in which writing they are used, especially if they are placed in a different writing collection.

There are buttons for detaching these in the same view below the writing adjustments and table listing attached particulars. If it happens that areatext that is attached to a writing is moved to a different solution, then it don't get shown, when viewing the writing.

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.

There are no plans to introduce timed publishing of writings, but one can pre-set the dates of your posts, organise them as one sees fit and then make them as participating when it's time to publish them. Draft writings can be made by creating a new writing, keeping it open and then Alt-clicking on the writing that should be copied to it in its entirety. Later, same can be done in reverse and the writing then left as redundant may be deleted.

The availability and update dates of a writing can be changed to be 10 minutes later or sooner by Shift-clicking or Shift-Ctrl-clicking on the relevant data cell. This is useful if one is preparing to put writing in a chronological publishing order. If the date information is blank when clicked, the time is first set to the current time and then changed to be 10 minutes later or sooner.

The readyness statuses can be changed quickly between preparing, later and almost by clicking on them while also pressing either Shift or Shift and Ctrl. In the bulk editing view multiple writings' readyness statuses can be changed at once, but it requires navigating to there.

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.

If one clicks writing while holding down the Alt key, the contents of the selected writing will overwrite much of what the opened writing used to have. The overwriting does not affect the title of the writing, its readyness level nor its participating status, but everything else. Since this kind of overwriting also changes all previous particulars of the opened writing, such as images, this can be used e.g. for versioning writings, e.g. in situations where one is about rewrite something but don't want to publish the changes immediately, but sometime later. Afterwards overwriting can be done in the opposite direction, so that the public address of the writing doesn't need to change.

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 textarea and, in some cases, whether a separate visibility setting is turned on in the writing fine-tuning view. These textareas can be seen in many views, wherein writings can be edited.

Some of these textareas have more sophisticated functionality, such as linking references to parts in the content text of a writing, selecting a date with the mouse, selecting tags from a dropdown list, etc.

The usefulness of the References text field is improved with a few features. When this text field is defocused, references appear in panel instead of the text field so that the links act like links. When there's a number in bracked on the left side of reference information, Ctrl-clicking it inserts a numeric reference to the text content of the writing where the cursor is positioned. Next to actual links are automatically fetched favicons. All these links will be renumbered if Ctrl is pressed at the same time during the defocusing phase, which should be used with caution, as the references already in the content text will not be changed. Clicking on the reference number in the brackets already in the content text will highlight the reference in the References panel.

If the browser allows it, links can be drag'n'dropped from browser bookmarks into the References text field when it is empty, and the links will be added to that text field. The text field will then be hidden to show the references information in the panel version. The security restrictions of many browsers prevent reading the name information of multiple links and might allow to do so only on the first one or none at all. That's why links from bookmarks can only be drag'n'dropped one at a time to the panel and all at once to the text field.

Of these textareas, the Document header and Document footer are only used in the writing sending view, where one can e.g. generate a Word document based on a writing, which can be given a header and footer. This is an experimental feature for which address, document type name and date may be given, and which will be placed in appropriate positions together with page numbering etc. The syntax is described in more detail in the placeholder hint of the relevant textareas.

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 always 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). An image can also be drag'n'dropped from the "particular browsing" view, which will result in creating a new image for that purpose only. That all also applies to cover images of solutions. There can be two different cover images per solution, where the rule is that if a solution has only one cover image, it will be used in appropriate size on both the solution index page and the front page of a solution, but if holding down the Ctrl key during the upload phase a different image will be saved as the solution index cover image.That all also applies to cover images of solutions with the difference that they are used in the public solution index instead of the project list view.

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. When a plain text file is dropped to the writing table, it is possible to make the file be read using encoding ISO-8859-10 by pressing Shift key at the time of dropping. Web addresses can be dropped over the writings table in a few different views, with the result that the web address is processed using an external API to extract the name of the web page and its mildly AI-assisted inferred "relevant content", which is then saved as the name and content of a new writing. If a redirectlink is dropped over the writings table while pressing Shift, a new writing of such type is created. Some browsers have restrictions on which links can even be dragged, but many allow doing it e.g from address bar and bookmarks.

The file names from which the names of writings are created can be prepared several at a time using e.g. the PowerShell ("an advanced shell that allows, among other things, the execution of scripts to automate many computer functions") included in the Windows operating system. It can be used to e.g. name all the files in a directory based on some criteria.

Removing the "df - " at the beginning of a file:

get-childitem *.docx | foreach { rename-item $_ $_.Name.Replace("df - ", "") }

Renaming files completely so that the filename starts with "gh_" followed by numbering in ascending order, where the numbers are preceded by up to two zeros:

Get-ChildItem *.txt | %{Rename-Item $_ -NewName ('gh_{0:D3}.txt' -f $i++)}

In the alternative text editing view, you can also drop text content from plaintext or Word files into "sliced" parts of the writing, which will then be placed exactly where the text cursor is located in that "slice" at that time.

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 moving things. 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.

Items in an adequate can be moved from one adequate to another by dropping an adequate item on the target adequate in the table listing them. Adequates can be moved from one adequate set to another by opening the adequate set and dropping an adequate over adequate set drop-down list.

Another view that includes drag'and'drop areas is the File storing. Writing named "Project files, CDN files and importing using SFTP" has information about its functionalities.

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.

The Text editing and Fine-tuning text views have slightly different text editor menus for the Misc and Tools menus. In the latter, tools such as language translation, blank line deletion and printing are available. Misc menu's items can be used to change the appearance of the text editor by changing the font and the type of placeholders, among other things. In the view that has more affection the styling and layout of published text, helpful tools include the ability to quickly change the width of all images in the writing and to place all attached image-type writingparticulars to a writing at once.

There are a few different ways to affect the size of the "Content" area of a writing. Vertically, it is done by moving the horizontal bar at the bottom of the Content text area. Horizontally, there are many options in the Mood menu, one of which hides from view the table on the left listing the writings, to leave more space to Content area. The other one does not hide it, but narrows the width of the left and right sides. The third is the default setting, where everything has a reasonable amount of space. The others arrange more screen space for images and places them in a grid or one above another.

When there is a lot of text together with many subheaders it can be useful to momentarily make the subheaders stand out a bit more, but not too much. Sometimes it can be useful to have all the subheadings in the text copied to the clipboard, so there is a function for this in the Tools menu.

These menus are subject to change from time to time as features are added, but not everything that can be done is added there, such as the ability to place some special characters to the text as such can also be done by using so-called alt codes, i.e. pressing the Alt key and typing e.g. 0173, which will then will place a "soft hyphen" to the text. It may may not look like anything visually, but the browser can hyphenate the word at that point.

There is a separate button for saving, but one can also press Ctrl-S (Command on a Mac) to save the writing. Other special features of the "text editing" view, for which there are no visual hints, are described in the writing "Listing table functionalities".

The pictures show that there are some options for the styling text. There are four types of list styling: bullet list, number list, bulletless list and "on same row bullet list".

Some stylings will not appear in the published writing, as they are only meant to be an aid to editing. Useful at least when, during the content production phase, some relevant points are marked and which can also be copied to the clipboard all at once.

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.

The References text field of a writing serves both as a normal text field where references can be put, and also as a more useful memory aid. Any line in it that begins with a number in square brackets can be Ctrl-clicked to add the corresponding reference number to writing's content text. The references thus added to the text will appear in the published version, but without the highlighting style. In the text editing view they the be clicked, which caused corresponding line in the References text field will to be visually highlighted. Between those numbered lines there may be other lines of text which do not have the same functionality, but are just text. When the References text field is defocused, a panel is displayed in its place, showing the links with the favicons provided by the target sites.

If text excerpts have been placed to a content text of a writing but not all if any of the relevant reference links are put in the References textfield, references can be retrieved automatically for each text paragraph. In practice, search engines are used to search for matches in the text paragraphs, after which the relevant content text (e.g., article text) is retrieved from the found page candidates in another way and compared to the retrieved text paragraphs for greater certainty. The reference links found in this way is marked as a reference for the text paragraph in question, and the same is done for each text paragraphs. This does not work reliably with e.g. quotations that are used on many websites, because it is not possible to automatically determine which of them is the source of the text excerpt, but otherwise it works very well on article and news websites.

In another use case, both text paragraphs and reference links are available, but the connection between them is not set. In such case, the missing reference connections can be added in similar fashion to above-mentioned method. This makes it easier to collect text excerpts from the internet, because the text excerpts and links can be "thrown somewhere" and the connections between them can be added later.

Since texts can sometimes become very long and contain many references, one may want to edit them separately and then combine them later. At that point, one may notice that there are overlaps in the numbering of the reference links. To fix this, the References text field need to be focused and after which, while holding down the Ctrl key, scrolling up or down with the mouse wheel causes the reference numbers to change in both the References text field and the body text of the writing, allowing one to increase or decrease the numbering in the whole writing at once.

If one wants to manually add reference numbers to writins's content text, but the reference links do not have any, such can be added to all of them by holding down the Ctrl key while defocusing the References text field. If reference numbers should be removed from References text field, that can be done by holding down both the Ctrl and Alt keys while defocusing.

The text editor's menu has other functions for handling references, such as using one or more links between text paragraphs as sources of information for the preceding text paragraphs, i.e., those links are automatically used as reference information and the reference numbers are inserted into the text at the same time. In this way, one can search the internet for text excerpts e.g. relevant to a topic, insert the relevant links after the text paragraphs, and continue doing the same as later they can all be automatically handled. Reference numbers without reference links can be removed from content text semi-automatically, as the unused reference links can be removed semi-automatically from the References text field.

When transferring files to the server, especially when transferring large files, one may want to know the current subprocess and an estimate of when the transfer will be completed.

Thus, when importing a project or a solution from a project, the project list view will display real-time information about the file transfer and subprocesses such as unzipping, moving the images in the zip file to where they belong etc.

The additional information displayed in the file storing view is either limited to showing the progress of the file transfer as a percentage or then as much additional information is displayed as in the project list view.

When uploading images progress is shown as amount of process images. Uploading of images also automatically scales images to different sizes.

To automatically enhance the content of writings, various types of functional embeds may be used. They appear alongside writing when editing the such, just like other placeholders. They can be used to add list of subheading from the writing, a list of contributors, a live news section with subheadings, etc., without much effort. It is not guaranteed that these features are available before they can be considered to not be experimental features.

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.

From a content production perspective, the publishing application has been developed on a "big screen and rollerball computers with physical keyboard first" basis, but time is sometimes spent ensuring that tablets and laptops with a sufficiently high resolution and size could also be suitable devices. For browsers, it seem to be easy to achieve an equal level of functionality, so the assumption has been taken that functionality is good even on more exotic ones, provided that it has been verified with the most common browsers.

The publishing application functions well and equally on at least Edge, Firefox, Chrome and Safari.

In terms of user experience, a 32-inch monitor at 1440p resolution connected to a deskop computer seems like something of a sweet spot, but on the other hand, the Apple iPad Pro 12.9" is a device that fits all the views of the publishing interface just snugly enough. A separate physical keyboard is still recommended. Some functions may not be available on mobile devices if there is no separate keyboard connected, as the alternative would be to put more switches and buttons on the screen, which would in turn change the user experience. In some situations, the use of a wheel mouse is recommended, but not necessarily necessary.

The Samsung Galaxy Tab S7 having a 11-inch screen has different dimensions to the iPad, which means that not all kinds of elements can fit side by side in portrait mode, but on the other hand the publishing interface adapts quickly to landscape mode. Also, using a browser in fullscreen always gives a bit more space, which is useful when using a laptop such as the ASUS ZenBook in all its 14-inch.

It has been tried to use the publishing application on a Sony Xperia Z3 Compact Tablet, which has only moderate power and a screen size of only 8 inches. Technically the publishing service works normally on it, but the different parts of a view of the user interface have to be placed one above another in accordance with the principles of responsive user interface design, so there's quite a bit scrolling required.

As for controllers, the Samsung Stylus Pen is very handy and recommended for compatible devices, offering not only very good sensitivity and accuracy, but also the hover feature that Apple Pencil lacks.

The instructions may refer to the using of the Ctrl key (Windows) in certain situations, but the Meta key (Mac) can also be used to access those functionalities.

When using or buying a laptop computer, it is recommended that it should have arrow buttons that aren't kind of squeezed to fit in their place as otherwise one needs to consciously think about using them, motor movement slows down and and the flow of thought gets interrupted unnecessarily.

In the text editor menu, there is an option to translate the selected text into another language. 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. The language translation is configured to be used from Finnish to English and vice versa.

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.

In the "text editing" view, it is possible to make a few kinds of colour marking on the writing being edited, which can be marked e.g. on a copy of a writing and which can be copied to the clipboard at once if necessary.

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 real added value to the use of the publishing application and do not require payment from the first use.

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. Any additional information can be added to the text fields by first inserting a space and then entering e.g. information about pricing.

There are many choices to try and deploy. For a while at least, DeepL, Wordnik, ABBYY, Sceenshot Machine, Mapbox, Positionstack, Newsapi, Mediastack and others have been deployed.

Some external services are used only privately, such as translating text from one language to another, but others, such as map services, are also a bit problematic in a way, as the apikey of such services must be included in writings in which a map is used. If it is a public writing anyone can find that apikey. It is possible to overcome this problem by making additional adjustments in the user preferences of the map service, e.g. regarding the domain on which apikey can be used. Another consideration for the use of apikeys in public works is that their usage may be free only up to a certain limit. Some of these services provide real-time statistics on their use (e.g. Mapbox: Maps Loads for Web (loads), Static Tiles API (tile requests) and Temporary Geocoding API (requests).

Obtaining an SSL certificate for the publishing application instance is recommended when using these external services, as it is the policy of browsers that all cookies related to a web address are transferred to the server with each connection, meaning that with unsecured connections some data e.g. apikey can be captured by secretly monitoring the data transfer. Storing the apikey to a database instead of cookies allows them to be transferred less frequently from the server to the browser side, but still every now and then.

As the client of the publishing application will in any case have a CDN service account (required), the service from the same provider for storing and sharing files can also be enabled, which is fully optional. This requires the information "storage zone" and "storage apikey", which are created in the CDN service settings. The client of the publishing application can choose to share that information with those who have been set up a new user accounts in the admin settings of the publishing application. For more information on how to use CDN Storage, see the writing "Project files, CDN files and importing via SFTP".

There are many features and functionalities in the user interface of this publishing application that do not have any visual cues in the views where they are available, but they are all brought together in a "cheat sheet" view. It can be accessed by setting visible the button for it in the user settings, and which is then accessible immediately after logging in. User probably don't need that indefinitely, so there's no need to always be reminded of it.

As information in the "cheat sheets" there are brief explanations of the use of drag areas, mouse wheel, clicks and special keys, separate tools etc. Using them has a significant beneficial effect to the user experience.

Device-specific differences in operation are some of the reasons that justify changing the mode of some functionality. E.g. the Apple Pencil used with the iPad cannot perform hovering functions, because the hardware in them do not allow it. This is why when using the iPad, "placeholder quicklooks" should be turned off, so that when tapping a placeholder, nothing confusing would open up.

It may happen that a writing collection grows to having, say, hundreds of writings, in which case you may want to limit the maximum height of the tables listing the writings to reduce vertical scrolling. This setting also affects the image container tables as it tends to happen that they become numerous.

Experimental features include infinite viewport and PDF export. The former works great on Windows 11, for example, but less well on many mobile browsers. PDF export works well if A4 is used as the page size, but for other sizes the implementation is still under consideration.

Contrary to what the image implies, the possibility to set the "Show modifier key substitutes" mode is no longer available, as it would enhance the usability on a mobile device in the wrong way. Unless otherwise stated, some functions requiring special physical keys are only available on mobile devices when using a separate keyboard.

Sometimes a bug is so problematic on certain devices that it is better to turn something off. For some reason, many of these problems occur on iPad devices, but at least to a very limited extent. On the iPad, it is worth turning on the "Disable position changeability of writing particulars" option. It does nothing more than make it not possible to rearrange the order of the writing particulars in the text editing view, which is of little consequence because it doesn't anywhere else. Otherwise you couldn't tap writingparticular's caption to edit it.

Images placed in image catalogs can be selected to be converted to PNG file format (from JPEG). The choice of conversion options may become more varied once support for e.g. the WebP file format is added.

There are more of these user settings than the image suggests, such as "Tighter UI", which means using the space between visual elements in the UI views more compactly and reducing the size of fonts, among other things. For convenience, new writings can be chosen to be primarily "participating" or "non-participating", if there is a use for such a user settings. There are also some user-specific settings related to the usability of things in preparation.

The user might also be interested to know how much data transfer from the server and away from the CDN has taken place in the current billing cycle, and how much disk space is still available, so this information can optionally be kept visible in the project list view. Also, the number of blog posts per solution may be something one would like to see directly in the project managing view, so that option can also be enabled.

When there is suddenly need to restrict amount of the data transfer from the server (outbound traffic), it is possible to limit the maximum size of the images to be displayed. In that case, the maximum image width will be limited to 640 pixels, which is much less than the maximum size of 1600 pixels wide images. This mode of for trying to ensure that there would be no change in the readability of writings and that images could still be displayed, albeit in decreased quality.

This user-specific view is very prototypical and not just in its naming. It is intended to

a) Be used to let oneself to become aware about possible problems (Problems) that may occur, e.g. when transferring elements in a slightly incomplete way, e.g. from project to project, but forgetting to transfer something. Where possible, "one-click" fixes are available.

b) To confirm something that needs a little more clarification (Clarifications), such as the lengths (in terms of time) of solutions' caches and images that are in some image catalogs but aren't used anywhere. There is also a somewhat similar option in the "browse image catalogs" view, which filters image lists to show only those images that are not yet used anywhere. When one have a lot of pictures, things like that can get forgotten.

c) Let one get manually reminded (Reminders) about something that might need to be / should be checked periodically like e.g. to list writings that are marked as "preparing". It is possible that this functionality could end up somewhere else with a different implementation.

It was meant to make this screen be useful without need for a user to do too much clicking and thus have all the relevant information loaded at once. This may also mean that something is better utilized elsewhere. E.g. it is convenient to optionally list writings with a readyness status of "preparing" in the "project listing" view.

With all the accumulation of all kinds of ready-made content and potential use, it can be a little difficult to remember or decide what was still in progress or about to be taken up, despite all the naming and organising. In the case of images, the particularbrowsing view has already offered the possibility to list only those images that are not yet used anywhere, and for writings etc., it was possible to choose whether something was participating or not.

In addition to these options, there is also a 'in preparation' flag that can be set for image containers, collections of articles and adequates. In practice, the labels appear in a uniform way in the tables listing these on the left-hand side of the row of the table being labelled, which can be shown or removed by using the toggle buttons in the particularbrowsing, textediting and adequates views.

If a project has been marked as "preparing" in this way, there will be related links below the project image in view listing projects so that less navigating would be needed to get to a relevant view.

Separate writings' readyness statuses can be set to be either "preparing" or "later", if one wants to list either kind of them below the projects in the project list view. These are also shown for side projects. In the user settings, there is a choice of which kind of them, if either, is to be shown there. They will only be shown if a user is currently listing "Fresh" projects as the idea has been that those writings will be dealt with "in the near future at the latest". This is useful if a user has a large number of projects, which together have many writings, and one don't always want to have to remember which writings was meant to be dealt with.

Adequate sets might be used more often if there was a shorter distance to navigate to the adequate in them. For this purpose, there is a user setting similar to what is mentioned above, to list adequates that are marked as "Preparing state" in the project list view.

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 solutions 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 redirect link is set is exported, removed and then re-imported. Later there will be Usability checks view, where these kinds of checks are done automatically, among other things.

Redirection links work for all different types of works, provided that the target solution's settings explicitly allow redirect link targeting. Title, ingress, date, tags and mainimage are retrieved from referred writing as appropriate.

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 starting point was originally that "of course a writing has to have a name", but does it have to? Surely something must be shown when e.g. listing such on the front page of a solution, so what would it be if not the name of writings?

There are use cases where it is impractical to try to come up with a name for an writing, so the decision was made to use the first 300 characters of the first text element of writing's content, whether it be a subheading, text paragraph or something else, instead of the name of the writing. This substitute text is used, e.g. in tables listing writings and on the front page of a published solution. On the writing pages of a published solution, names of writings are simply omitted.

In the text editing view additional information about e.g. a link or video id is retrieved using external service. The process begins, when the text field where to a link or relevant id in the link is entered gets defocused. This information is then retrieved using an external service or application programming interface (API), e.g. the service provided by the YouTube that outputs information in oEmbed format. In the case of an online video, query returns structured (i.e. machine-readable) information, e.g. on the length, author and height in pixels. Some of this information is not visible to the user at any point, but is used in other ways.

In the adequates view there's a text area for adding links, to which one can enter or drag'n'drop one of more links and then begin automatic processing of them.

Each separate view 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).

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.

In the Text editing view, there is a separate menu option to make the text editor the focus of attention without trying to imitate the so-called "quiet editing mode" offered by some other word processors or text editors, which would effectively just mean switching to fullscreen mode and hiding everything else from view except the text being edited. Not even from a thought process point of view it makes sense to hide almost all visual elements from view.

In the user settings, there is a Tighter UI option, which slightly reduces the size of almost all fonts in the user interface of a regular user and reduces the space taken up by some visual elements. This is useful e.g. on laptops that don't have a very large screen. On the iPad Pro and many other tablets, the Tighter UI setting may feel appropriate whether is enabled or not.

In the user settings there's enablable option for "studyind mode", which is only applicable in the text editing view. This adds a toggle button named "Studying mode" to that view, which, when turned on, imposes some editing restrictions on the writings, and the functionality of the table listing the writings becomes such that one can mark which writings are e.g. recommended to be studied next and which perhaps later. These markings are entirely visual, which means that they don't have exact defination. They can be set by Ctrl-clicking on the writing names.

These to-study markings are saved with the writings in the solution so that they are also stored in the backup of the relavant project and thus, one could prepare something to study for other and give them a copy of the backup file, which they could import to their instance of the publishing application. By turning off the study mode, the text editing view is restored to normal. With study mode enabled, all those markings can be cleared from writings of a writing collection by clicking on "Clear study markings".