Scott Scoble personal brand website — blog, speaking, consulting, fractional
|
All checks were successful
Build and Deploy to Storj / build-and-deploy (push) Successful in 9s
## Agentic Wars Blog Post Review changes applied: 1. 'Convenience is not capability' pulled into its own callout 2. Closer reframed: 'Are your capabilities compounding, or are you being extracted from?' 3. Blog card excerpt fixed ### Changes - `src/pages/blog/agentic-wars.astro` — new blog post - `src/pages/blog.astro` — added card to blog index --- ## LinkedIn Post The agentic wars are here. Meta has Hatch. Google has Remy. Everyone is building agents. The question nobody is asking: when you use them, whose capability actually compounds? Hatch keeps you in Instagram. Remy keeps you in Gemini. Every prompt, every delegated decision, every pattern the agent learns — it all compounds for the platform, not for you. Their models get smarter. Their lock-in gets deeper. You get more convenient. Convenience is not capability. This is the third extraction wave. Cloud took your infrastructure. Social media took your attention. Now agents are taking your decision patterns. Every time you use a hosted agent, you're training someone else's model on your judgment. Their capability compounds. Yours does not. The alternative: run your own agents. Keep your data. The open-source tools exist today. I've been running my own agent system for months. The value isn't in the output — it's in the decision loop. I review, I decide, I articulate what I actually think. That compounds my judgment, not a platform's. Are your capabilities compounding, or are you being extracted from? https://scott.scoble.me/blog/agentic-wars #AgenticAI #PersonalAI #OpenSource #Cultivation Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/brand-site/pulls/87 Co-authored-by: Marcus (agent-cos) <cos@marcus.local> Co-committed-by: Marcus (agent-cos) <cos@marcus.local> |
||
|---|---|---|
| .astro | ||
| .forgejo/workflows | ||
| public | ||
| src | ||
| .ci-enabled | ||
| .gitignore | ||
| astro.config.mjs | ||
| EOF | ||
| flake.nix | ||
| one-sheet.typ | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| RESOLVED-48-62.md | ||
| tsconfig.json | ||
Scott Scoble — Speaker Website
Professional speaker/consultant website for Scott Scoble.
Stack
- Framework: Astro 5
- Hosting: Storj (S3-compatible static hosting)
- Domain: scott.scoble.me
- CI/CD: Forgejo Actions
Development
npm install
npm run dev
Build
npm run build
Output goes to dist/.
Deploy
Deployment is automatic on push to main via Forgejo Actions.
Manual Setup
-
Add secrets to Forgejo repo:
STORJ_ACCESS_KEY— Storj S3 access keySTORJ_SECRET_KEY— Storj S3 secret keySTORJ_BUCKET— Bucket name (e.g.,brand-site)
-
Ensure bucket exists in Storj with public access and custom domain configured.
PDF Generation
nix-shell -p typst --run "typst compile one-sheet.typ one-sheet.pdf"
Project Structure
src/
components/ # Reusable Astro components
layouts/ # Page layouts
pages/ # Route pages
content/ # Content collections (future)
styles/ # Global CSS
public/
images/ # Static images
downloads/ # Downloadable files (PDFs)
.forgejo/
workflows/ # CI/CD workflows
License
MIT