Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 20, 2026

Implements the public-facing homepage for ObjectOS, establishing it as "The Business Operating System" - an enterprise low-code runtime engine built on ObjectQL & NestJS.

Changes

Hero & Brand Positioning

  • "Enterprise Low-Code Runtime Engine" badge
  • "The Business Operating System" tagline with clear messaging: "Instant Backend. Security Kernel. Workflow Automation."
  • Grid background pattern, responsive CTAs to docs and GitHub
  • Positioned as built on ObjectQL (dependency) rather than as peer products

Introduction Section

  • Explains ObjectOS as the runtime platform: "While ObjectQL defines how data looks, ObjectOS defines how business runs"
  • Three role cards showcasing ObjectOS capabilities:
    • The Enforcer: RBAC and Record-Level Security (RLS)
    • The Server: REST, GraphQL, and JSON-RPC APIs
    • The Automator: Triggers, workflows, and scheduled jobs

Key Features

  • Enterprise Security Kernel: Authentication (OIDC, SAML, LDAP), fine-grained permissions, audit logging
  • Instant API Gateway: Auto-generated REST API, GraphQL schema stitching, metadata API
  • Workflow & Automation: Triggers (beforeInsert, afterUpdate, beforeDelete), flow engine, job queue

Architecture Section

Shows ObjectOS modular monorepo structure:

  • @objectos/kernel - Core logic engine wrapping ObjectQL
  • @objectos/server - NestJS application layer
  • @objectos/plugin-auth - Authentication strategies
  • @objectos/plugin-workflow - Workflow engine
  • @objectos/presets - Standard system objects

Technical

  • Enhanced metadata: Open Graph, Twitter Cards, SEO keywords focused on ObjectOS branding
  • Lucide React icons for visual elements
  • TailwindCSS responsive layouts
  • AGPL v3 licensing messaging

Screenshot

ObjectOS Homepage

Original prompt

设计objectos开源站点首页,参考以下内容

Role: Chief Brand Architect & Principal System Engineer for ObjectStack

Context:
You are the architect behind the official website of ObjectStack (objectstack.ai).
ObjectStack is NOT a traditional SaaS, nor just a framework. It is a "Post-SaaS Operating System" designed to decouple data from storage and logic from implementation.

Your Mission:
To articulate a paradigm shift in software architecture to a high-level technical audience (CTOs, VPs of Engineering, Lead Architects). You must translate complex "Meta-Programming" concepts into tangible business value: Asset Longevity, Data Sovereignty, and Infinite Extensibility.


1. The "ObjectStack" Taxonomy (Strict Naming Conventions)

You must adhere to this naming system. Do not use generic terms like "Data Layer" or "ORM" in branding.

A. The Core Trinity (Open Source / MIT)

  • The Engine (formerly ObjectQL)

    • Product Name: ObjectQL
    • Concept: The Metadata-Driven Data Engine.
    • Value: "The Universal Protocol." It abstracts storage (SQL/NoSQL/Excel) and automates logic.
  • The Components (formerly ObjectUI)

    • Product Name: ObjectUI
    • Concept: The Enterprise Interface Kit.
    • Value: "The Projection Layer." Server-driven UI rendering that adapts to the Engine's schema.
  • The Platform (formerly ObjectOS)

    • Product Name: ObjectOS
    • Concept: The Low-Code Kernel & Application Platform.
    • Value: "The Operating System." Identity, Organization, Workflow, and Governance.

B. The Ecosystem & Commercial Layer

  • Object Marketplace: The hub for Drivers (Redis, Excel, Postgres) and Apps (CRM, ERP templates). (URL: /market)
  • Object Cloud: The serverless PaaS for hosting ObjectStack. (URL: console.objectstack.ai)
  • ObjectStack Enterprise: The commercial license providing Governance, SSO, and Audit Logs.

Tone Guidelines

  • Authoritative but Modular: Speak like a System Architect. Use words like Protocol, Kernel, Driver, Schema, Manifest.
  • Polyglot & Agnostic: Never imply we only work with SQL. Crucial Differentiator: We treat Excel, Redis, and Postgres as equal citizens.
  • Anti-Fragile: Emphasize that ObjectStack protects against "Framework Fatigue." React changes every 3 years; ObjectQL Protocols last for decades.

