docs: refresh org profile around AI implementation focus - #1
Conversation
Sync with current positioning: AI agents, MCP servers and automations lead; open-source grouped into MCP servers / agent tooling / WordPress; products table updated; connect adds benkalsky.co.il blog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@codex review |
There was a problem hiding this comment.
Pull request overview
Updates the organization profile README to reflect Digitizer’s current positioning around AI implementation (agents with permissions/oversight, MCP servers, and end-to-end automations) while retaining web/SEO as supporting capabilities.
Changes:
- Refreshes the headline and “What We Do” section to emphasize AI implementation, MCP servers, and automations.
- Reorganizes open source projects into three focused tables (MCP Servers, Agent Tooling & Products, WordPress & Web).
- Updates the products list, tech stack line, and “Connect” links (adds benkalsky.co.il blog).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a50c63cf80
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 🤖 **AI Implementation** — autonomous agents with real permissions, audit logs and human oversight | ||
| 🔌 **MCP Servers** — connecting AI to the systems businesses run on: billing, hosting, CMS, ads | ||
| ⚡ **Automations** — end-to-end business processes that close tasks, not just answer questions | ||
| 🌐 **Web Development** — WordPress, Next.js, headless architectures; performance and Core Web Vitals | ||
| 🔍 **SEO & Content** — technical SEO, bilingual content (Hebrew + English), AI-powered content pipeline |
There was a problem hiding this comment.
GitHub Markdown treats these adjacent lines as soft breaks, so the five distinct services render as one continuous paragraph instead of separate entries. Use a list or restore the trailing double spaces; the same regression affects the contact methods on lines 63–65.
Useful? React with 👍 / 👎.
…d-1 P2) GitHub Markdown soft-wraps adjacent lines into one paragraph; trailing double spaces restore one entry per line. Applied to both the What We Do list and the Connect block (same rendering rule). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Syncs the org profile README with the current positioning on benkalsky.co.il and digitizer.co.il: AI implementation leads (agents with permissions/audit/oversight, MCP servers, automations), web/SEO heritage stays. Open source reorganized into three tables — MCP servers, agent tooling & products, WordPress & web — matching the site's proof section. Products table refreshed; connect row adds the Hebrew blog.
🤖 Generated with Claude Code