upcontent 0.1.2 → 0.1.4

package/.upcontent/config.json

@@ -42,7 +42,6 @@
   "navigation": {
     "roots": [
       "index.md",
-      "README.md",
       "getting-started",
       "guides",
       "customization",
@@ -73,12 +72,13 @@
         "AGENTS.md",
         "CLAUDE.md",
         "CONTEXT.md",
-        "PRODUCT.md"
+        "PRODUCT.md",
+        "README.md"
       ]
     },
     "labelOverrides": {
       "docs": "Project Docs",
-      "readme": "Repository README"
+      "index": "Getting Started"
     }
   },
   "content": {

package/README.md

@@ -1,8 +1,3 @@
----
-heading: Upcontent
-description: Turn a documentation repository into a fast, searchable, customizable static portal.
----
-
 <div align="center">
 
 # Upcontent

package/index.md

@@ -5,15 +5,137 @@ sidebar:
   order: 1
 ---
 
-Upcontent turns a Markdown repository into a documentation site that is ready to share.
+Upcontent turns the documentation repository you already have into a fast, searchable, customizable portal.
 
-It adds clear navigation, full-text search, technical content rendering, consumer-owned branding, and a repeatable static build while keeping the source repository as the source of truth.
+[![CI](https://github.com/lumamontes/upcontent/actions/workflows/ci.yml/badge.svg)](https://github.com/lumamontes/upcontent/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/upcontent?color=0f766e&label=npm)](https://www.npmjs.com/package/upcontent)
 
-## Start here
+## Explore Upcontent
 
+- [See the live portal](https://lumamontes.github.io/upcontent/)
+- [Explore the capability showcase](showcase/)
 - [Set up a consumer repository](getting-started/consumer-repository/)
 - [Run your first build](getting-started/first-build/)
+- [Configure content](customization/content/)
+- [Configure navigation](customization/navigation/)
 - [Customize the portal](customization/)
 - [Validate before publishing](guides/validate-your-site/)
+- [Publish to GitHub Pages](deployment/github-pages/)
+- [Publish to another static host](deployment/static-hosts/)
+- [Publish releases through npm](deployment/npm/)
 
-The [repository README](readme/) contains the project and development details for Upcontent itself.
+## See the result
+
+This is the real Upcontent portal generated from this repository and deployed to GitHub Pages.
+
+<p align="center">
+  <a href="https://lumamontes.github.io/upcontent/"><img src="assets/readme/portal-home.png" alt="Upcontent documentation portal home page" width="900"></a>
+</p>
+
+The same build includes a capability showcase for technical content, structured data, callouts, diagrams, navigation, and search.
+
+<p align="center">
+  <a href="showcase/"><img src="assets/readme/portal-showcase.png" alt="Upcontent capability showcase page" width="900"></a>
+</p>
+
+## From repository to portal
+
+Upcontent keeps your source of truth in Git and adds the publishing layer: clear navigation, full-text search, technical content rendering, consumer-owned branding, and a repeatable static build.
+
+If your Markdown already lives in a GitHub repository, the flow is:
+
+```sh
+pnpm dlx upcontent init
+pnpm dlx upcontent dev
+pnpm dlx upcontent check
+```
+
+The first command creates `.upcontent/` and a GitHub Pages workflow. The second starts a local portal using the repository you are already in. The third builds the consumer portal and validates the generated site. You do not need to clone the Upcontent renderer into your documentation repository.
+
+Push the generated workflow and your documentation is published as a static site. The source repository remains the source of truth; Upcontent does not require a database, a companion server, or a new authoring system.
+
+## What you get
+
+- A responsive [Starlight](https://starlight.astro.build/) portal with navigation, search, themes, and table of contents.
+- A `.upcontent/config.json` file for identity, navigation, rendering, and content boundaries.
+- Consumer-owned logos, favicon, CSS, site identity, and navigation.
+- Rendered callouts, Mermaid diagrams, JSON, YAML, CSV, and wiki links.
+- A static `dist/` directory deployable to GitHub Pages or any static host.
+- Build checks that catch broken wiki links and excluded content before publication.
+
+## Is it a good fit?
+
+Upcontent is a good fit when:
+
+- Your documentation already lives in Markdown or MDX.
+- Your team wants to keep writing in Git.
+- You want the portal to be owned and deployed by the documentation repository.
+- You need more than raw Markdown, but do not need a dynamic application.
+- You want branding and navigation without maintaining a custom docs frontend.
+
+It is not the right fit when your site needs runtime authentication, server-rendered personalization, or review comments inside the published portal.
+
+## Explore this repository locally
+
+Clone this repository, then start the included golden consumer:
+
+```sh
+git clone https://github.com/lumamontes/upcontent.git
+cd upcontent
+pnpm install
+make dev CONTENT_PATH=.
+```
+
+Then open the local URL printed by Astro. The [capability showcase](showcase/) is the fastest way to see the complete rendering and customization surface.
+
+## Configure your portal
+
+The consumer configuration is deliberately small:
+
+```json
+{
+  "site": {
+    "title": "Engineering Docs",
+    "description": "Documentation for the engineering team.",
+    "socialImage": "https://docs.example.com/social-card.png",
+    "locale": "en-US",
+    "logo": {
+      "src": ".upcontent/logo.svg",
+      "alt": "Engineering Docs"
+    },
+    "favicon": ".upcontent/favicon.svg"
+  },
+  "seo": {
+    "enabled": true
+  },
+  "repo": {
+    "url": "https://github.com/acme/engineering-docs"
+  },
+  "theme": {
+    "customCss": [".upcontent/theme.css"]
+  }
+}
+```
+
+Follow [Set up a consumer repository](getting-started/consumer-repository/) for the complete setup, then use [Customization](customization/) to shape the portal.
+
+## Build for production
+
+```sh
+make build CONTENT_PATH=/path/to/your-consumer-repo
+```
+
+The generated site is written to `dist/` and includes the Pagefind search index. Before publishing, run:
+
+```sh
+pnpm test
+pnpm check
+make build CONTENT_PATH=.
+make check-external
+```
+
+Read the [deployment guide](deployment/) for GitHub Pages and other static hosts.
+
+## Built on Astro and Starlight
+
+Upcontent uses the official [Astro](https://astro.build/) framework and [Starlight](https://starlight.astro.build/) documentation theme as its rendering foundation. Upcontent adds the consumer-repository contract, content integrity checks, configuration surface, and deployment workflow around them.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "upcontent",
   "type": "module",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "packageManager": "pnpm@10.20.0",
   "repository": {
     "type": "git",

package/scripts/verify-golden-build.mjs

@@ -1,13 +1,12 @@
-import { existsSync, readFileSync } from 'node:fs'
+import { existsSync } from 'node:fs'
 
-const htmlPath = existsSync('dist/readme/index.html') ? 'dist/readme/index.html' : 'dist/index.html'
-const html = readFileSync(htmlPath, 'utf8')
+const htmlPath = 'dist/index.html'
 const requiredAssets = ['assets/readme/portal-home.png', 'assets/readme/portal-showcase.png']
 
+if (!existsSync(htmlPath)) throw new Error(`Golden build is missing: ${htmlPath}`)
+
 for (const asset of requiredAssets) {
   if (!existsSync(`dist/${asset}`)) throw new Error(`Golden build is missing: dist/${asset}`)
-  if (existsSync('dist/readme/index.html') && !existsSync(`dist/readme/${asset}`)) {
-    throw new Error(`Golden build is missing README route asset: dist/readme/${asset}`)
-  }
-  if (!html.includes(asset)) throw new Error(`Golden build does not reference: ${asset}`)
 }
+
+if (existsSync('dist/readme/index.html')) throw new Error('Golden build unexpectedly published README as a portal route')

package/src/lib/sidebar.ts

@@ -113,8 +113,8 @@ export function buildSidebar(docsRoot: string): SidebarEntry[] {
     }
   }
 
-  // A homepage fica fixa em primeiro, com o label configurável "Home" por
-  // padrão, sem competir alfabeticamente com as outras páginas.
+  // A homepage fica fixa em primeiro, com o label configurável, sem competir
+  // alfabeticamente com as outras páginas.
   const homepageIndex = entries.findIndex(e => !isSidebarGroup(e) && e.slug === 'index')
   const homepageEntry = homepageIndex >= 0 ? entries.splice(homepageIndex, 1)[0] : undefined
   const sorted = sortEntries(entries)