The project managing view contains navigation links/buttons to all views/modal windows relevant to the project, from the beginning of writing to fine-tuning the final work, from backup functionality to selecting image catalogs, and from asset management to search functions. Yhdestä projektista voi johtaa useita, yhteisesti kuvakatalogeja käyttäviä teoksia kuten esim. erikielisiä sellaisia.

After logging in, the Fresh section of the project list always opens, listing the projects that the user has classified as current or such. From the same view, you can access the Settings modal window, where you can make user-specific settings from image catalog to the configuration of external services. The function for logging out is placed exclusively in this project list view. The sorting labels fresh, past and forgotten can be taken to mean that wherever the project is placed, the word "forgotten" does not have to mean that something has now been definitively left in a position where it is no longer used and that it may not even be important and, who knows, even if one wants to forget it. Later on, it may be promoted back to the fresh level, e.g. if one feels like it, or left at the past level for a while, in case there is time for further contemplating or preparation at some point. "In preparation" markings are shown per project, if there are any. Projects of other users for which the user has editing rights are displayed in a slightly different style.

Below project's cover page, there are links with amounts to writing collections, image containers and adequates marked as "preparing", if any of them has such marking. List of writings having readyness status of "preparing" or "later", linked to the text editing view, can optionally be shown under the project listing panel. There's a user setting for this. Relative importance of those writings in the list can be indicated by toggling using Ctrl-clicking. Adequates can also be displayed clickably in this view if they are set to be in "preparing state". Ctrl-clicking them toggles the visibility of the associated adequate set's name.

Dropping a backup of a project into this view (to the panel listing projects) will cause a new project to be created based on the backup. A backup file can contain more than one project. The limit for the filesize is 500 MB, beyond which one can use importing via SFTP as explained in the writing "Project files, CDN files and import via SFTP".

The basic elements of a writing are the textual parts of it (some of which are fully optional) and the "particulars" that can be included to the writing (are initially just attached to it without being placed in a specific position). There are many more types of these attachable particulars than just images. It is also possible to include another writing in an writing. In addition to the text formatting functions, the text editor menus offer a variety of helpers etc.

More specific types of writings include redirectlink, which allows using of writing in other solution. Choice "Several with images" is not an actual writing type and instead it creates new writings one per an images based on image particulars that are referred on the clipboard. Multiple writings can be created using the "Selected to new writings" menu item in editor's Tools menu, which creates one new writing per line selected in the editor. These text lines will become the names of the new writings. The creation of several new writings with one image attached can be initiated by copying the images selected in the imageassorting view to the clipboard and then pressing "Several with images" button.

If one had simply created a project, made a collection of writings and saved a few writings to it, without any fine-tuning of the writings, you would already almost have a table of contents for the work. All that would still be needed is to select which collections of writings to include in the work from the fine-tune writings view. In the work-specific adjustments view, you could put a cover image for the work, which would be shown by default above the table of contents.

If some fine-tuning had already been done e.g. on the typeface and the stylization of the borders of the included images, the effects of the adjustments would be immediately visible on the writing page of a work. All the final works have direct links to the collections and writings, both in the table of contents and elsewhere. The images displayed in the modal window can be browsed using the arrow keys on the keyboard or the previous/next icons that are displayed, if so choosen in the user settings. The images browsable in the modal window include all the images of the writing, even if they are in a different pictureshow.The images in the writings can be viewed in larger size.

From a productivity point of view, it would not necessarily be appropriate for a piece of writing to always look exactly as the end result appears, as the thinking process is different, when attention to styling takes up a slice of the thinking time. This is why the fine-tuning of the essence of the writing and the stylization of the elements included in the writing are done in a separate view. Saves time and mouse movements, also. The final appearance of the writing can be viewed in the preview panel or by opening the part of the work where the writing is visible in another tab or browser window.

In the writing fine-tuning view, there is a wide range of quick adjustments to try out and choose from. These include the font of the text in the body of a writing, positioning of ingress and style of the border optionally surrounding images. Other effective adjustments include e.g. pushing the images of a writing slightly over the text edges or edges. To apply adjustments to several writings at once, it is sufficient to first make the appropriate adjustments to one writing and copy them to the other writings selected in the mass editing view.

Some of these adjustments are probably less frequently needed, but useful to have available when you need them. One such is the adjustment that makes line breaks for reference and/or meta text (not shown in the picture) be done at any point. Without using it e.g. long web addresses might extend past the boundaries.

Quick adjustments affecting the whole work also have their uses, for example to make the content of the front page of the work more preparatory (more on this elsewhere) and to make small adjustments from language selection to caching and from setting the publicity to setting page width. With a single adjustment a work started as a blog can be transformed into a work having a hierarchial table of contents like in a book. For some works, it may be useful to set the scalability of the images presented in small size so that they do not end up being too small (will get set to 100% width on a smartphone, for example). The setting also affects all the other particular types such as videos, maps, etc. It may sometimes be user-friendly for the reader to enable icons to indicate, for example, the inclusion of videos and image collages in some writings. There are also symbols for redirectlink writings to make them stand out where they are listed. Caching per work is very useful in avoiding server load (even a few seconds of caching is very useful).

From time to time more solution spesific settings become available. Some others include the "Page menu", which allows each page of a work to display a menu that is largely automatically generated from collections of writings available in the public work, from presentatation pages or from blog layouts. Any special pages are also put to these menus or, if no menus are used, at the beginning and end of the rest of e.g. table of contents. If special pages should be omitted from page menu its name need to start with character ":".

An automatically generated specialpage containing a comprehensive list of writings in the work, ordered by availability date, can be made to appear in a page menu or a plainstructure-type front page by enabling the option selectable from the drop-down list.

Links showing writings of a writing collection can be made to function in four different ways: to show the full contents of writings, to show writings as a list with some essential information (nimi, ingress, tags and main image), to show only the name of the writing collection instead of a clickable link or to show a playlist.

The previous and next links at the bottom of a writing page can be let to be links with the writing names, hide them completely or use just bland link names "previous" and "next".

"Allowed tags" means tags separated by commas, which determine which of tags added to an writing (a separate text field) are taken into account in contexts where tags can be used to do something. These tags can be added in few different views by selecting from the dropdown list.

The possibility to generate a printable version by pressing a single button, as explained in more detail in the writing "Exporting solutions", has only one adjustment to control how it behaves, meaning the the font size multiplier. Choosing option "1.00" works appropriately when printing at A4 size, affecting all text sizes in a writing (headings, captions, etc.). This does not affect redirectlink writings, which are affected by the same setting on target solutions.

One can choose to display the cover image of a work on all pages or on the front page using the solution-specific setting, but it is also also possible to select whether the image should be displayed in a larger size or not at all, and how title of a work should be displayed or whether to not show it at all by "tweaking" special page "Opening section"'s name. The same tweaks also affect the appearance of the PDF version of the solution, if one decides there's need for such.

In practice, if the name of a "Opening section" special page starts with:

1. "_" no cover image at all
2. "#" cover image in a rather huge size
3. ":" cover image without solution's name
4. "_:" no cover image, no solution's name
5. "#:" cover image in a rather huge size, but without solution's name.

Those could have been implemented with buttons, but maybe there are enough of them already?

For other specialpages it is possible to have:

(when using pagemenu)

1. specialpage removed from the page menu and include specialpage's name and its contents to the front page by adding ":" at the beginning of the name
2. name of the specialpage removed from its own page and from the front page by adding "#" at the beginning of the name
3. both of the above by adding ":#" at the beginning of the name
4. name and content of the specialpage removed from the front page by adding "_" after the above

(when not using page memu and the content listing type is "plain structure")

1. editing the name of the specialpage has no effect

(when not using page menu and the content listing type is other than "plain structure".)

1. name and content of the specialpage removed from the front page by adding ":" at the beginning of the name
2. name of the specialpage removed from its own page and from the front page by adding "#" at the beginning of the name
3. both of the above by adding ":#" at the beginning of the name
4. name and content of the specialpage removed from the front page by adding "_" after the above

On the page listing user's public solutions, the cover image of a solution can be omitted by selecting relevant setting. It will then be replaced by a grey rectangular area. The cover images of published solutions of a user can be made to appear larger by enabled the relevant mode in the user settings.

In order for solutions to appear in a same group on the page listing public solutions, they must be given the same group name. If none of the user's public solutions have a group name, the space occupied by the group name will be omitted from the page listing public solutions. The solution can also be excluded from the list of solution made available to the public.

