KoniKode · Software built with intention

DEVELOPER ONBOARDING

Start with a useful page.
Add the behavior it needs.

Choose your foundation, check the reference version, then build a small local application you can inspect and test. Clean Framework owns server decisions; FrontBaseJS enhances the HTML people receive.

CHOOSE A STARTING POINT

Follow the path that fits your work.

Build the server application

Use Clean Framework for routing, controllers, native PHP views and server-authoritative validation and access. Start with the candidate boundary, then follow the application recipe.

Read the Clean Framework starting point ↗

Enhance an existing interface

Use FrontBaseJS for focused state, events, navigation and HTTP communication. Preserve semantic HTML, working URLs and a useful baseline when JavaScript is unavailable.

Read the enhancement and recovery guide ↗

Give an IDE or AI tool product context

The Knowledge API supports all 79 Clean Framework references, product selection, search and stable IDs through account-owned keys. Start with one request and add a host integration only when you need it.

Follow the API integration guide ↗

Evaluate source access

Both frameworks are proprietary and in development. Public downloads and supported release terms are not available yet. The browser documentation is open without an account. Read-only API credentials are managed through the shared KoniKode account.

Discuss an evaluation ↗

VERSION AND RUNTIME

Match your setup to the reference.

These are the independently pinned references used by this website. They identify the integration example and its source prerequisites. Packaging, support commitments and a general production qualification remain release work.

FrontBaseJS

0.1.0-alpha.2

Node.js 22+ for build tools

Compile and enhance HTML with state, actions, navigation and bounded HTTP requests.

Alpha reference · public distribution pending · reference a2fba2b20aef

Read in this order

  1. Overview
  2. Role and maturity
  3. Navigation, state and recovery

Clean Framework extensions depend on the adapters you use: mysqli for MySQL, curl for live provider HTTP, fileinfo for upload inspection, sodium for encrypted credential storage and gd for image derivatives. FrontBaseJS build tooling uses Node.js; its browser output needs application-specific browser testing.

A SMALL, REVIEWABLE FIRST APPLICATION

Prove the full path before expanding it.

  1. Read the boundary and obtain authorized source

    Use the setup instructions matched to your reference. Keep application code, configuration and Git history separate from each framework. An account or a documentation visit does not grant a source-code license.

  2. Render one meaningful route on the server

    Follow the Clean Framework first-application recipe and walkthrough. Confirm the controller and template produce readable HTML with working links before adding browser behavior.

  3. Enhance one interaction

    Add an action or document request through the actual FrontBaseJS contracts. Keep requests bounded, preserve focus and history, and provide a clear path back to normal navigation when a request fails.

  4. Check the baseline and recovery

    Try keyboard navigation, a narrow screen, JavaScript unavailable, Back/Forward and a failed request. Keep authentication, authorization and validation on the server. Review the framework’s release gates and your application’s deployment needs before going live.

Install KoniKode