[email protected]

The article describes the basic concepts and capability of the Cloudburo Publishing Bot in a narrative way. It will allow you to get a good overview what is offered by the bot.

An Online Content site for your community

The Cloudburo Publishing Bot Platform is managing content sites of multiple users.

A Cloudburo content site consists of multiple articles which were transformed from Evernote notes stored in dedicated Evernote notebooks.

A content site is offering the articles in a responsive mobile friendly HTML format to the online audience which provides in an optimized reading experience on any device size.

A content site is represented by a unique user chosen site identifier (SID) within the Cloudburo Publishing Bot Platform. You may manage multiple sites from one Evernote account.

By default the content side of a user is reachable via https://<yourSiteId>.curation.space. You may choose to use your own domain.

A blog article may be originated from a note which was placed in one of two Evernote transfer notebooks.

Notes in the transfer notebooks will be periodically fetched by your Cloudburo Publishing Bot, converted to articles and published on the users content site.

After the note is published it will be moved to the Evernote Archive Notebook with the name <yourSiteId-Z-Archiv>. The note will be marked with the tag clb-processed.

This feature will allow you to speed up article publishing on news site, refer to the workflow description for details

Evernote notes are the foundation of your published articles

The Evernote note creation date as well as the note title must be treated as immutable after the initial article generation step. These two attributes are part of the article URL and will uniquely identify the article in your content site.

Changing these two fields will result in a new article entry. Otherwise an change on a processed note and moving it back into the Transfer Notebook will result in an updated article.

A generated article can be removed from the content site, by attaching the clb-delete tag and move it to one of the Transfer Notebooks. The note will be fetched and the corresponding article will be removed from the content site. The note itself will be moved to the Archive Notebook and the clb-delete tag will be unattached.

A note may have dedicated tags attached with a prefix of “<site identifier>-<category>”. The tags will be used to categorize the articles on the content site. The content site will offer a category menu which lists all used categories in oder to get a list of articles by category entty.

Fine tune the publishing periodicity according to your needs

should be published on the content site.

If the publish scheduler triggers a generation event, the above described transfer notebooks will be checked for available notes. If available the scheduler will fetch the oldest note (creation date) and generate the corresponding content site article.

For notes with the tag clb-processed or clb-delete attached the scheduler doesn’t apply - i.e. they will be updated or deleted in the next publishing cycle.

Embed various kind of rich content artifacts

Control content site menu and footer, as well as social media icon links

Additional Header- as well as Footer menus, as well as optionally a customized entry (index) page, may be defined in dedicated Evernote notes. Socia media icons to link to your social media sites are available.

A rich set of integration options exists to further customize and extend your content site