A Portfolio of A Self-Sufficient Web

To make the web self-sufficient is to help each human own both their macro and micro content. This total content ownership requires a shift off today's web era.

Today's era, web 2.0, encourages you to go write at different sites because that's where the services are. Instead, you write at one site, your site (web 1.0), and let the services come to you (hello web 1.0++). This content shift requires a shared web workflow.

Yet, we can't afford to empower each simple human with abstract web workflow. But, we can democratize the web workflow to meet the simple human expectation.

Vision
A self-sufficient web
Mission
To democratize the web workflow
Team
1 stubborn human
Audience
5bn+ simple humans

Programs & Projects

This portfolio of programs and projects is a work in progress. Execution takes a bottom-up approach. It starts with the Guiding Resources, the Web System, then the Domain Registrar.

  1. Project Domain Registrar initiates the vision with domain name management for an owned web presence. Then, kickstart the mission with a parking page powered by the web system. And, eases the vision with a Single Sign-On service to access private services.

  2. Program Web System fulfills the mission with a Cloud GUI Code Editor to manage content and use services. The editor contains a markup editor, a style editor, and a script editor.

    • Project Markup Editor provides a content editor powered by the HTML language.

    • Project Style Editor provides a content designer with readable defaults powered by the CSS language

    • Project Script Editor provides a content enhancer powered by the Javascript language.

  3. Program Guiding Resources help the team build and the audience use each editor. Through reference materials, technical guides, IntelliSense Software, non-technical guides, and operating system.

    • Project Reference Material list elements of each language the team must resolve for the corresponding editor.

    • Project Technical Guides describes each reference element to help the team build its IntelliSense software

    • Project IntelliSense Software leverage the technical guides to help the audience avoid usage scenarios.

    • Project Non-Technical Guides abstracts the technical guide to design and document the UI of each editor for the audience.

    • Project Operating System helps the team to documents and standardized the development process