Welcome to Hub Nexus

Hub Nexus is a cloud platform for publicly funded and versioned content publishing and development, allowing authors and contributors to store and manage their content, through open collaboration from public edit requests.

Another way of saying, Hub Nexus is the content creating and developing platform with Typora-like editor, Git-like version control, and Patreon-like donation.

This node introduces Hub Nexus features and functions, and demonstrates examples to share in the node sections

Hub Nexus

Hub Nexus is a place to share anything where each created node as the hub connects other nodes forming nexus of nodes to share certain or collections of information

Node

A piece of information you'd like to share, e.g. gossip, feedback, thoughts, topics, Q&As, inspirations, creativities, academic fields, encyclopedias, books, image galleries, podcasts, songs, vlogs, or collections.

A node

• is unique: node title is unique
• is versioned: each version is an approved, published, public edit everyone could make a request
• has sections: relates to a nexus of information collections, and each collections could be related, categories, a topic, or etc.

Section

When a node connects with other nodes, it forms a section.

A section is a collection of information, and it must belongs to an edit. Whether it belongs to current version of node, depends on the associated edit to correspond to the latest version of node.

A section is considered outdated when an edit is completed, i.e. published, abandoned, or reverted, and its content is not reflected on current version of node.

Due to each node is independent and versioned, node connections in a section is uni-direction. For example, when node A creates a section A which connects node A, node B, node B needs to explicitly create another section B if node B also wants to connect both.

Edit

Node versions consists of approved and published edits. And everyone could submit an edit request.

When an edit is created, it is in draft mode. The draft could be saved and continued later.

Once the draft completed and moved to review stage providing a diff view against previous node version, the reviewers, the node quorum, should then reach a consensus, determined by the voting count threshold. Each vote status is one of approved, disapproved, requested for change, or not voted.

The person who made the edit request, could go back to draft mode or wait for the final consensus to make actions, i.e. publish, back to draft, or abandon

When the node get versions updated while an edit is in draft or review, a banner would display to notify edit participants that the edit might be outdated. The drafter, the person who made the edit request should manually pull and merge with the latest version of node.

Node Quorum

A node quorum, or node maintainers, consists of main author, and invited contributors. We could invite both internal and external users to help contributing the node via invitation emails.

Besides making edit requests to improve node content, node quorum also have a duty to review, and vote which current open edit requests could be for node next version.

Node author has the ability to

• transfer ownership of a node to others, either internal or external via invitations
• become a contributor to relieve the responsibility of the author, but still keeps contributing to the node. The node author position automatically becomes up for grabs
• make self position up for grabs to let anyone have a chance to become the node author
• invite internal and external users to help contributing the node via invitations
• remove any invitations, or contributors as the author's own discretion
• vote on node open edits
• receive greater payouts from node supporters donations

Node author has the ability to

• invite internal and external users to help contributing the node via invitations
• remove any invitations as the contributor's own discretion
• leave to relieve the responsibility of the contributor
• vote on node open edits
• receive payouts from node supporters donations

Viewer Actions

Viewer of the node, could like, share, watch Later, favorite or follow on the node, or its sections

Viewer could also support the node financially, with an arbitrary amount and a selected intervals, i.e. one time, daily, weekly, monthly, or yearly. The invoice(s) would be finalized depending on the chosen interval. A payout among node quorum would happen after each invoice is finalized.

Hub Nexus doesn't store payment sensitive information. The entire payment process is handled by Stripe. It is optional to onboard. it is, however required, if viewer wants to support the node financially, or node quorum wants to receive the support.