Some settings like "Dates in writings' metainfo" may not do anything as such, and for that one also need to adjust the meta info setting in the "writing fine-tuning" view so that the meta info of a writing actually appears anywhere. Without these settings, date of a writing would not appear at all, but with them it can be placed near the titles or at the end of writings.

Every solution can be put to maintenance mode, which is manifested to users as a message that replaces everything else while maintenance mode is in effect. Maintance mode causes this message to be shown, when a reader tries to access a published work: "Solution has been put in to maintenance mode, which is a different choice from making it private. Someone probably just wants use time and care to perfect the solution without revealing anything too soon. If one had to guess, changes take an hour to finalize, but who knows."

At the side of a writing or between paragraphs of text, you can place an area to provide additional information, a summary etc., which is called a "sidebar" in the publishing "scene", but in this service it has already become known as a sidebar. It is possible that this may be confused with a slightly later feature, which has been provisionally named "sideshow" and which is basically a sidebar at the side of the front page of a work, where basically anything can be placed (statistics, advertisements etc.). Here are a few available sidebar border style adjustments to make it stand out from the rest of the text.

You can use images as content in these writings, but not pictureshows, nor anything embeddable. Due to memory load, it might be advisable to initially keep them in the same writing collection as the writings they are part of. In the fine-tuning writings view, hovering a pointer over a writing that uses one of these will cause the included writing to indicate its inclusion visually if they are in the same writing collection. All kinds of writings can be freely moved within the project boundaries from one writing collection to another without worrying about breaking integrity.

If the purpose is to display a few separately readable text paragraphs in a less space-consuming way than normal text layout, one could use "tabbed text," which is an embeddable type particular.

Editing a writing using slicing (sliced text editing)

It is often more comfortable to write when there is more text from the same writing visible, as this reduces memory load. In the sliced text editing view a writing is automatically split into several parts at the points where the subtitle is either bold, type of "Header 1" or type of "Header 2". Other two choices are to use empty rows or rows having only two minus characters for points to split at (will be added back to a writing at the time of saving).

Unlike in the picture, such a visual slicing can be done from primary and secondary points. This can be useful e.g. at the phase when one is just preparing to write something and want to keep a large amount of already written text quickly and visually presented. Also useful when there are lots of subtitles like e.g. in a writing that acts as a link directory. There are a few buttons to adjust the height and width of these slices.

If images or other attachments have been attached to the writing, they remain unchanged on save, even if they are not displayed to indicate that they are attached to it. Just a reminder: attaching differs from including. The placeholders stay where they were if they aren't removed while editing text.

If the text content is in a plaintext or a Word file, it can dropped to a "slice" at the point where the cursor is at that moment. The order of these "slices" can be changed manually by first selecting the "moving slices" mode and then moving them as desired. The "slices" can be reversed by using one of the dedicated buttons, which is useful, for example, if user have written things in chronological order but want them in the reversed order.

Editing all the writings of a writing collection (lots of text editing)

Another alternative way of editing text is to use the "lots of text editing" view. It allows to glanze writing collection's writings with less effort and there are a few buttons to adjust the height of these slices. In this view there is a "Show writing particulars (images)" button, which makes the catalog images in writings appear as thumbnails at the end of the writings. Other particulars are not shown, but they are kept in writings even when saving and the quicklook functionality is usable (hovering the pointer over a placeholder). This is one of the views that has a "Stickyness" switch, which allows certain part of the view to remain roughly in its place when the page is scrolled vertically.

Not all writings displayed in this view are loaded at once, but as with the lazy loading technique used for images, writings are loaded and when it is time for them to appear. By using the "Stickyness" button to keep the left-hand side of the view in place while scrolling, one can easily edit or write hundreds of writings.

In both of these views, instead of listing writing collection's writings, they can be listed by writing finding group description for which links can be accessed via the search view.

Editing writings of a whole project (kanbanish text editing)

At one point, a third-party idea management application changed its visual appearance in such a way that it no longer felt so enjoyable to use it, so it was decided to try and see if the publishing application could also have a Kanban-type view. This means that ideas can be moved from column to column (e.g. backlog, ongoing and completed ones). Tags can be used to add something to classify these ideas. In practice, a column contains writings from a writing collection, but as in the lots of text editing view, they are loaded "lazily" (just before when should appear). This view is not specifically intended for managing intentions and ideas, but has simply been given such name because of its similarity. Writings are moved from one collection to another as soon as the drag'n'drop ends. The order of writings of a writing collection can be based on availability time or position, which is selected in the fine-tuning view for writings.

Although one can attach image particulars to an open writing by drag'n'dropping them from the "browse particulars" view, the kind of "compactness" offered by the view combining the "browse particulars" and "text editing" views may be preferable, since glancing between two different views requires a subtle mental reorientation. When same time is spent in the same view

When all the time is spent in the same view, no such "extra fumbling" is needed. Editing writing works exactly the same as in the actual "text editing" view, with the difference that images can be added only by drag'n'dropping from the list on the left. As in the "browse particulars" view, images can be viewed in large size (by clicking on the image) and recropped in the modal window that opens (by Ctrl-clicking on the image).

If there are so many images that you can't even see the writingparticulars list when you look at the bottom ones, it is also possible attach images from the catalogue by clicking on the image while holding down the Alt key. Among switches there is one named Sticky, which would prevent other columns of the view expect the one showing image catalog's images from scrolling. As in the particular browsing view in this one too it is possible to use one switches used for filtering what images to show. The other one of those is the one that shows only images that aren't used anywhere and the other one shows images that are marked as being "usable". Heights of very long images can be limited by using the switch named "Limited heights". Description and source information of images can also be hidden.

The front page of a work is a kind of introduction or content listing about what the work contains, and when you change the type of content list, it is this front page that changes most in the work. There are other alternatives to the book-like table of contents, including the "presentation page", which can contain sets of writings arranged in different ways, and a "blog-like", which presumably means a blog-like presentation, where the layout can be adjusted in some way.

In the case of presentation page writings, a "mainimage" for a writing can be displayed (referred to as a "feature image" in some other services/applications). The mainimage must (optionally) be set for each writing separately in the view where the appearance of the writings is fine-tuned and where, for example, images can be included to the writings. A mainimage is also (optionally) used on a writing page as a header image or then just on a introduction pages alone.

Presentation page..

On the works' front page, the "presentation page" could look like this. It shows several different writing sets made from the same collection of writings, in some cases with the writings automatically placed and in others the writings are placed manually. Published work can use multiple layouts, if enabling setting "Page menu" is selected in solution's adjustments. Writing sets are non-participating when added, so that they could be added to presentation page that is already published without any public changes.