Key Value Mappings

Feature The "Why" (Business Value)
Metadata-Driven "Asset Longevity." Don't hardcode logic. Define it in Schema. Your IP survives the next tech cycle.
Universal Drivers "No Vendor Lock-in." Connect to Oracle today, switch to Postgres tomorrow, mount an Excel sheet meanwhile. Zero migration scripts.
Server-Driven UI "Development Velocity." Backend changes instantly reflect on Frontend. No "API glue code."
Enterprise Edition "Governance & Control." Community gives you the engine; Enterprise gives you the guardrails (SSO, Audit, HA).

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

@vercel
Copy link

vercel bot commented Jan 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
objectos-site Ready Ready Preview, Comment Jan 20, 2026 0:31am

Request Review

Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
@huangyiirene
Copy link
Contributor

错了,你现在要构建的是一个子站点objectos的主页 @copilot

Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
Copilot AI changed the title [WIP] Design homepage for ObjectStack open source site Design ObjectStack homepage with brand architecture Jan 20, 2026
Copilot AI requested a review from huangyiirene January 20, 2026 12:22
Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Jan 20, 2026

错了,你现在要构建的是一个子站点objectos的主页 @copilot

你说得对!我已经重新设计了页面,现在聚焦于 ObjectOS 本身——作为企业级低代码运行时引擎,而不是整个 ObjectStack 生态系统。

已更正为:

  • ObjectOS 作为"业务操作系统"
  • 基于 ObjectQL 和 NestJS 构建(依赖关系,而非平级产品)
  • 强调三大角色:执行者(RBAC)、服务器(API网关)、自动化器(工作流)
  • 展示模块化单仓库架构(@objectos/* 包)

提交: ab1f647

ObjectOS Homepage

Copilot AI changed the title Design ObjectStack homepage with brand architecture Design ObjectOS homepage for enterprise runtime engine Jan 20, 2026
@huangyiirene huangyiirene marked this pull request as ready for review January 20, 2026 13:04
@@ -1,34 +1,252 @@
import Link from 'next/link';
import { Shield, Zap, Cog, Lock, Workflow, Database, ArrowRight } from 'lucide-react';

Check notice

Code scanning / CodeQL

Unused variable, import, function or class Note

Unused import Cog.

Copilot Autofix

AI 1 day ago

In general, unused imports should be removed from the import list so that only actually referenced symbols are imported. This avoids confusion and keeps the codebase cleaner.

For this specific case, the best fix is to update the lucide-react import on line 2 in apps/site/app/page.tsx to remove Cog from the destructured import list, leaving all other imported icons unchanged. No other code changes or new definitions are required, since nothing in the file refers to Cog.

Concretely:

  • Edit apps/site/app/page.tsx.
  • Locate the line import { Shield, Zap, Cog, Lock, Workflow, Database, ArrowRight } from 'lucide-react';.
  • Remove Cog, from the list, resulting in import { Shield, Zap, Lock, Workflow, Database, ArrowRight } from 'lucide-react';.
  • No additional imports, methods, or variable definitions are needed.
Suggested changeset 1
apps/site/app/page.tsx

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/apps/site/app/page.tsx b/apps/site/app/page.tsx
--- a/apps/site/app/page.tsx
+++ b/apps/site/app/page.tsx
@@ -1,5 +1,5 @@
 import Link from 'next/link';
-import { Shield, Zap, Cog, Lock, Workflow, Database, ArrowRight } from 'lucide-react';
+import { Shield, Zap, Lock, Workflow, Database, ArrowRight } from 'lucide-react';
 
 export default function HomePage() {
   return (
EOF
@@ -1,5 +1,5 @@
import Link from 'next/link';
import { Shield, Zap, Cog, Lock, Workflow, Database, ArrowRight } from 'lucide-react';
import { Shield, Zap, Lock, Workflow, Database, ArrowRight } from 'lucide-react';

export default function HomePage() {
return (
Copilot is powered by AI and may make mistakes. Always verify output.
@huangyiirene huangyiirene merged commit 2f2b135 into main Jan 20, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants