Urgent.News

What's breaking now, across thousands of outlets.

Tech

An open-source, modular CMS for developers and AI-assisted/vibe-coded websites.

For years, the CMS ecosystem has largely followed the same formula. Install a CMS. Choose a theme. Install plugins. Customize some templates. Add an API when you need one. Then, eventually, try to connect everything to AI. But the way we build software has changed. Developers increasingly work alongside AI coding assistants. People are building websites by describing what they want instead of…

Basehim is an open-source, modular, API-first PHP Content Management System (CMS) designed for developers and AI integration. The system aims to provide a simpler foundation for building, customizing, automating, and extending websites without overcomplicating the infrastructure stack. Unlike traditional CMS architectures that were designed for human administrators, Basehim is built to work with modern PHP and MySQL hosting environments, eliminating the need for SSH access, Composer, Node.js, build pipelines, background workers, containers, or cloud deployment environments.

Basehim's architecture is built around three key ideas: API-first, modular, and AI-ready. The API-first approach means that the REST API is not an afterthought, but a core component of the CMS, exposing resources such as posts, pages, media, taxonomies, menus, comments, users, settings, apps, caching, and scheduling. Authentication is flexible, with options for server-to-server integrations, applications acting on behalf of users, and AI agents.

The built-in Model Context Protocol (MCP) server allows AI applications and agents to interact with external systems, while still maintaining security through OAuth 2.1 and scoped permissions. This ensures that AI agents have only the necessary permissions to perform their functions, preventing unauthorized access to sensitive data.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Harness Engineering - Part 8: Observability

Welcome back to the Harness Engineering series — a 10-part journey from raw language model to production-ready agentic system. Made by builders. For builders.

  • Observability consists of logs, traces, and latency metrics
  • Logs capture model call details: input, output, latency, tokens
  • Traces record tool executions: name, arguments, result, duration

Network Troubleshooting as a Stack: Find Which Layer Is Broken First

The difference between a good infrastructure troubleshooter and someone who restarts services and hopes is a mental model.

  • Network operates as a stack: Application, TLS, Port, DNS, Gateway, Route, Interface
  • Start troubleshooting from Interface layer by checking link and IP address
  • Use specific commands (ip addr show, ip route get, ping, dig, nc, openssl, curl) to test each layer

More from Saturday 15 August →