2 in 1

Technology behind is web technology.  Because of this, KHub+ is designed with

Two Systems in One Installation

Front End = public facing website
Back End = privacy protected intranet for internal only

Excellent fit for startup companies or individual consultants who do not have a website.

Two Systems

 

Website

Front End

Public Facing

 

 

 

Intranet

Back End

internal Access Only

 

 

Front End website is built with pubPages.  All pubPages are visible in public by default.  Same as the inPages, it comes with an extremely flexible Paragraph structures like building LEGO.  No coding is needed.

This is important for content creation because

  • novice users without the necessary technical background can build a professional website after a minimal training
  • users can make changes as they wish without relying on technical people
  • yet, technical users still find it productive because coding is very time-consuming.
  • stay focused on content without worrying technology

In a team or an organization, this means cost saving, effectiveness and productivity.

 

Back End intranet is built with inPages.  All inPages are private by default unless specifically configured as public by user for special reasons but can be switched back to private later.  Same as the pubPages, it comes with an extremely flexible Paragraph structures like building LEGO.  Again, no coding is needed.

Intranet is where to start for organizational knowledge management.  KHub+ is designed to facilitate KM.  It only make sense when users (content creators) can contribute the content they consider important without the need to learn the technicals first, or ask help from the technicals.

 

Site-in-Site Architecture

Sites within Intranet

= Sub-Intranets

A comprehensive yet logical architecture:

Website Intranet
  Common Area Restricted Area
open to public accessible by internal users but not to public accessible only to the individual group you belong
 

Examples:

  • internal news, notices & announcements
  • rules & regulations
  • organization activities
  • forms & submissions
  • rooms & equipment booking
  • onboarding & general training
Dept Teams / Proj Comm more ...

e.g.

  • sales
  • marketing
  • HR
  • Finance
  • IT
  • R&D

e.g.

Teams

  • shareholders
  • senior management
  • product announcement

Projects

  • mid or long-term projects
  • knowledge & experience collection

Communities of

  • practice
  • interests

Addressing

  • future requirements
  • changes
  • discoveries

 
   

Sub-Intranet (Site-in-Site Architecture)

For individual group:

  • Owns their own sub-intranet: design, management, content, updates
  • Fulfill their own needs, design to fit into their own workflow, behaviors and habits for productivity
  • Maintain their own knowledge-base and training
  • No need to jump around for works
   

FastAccess Toolbox (Productivity Toolbox)

Each individual group owns a FastAccess Toolbox, slide-out access in 1 click:

  • Owns their own FastAccess Toolbox: design, management, content, updates
  • Fit to own needs & workflow

Easy Content Creation

No technical background required

Tech for the non-technicals

Only 2 types of content pages, making it absolutely simple for content creators:

inPage pubPage

Intranet Pages

private by default

Public Pages

public by default
The inPage is mainly for the intranet.  It is only visible and accessible by the intranet login users (private).  By default, all inPages are private, unless it is purposely made public, at the discretion and control of the author. The pubPages is mainly for the website.  It is public and visible and accessible by all readers without the need to login.  By default, all pubPages are public, unless otherwise selectively configured as private by the author to facilitate the preparation process.
  The structures of inPage and pubPage are pretty much the same, except a few additional features to facilitate website design for its appearance, such as banners.

NO CODING

No technical background required