Manage后台管理
A practical content-management plan for MAC-Lab's GitHub Pages website, combining GitHub login, static CMS editing, issue forms, and scheduled automation.MAC-Lab GitHub Pages 网站的后台管理方案：结合 GitHub 登录、静态 CMS、Issue 表单与定时自动化。
What GitHub Pages can and cannot doGitHub Pages 能做什么，不能做什么
GitHub Pages is excellent for a public academic website: fast static pages, strong version history, stable URLs, search-engine crawlability, scheduled GitHub Actions, and safe public documentation. It does not provide a private database or server-side user system by itself. For login-based editing, the best lightweight path is to use GitHub authentication and commit-based content management.GitHub Pages 非常适合公开学术网站：静态页面快、版本历史清楚、URL 稳定、搜索引擎容易抓取，并且可以配合 GitHub Actions 定时更新。它本身不提供私有数据库或服务器端用户系统。若要登录编辑，最稳妥的轻量路线是使用 GitHub 身份认证和基于提交的内容管理。
Current Admin Status当前后台状态
Two admin layers are now prepared. `/admin/` is the public-content CMS for website pages. `/console/` is the internal lab operations workspace for members, student pages, lab news materials, partner CRM, outputs, review tasks, frontier curation, analytics snapshots, backup exports, and audit logs. The console is designed around owner, admin, and student roles, with private records stored in Supabase rather than the public GitHub Pages repository.现在已经预留两层后台。`/admin/` 用于官网公开内容编辑；`/console/` 已升级为实验室内部运营工作台，包括成员、学生个人页、实验室新闻素材、合作 CRM、项目成果、审核队列、前沿精选、访问统计快照、备份导出和操作日志。控制台按 owner、admin、student 三类角色设计，内部记录放在 Supabase，不进入公开 GitHub Pages 仓库。
Operational Console Model后台工作台模型
People and Permissions成员与权限
New users enter as pending students. The owner can activate accounts, promote trusted admins, and keep ordinary students focused on their own pages and material submissions.新用户默认进入待审核学生状态。owner 可以激活账号、设置可信学生管理员，并让普通学生主要维护自己的页面和提交材料。
Material Intake素材沉淀
News, student achievements, papers, projects, system progress, competition results, and partner-facing proof points can be entered first as internal materials, then rewritten into public website language after review.新闻、学生成果、论文、项目、系统进展、竞赛结果和合作证明点可先进入内部素材池，审核后再改写成适合官网发布的文字。
Partner Pipeline合作线索
Scenario requests can be recorded with organization, contact, application domain, available signals, constraints, and expected decision value. This makes later project proposals and pilot designs easier to trace.合作需求可按单位、联系人、应用方向、可用信号、约束条件和预期决策价值记录，方便后续申报书、技术方案和试点设计追溯。
Public Publishing公开发布
Approved materials can now generate public Markdown/YAML drafts for news, frontier items, student pages, capability cases, and solutions pages. Git commits preserve every public change.审核后的材料现在可以生成公开 Markdown/YAML 草稿，用于新闻、前沿精选、学生页面、能力案例和行业方案页面；所有公开修改都通过 Git 提交保留版本记录。
Review Queue and Audit Trail审核队列与操作日志
Content tasks, frontier curation, and audit logs make the console more than a form collection: materials can move through submitted, review, approved, public-ready, and archived states with traceable changes.审核任务、前沿精选和操作日志让控制台不只是表单收集，而是能让素材按 submitted、review、approved、public_ready、archived 等状态流转，并保留可追踪修改记录。
Analytics and Backup访问统计与备份
Aggregate traffic snapshots and JSON exports turn the website into a maintainable lab asset: the team can see which public pages are working, preserve operational data, and hand over work without losing context.聚合访问统计快照与 JSON 导出让网站成为可运营的实验室资产：团队可以观察哪些公开页面有效，保留后台数据，并在学生管理员交接时不丢上下文。
Private lab management is staged at `/console/`.内部管理控制台已放在 `/console/`。
Recommended roles are simple: Professor Sun as owner, a small group of trusted students as admins, and ordinary students as members who can maintain their own pages and submit materials.推荐权限保持清晰：孙晓教授为 owner，少数可信学生为 admin，普通学生为 student，可维护自己的页面并提交新闻、成果和项目材料。
Open Console打开内部控制台Supabase provides login, database, and role control.Supabase 负责登录、数据库与权限。
GitHub Pages remains the public website host. Internal data should live in Supabase with Row Level Security, not in this public repository.GitHub Pages 继续承担公开官网托管；内部数据放入带行级权限的 Supabase，不进入公开仓库。
Read Setup Notes查看部署说明Recommended Admin Architecture推荐后台架构
Use `/admin/` for page and data editing用 `/admin/` 编辑页面与数据
The repository includes a Decap CMS scaffold. After GitHub OAuth is configured, authorized users can edit selected pages and data files in the browser and publish changes through commits.仓库已预留 Decap CMS 后台。配置 GitHub OAuth 后，授权用户可以在浏览器中编辑指定页面和数据文件，并通过提交发布。
Use GitHub Issue Forms for structured updates用 GitHub 表单收集结构化更新
Students and lab members can submit news, publications, cases, and frontier items through controlled forms, then a maintainer reviews and converts them into public content.学生和实验室成员可以通过受控表单提交新闻、论文、案例和前沿条目，再由维护者审核后转成公开内容。
Use GitHub Actions for scheduled refreshes用 GitHub Actions 定时刷新
The frontier radar runs twice daily through GitHub Actions. The same pattern can support monthly summaries, publication refreshes, sitemap updates, and content-health checks.前沿雷达已经通过 GitHub Actions 每天两次刷新。相同模式可扩展到月度观察、论文刷新、站点地图更新和内容健康检查。
Keep sensitive management outside the public site敏感管理不要放在公开站点
Internal student records, partner contracts, raw data, and unpublished technical details should stay in private systems, not in a public GitHub Pages repository.学生内部记录、合作合同、原始数据和未公开技术细节，应放在私有系统中，不应进入公开 GitHub Pages 仓库。
Seven Optimizations and GitHub Support七类优化与 GitHub 支持情况
Solutions Page行业解决方案页
Supported directly by GitHub Pages. The new Solutions page can grow by scenario, partner type, and application domain, keeping public communication focused on value, maturity, and collaboration entry points.GitHub Pages 直接支持。新的行业方案页可以按场景、合作对象和应用领域持续扩展，让公开表达聚焦价值、成熟度和合作入口。
Cases Page代表性案例页
Supported directly by GitHub Pages. Capability cases can present scenario value, research depth, delivery routes, and representative outcomes in a form suitable for public reading.GitHub Pages 直接支持。能力案例可以用适合公开阅读的方式呈现场景价值、研究深度、交付路线和代表性成果。
Collaboration Flow合作流程
Supported as static content and issue forms. The public site can explain the process; GitHub Issues can collect structured partner or lab-member updates.可通过静态内容和 Issue 表单支持。公开站点解释流程，GitHub Issues 收集结构化更新。
Visual Evidence视觉证据
Supported through static images and diagrams. The site can add architecture diagrams, scenario maps, transformation routes, and visual case narratives to make complex capabilities easier to read.可通过静态图片和图文模块支持。可以增加架构图、场景图、转化路径图和案例视觉叙事，让复杂能力更容易被理解。
SEO and AI SearchSEO 与大模型抓取
Supported through metadata, sitemap, robots.txt, llms.txt, structured data, FAQ sections, and stable URLs.可通过元数据、站点地图、robots.txt、llms.txt、结构化数据、FAQ 和稳定 URL 支持。
Frontier Radar as Knowledge Asset前沿雷达知识资产化
Supported through GitHub Actions and data files. The radar now keeps a larger archive and can grow into topic clusters, weekly selected signals, monthly lab observations, and capability-linked trend summaries.可通过 GitHub Actions 和数据文件支持。雷达现在保留更大的归档池，可继续扩展为方向聚类、每周精选、月度观察和能力关联趋势总结。
Backend Management后台管理
Partially supported by GitHub alone. Public content editing can use GitHub login and static CMS. Private databases, fine-grained internal permissions, and operational dashboards require external services.GitHub 单独可部分支持。公开内容编辑可用 GitHub 登录和静态 CMS；私有数据库、精细权限和运营管理看板需要外接服务。
Admin scaffold is available at `/admin/`.后台入口已预留在 `/admin/`。
The scaffold is intentionally limited to public content. Before live use, configure a GitHub OAuth provider for Decap CMS and add only trusted maintainers to the repository.该后台仅面向公开内容。正式使用前，需要为 Decap CMS 配置 GitHub OAuth，并只给可信维护者仓库权限。
Public website content is not the same as internal lab management.公开官网内容不等于实验室内部管理系统。
Use this website to publish public news, cases, recruitment, papers, media, and frontier summaries. Use private tools for student records, partner files, budgets, raw data, and sensitive technical documents.官网用于发布公开新闻、案例、招生、论文、媒体和前沿总结。学生记录、合作文件、经费、原始数据和敏感技术文档应放在私有工具中。