(Actually.. you'd better take a look at these: example: More expressive front page, example: Research news (online magazine) and example: multiple presentation pages.

There are about seven writing sets that require manual placement and about seven writing sets for which it is sufficient to just select a writing collection. There are about twenty styling and adjusting options to choose from (image from earlier version).

At the top of the view is a menu from which to select presentation pages created for the project. At the bottom, they are listed in such a way that you can change their order, change their names, change their participating setting and get an address that you can refer to, e.g. in writings.

Presentable pages containing one of more writing sets can be saved for later use. Writing sets can be ordered by simple dragging them using the mouse or other pointing device. Redirect links work in writing sets, too. When a new presentation page is created, a random name is generated for it. The presentation page can be duplicated as well as the blog appearances.

Blog-like..

The writings in a blog-like work may be spread across several collections of writings, as the date of the writings determines the order in which they appear to the reader. A work may also contain collections of writings that are not even visible to the reader, but are in the project just for some reason.

For visibility on the presentation page, writings have two changeable dates, one of which is the date that determines the order of writings (publication date) and the other is displayed in the title of a writing (optional update date).

This is what a blog-like work might look like with standard styling.

(Actually.. you'd better take a look at: example: Blogging about something)

There are almost twenty buttons for adjusting the appearance (image from earlier version), which affect margins, image sizes, text ribbon layouts, etc. You can save as many element layouts as you feel you might need.

This is what a blog-like work might look like with a few quick tweaks. The visibility and placement of the writing-specific tags is one of the controls.

Out of ink..

If there are a lot of writings in a work, just listing their names would take up a lot of screen space, making it less easy for the reader to grasp the scope of the work, or perhaps all the writings are in some way equally valuable/important, so why list all the names separately if all of one or more of the writings are intended to be read?

See sooner..

This, in all its simplicity, allows the reader to get straight to the point: the writings of all the collections of writings in the work are displayed below, separated by the name of the collection of writings, as they would appear if read separately.

[no image, might be needed to mention]

Any solution that has been prepared for online reading can be made into a PDF version with a single click of relevant button. The resulting PDF will contain a separate cover page, all collections of writings in their own parts with all printable contents. Page numbers in the footers with section information and before/after appecialpages are included. Images will be as well positioned as on the web, font choices are exactly right and otherwise results are generally just fine. Currently it is preferred to use content list type of "plain structure" as others like "presentation page" and blog-like would give unexpected results. Instead of the whole solutions, one can limit the use of the function to a selected writing collection.

This has been done in a completely different way to the previous attempt, where a TeX file was first generated, containing both styling and content, and then a PDF file was generated from it. Instead, the external service generates the PDF file from the same ingredients that browsers use to generate web pages, i.e. HTML code, CSS styling and JavaScript code. An important addition is the use of CSS3 Paged Media:

"CSS module specifies how pages are generated and laid out to hold fragmented content in a paged presentation. It adds functionality for controlling page margins, page size and orientation, and headers and footers, and extends generated content to enable page numbering and running headers / footers." (CSS Paged Media Module Level 3. W3C Working Draft, 18 October 2018.)

Many browsers have not implemented this standard and that is why printing directly from the browser does not provide optimal results as such, when the purpose is to include page numbering etc. E.g. the Firefox browser does not make much use of CSS Paged Media (since last tested), but Edge and Chrome do. However, a problem with using them is that they either include extra information like the date in the header and footer, or the header and footer contents have to be completely empty (the printing settings only have an either/or option). There is a button for making a printable version of the whole solution and icons for doing the same just for a writing collection.

Actually, as the external service that is supposed to be used for generating PDF files requires a fee to be paid, process is decreased by a one phase so that a user is served with a downloadable HTML file that contains all the mentioned "ingredients" and content. User can then use a browser to print it, if the browser has enough support for the CSS3 Paged Media.

There is only one adjustment for this in the adjustments of a solution, the font size multiplier. Choosing option "1.00" works appropriately when printing at A4 size, affecting all text sizes in a writing (headings, captions, etc.). This does not affect redirectlink writings, which are affected by the same setting on target solutions.

Links to the writing collections, which can be in the menu, writing sets, table of contents, etc., can be set to be in a form that causes the publishing application to display the writing in the writing collection as a playlist. The layout is then familiar to many, where a fully shown writing takes up most of the space, and to the side (or below) are selectable writings of the relevant writing collection, with writings' mainimages and other relevant information. When enabled in the solution-specific settings, playlist-mode becomes available largely everywhere else except in writing sets, wherein such decisions are made separately. Some might say that "playlist" might not be the most successful designation, since it isn't necessary to limit to e.g. videos as writings can have anything that writings can have.

This view that needs a separate login account is not intended to be used very often. Usually, only at the very beginning of becoming publishing application customer, this view need to be accessed briefly so that CDN address can be set. Without it being set all the public pages' footer contain a message that mentions about missing CDN address.

It provides, among other things, the possibility to create new users and the editing of user-specific constraints. Some areas of the managing view contain just information e.g. "how much outbound transfer bandwidth has been used in the current billing cycle".

If a project meant to be transferred to another user has adequate sets attached with it, these associations will be removed. However, adequateate sets can be transferred from one user to another separately.

The regularities for user-to-user transfers are:

• a project can be transferred from one user to another if the project catalogs are only used by that project, otherwise the transfer attempt is aborted from the start
• a catalogue can be transferred from one user to another if the catalogue is not used by any project
• a solution can be transferred from one project to another if they are from the same user
• an adequate set can be transferred from one user to another, but the adequate set is detached from all projects

These transfers typically require a relevant id code (e.g. projectid) and the username of the user to whom something is meant to be transferred. The text fields for these are helpful in that after entering an id or username and clicking outside text fields, additional information about e.g. target user is retrieved for display.

Occasionally, on rare occasions, one might choose from the normal user accounts the one that will become the main user, i.e. the one whose public solkutions will be listed when going to the domain's index page. Otherwise, a user listing would be displayed, from which one could select to see the user-specific listing of published solutions.

If necessary (highly unlikely), there's a simple button that can be used to clear the contents of long-lived caches that form in the central memories of the servers in use. Such caches include a partial copy of the database contents with relations, as it is much faster to retrieve information from them than from the database, as the database is located on a slower SSD.

It is possible to choose to reduce the visible size of the listed public solutions, when viewed on a smallish browser window widths so that more of them can be displayed at once, or to place them underneath each other and to not hide the descriptive text os solutions.