Road Map Not Fit For Purpose

Good to see a new version on the way (8.7.14.0) and some of the features are excellent.

Any chance that the Road Map can be brought into the 21st century? ;->

There have been several promises of RM updates (including around the previous release) and none have materialised. It is hopelessly out of date and pretty-much useless.

Conversely, if updated it would be really useful.

Kind regards,

Paul
1 person has
this question
+1
Reply
  • Paul,

    We have developed an internal content publishing system to produce content for https://codeontime.com and https://my.codeontime.com. The new roadmap and many other related documents are being prepared with it. The content will become available in both websites soon - this work consumes the majority of our development effort right now.

    The publishing system was built as add-on for apps created with Code On Time. It makes possible creating content in Office 365, Google Drive, or any text editor capable of producing documents in open document format (Oasis).

    The core of the new content publishing system is based on CMS feature of apps created with Code On Time. Any document with "*.odt" extension can be accessed by typing the path and the name of the document. For example, the introduction to Offline Sync will render an HTML page at docs/offline-sync/intro if the introduction is stored in Site Content as docs/offline-sync/intro.odt and content type is set to application/vnd.oasis.opendocument.text .

    Publishing component of Content Add-On reads *.odt files and converts them to internal JSON format. The json document is rendered as HTML page. Any images stored in *.odt files are accessible as child resources of parent document. For example, if there is an illustration in the Offline Sync intro, then it will be available as docs/offline-sync/intro/image1.png. Sample code found in *.odt files is rendered as code-mirror snippets.

    Synchronization component of Content Add-On performs synchronization of content with Office 365 or Google Drive. Initial release will support Google Drive with Office 365 to follow.This is how it works for our own content:

    1) We have a root content folder on one of the Shared drives.The folder structure represents the content of the app. Documents in folders with special names (blog, docs, news) will render with special user interface elements (sidebars, table of contents, etc).
    2) App https;//my.codeontime.com has a registration record for Google Drive API (the new feature)
    3) App https://my.codeontime.com has a registration record for Content Add-on. It points to the root folder (1) and synchronization API (2).
    4) Content synchronization component is invoked periodically to read changes to the root folder. It transfers documents from the drive to the Site Content of https://my.codeontime.com. The documents are retrieved from Google Drive in open document format. Changes to the file names and folders in Google Drive are automatically synchronized with Site Content in https://my.codeontime.com

    Google Drive is our new content repository. App https://my.codeontime.com is our new publishing system.

    Any document prepared in Google Drive or Office 365 becomes a part of the site content of an app created with Code On Time.


    The app will need to enable Content Add-on and have it configured to access the folder in the cloud document storage. If you create a Microsoft word document in the corresponding folder of the drive then it will become available in the site content of the app.

    Roadmap, blog entries, and other documents will be available directly at https://my.codeontime.com. Our current public website https://codeontime.com will mirror the same content.

    Code On Time v9 integrates with https://my.codeontime.com/docs. The configuration hierarchy maps directly to this site.

    The description of the new features reads as follows:

    Content Maker Add-On

    Make your app an engaging and friendly place for end users with Content Maker. Add content pages, blog posts, newsletters, and documentation with interactive public and private comments from application users.

    Create and manage content in Google Drive or Microsoft Office 365. Content Maker will automatically download and store new content to Content Management System (CMS) of the app. CMS integrates and renders content as information pages, marketing materials, blog posts, documentation articles, public forum discussions, and support requests.

    Users can comment on the content publicly and privately. Public comments are grouped in the section of the site called “forum”. Private comments are numbered and segregated in the “support” section.

    Users can contribute their own content enabling knowledge crowd-sourcing and sharing.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Thanks for this very comprehensive response. I look forward to the new CMS features and the RoadMap and Document improvements.

    Kind regards,

    Paul
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated