Umar Draz

Umar DrazSep 18, 2026

𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐚𝐧 𝐀𝐈 𝐜𝐡𝐚𝐭𝐛𝐨𝐭 𝐢𝐧𝐭𝐨 𝐖𝐨𝐫𝐝𝐏𝐫𝐞𝐬𝐬 𝐭𝐞𝐚𝐜𝐡𝐞𝐬 𝐲𝐨𝐮 𝐟𝐚𝐬𝐭 𝐭𝐡𝐚𝐭 𝐭𝐡𝐞 𝐀𝐈 𝐦𝐨𝐝𝐞𝐥 𝐢𝐬 𝐫𝐚𝐫𝐞𝐥𝐲 𝐭𝐡𝐞 𝐡𝐚𝐫𝐝 𝐩𝐚𝐫𝐭. AI Support Assistant lets you build an on-site chatbot that answers from your own documentation instead of guessing. Upload a PDF, Word doc, or text file, or point it at a documentation URL, and it indexes the content directly inside your WordPress MySQL database. No external vector database account, no extra SaaS bill. It works with Gemini, OpenAI, or the native WordPress AI connectors, streams answers in real time, and shows which document each answer came from. The part that takes longer than writing the RAG pipeline is everything around it, and that's what the latest release focuses on. 1- Admin and frontend fonts now load as local, self-hosted WOFF2 files instead of pulling from an external source. That closes a small but real GDPR gap and removes the extra network round trip on every page load. 2- The WordPress Native AI Client connector detection got smarter too. If a connector still needs configuration, the plugin now points that out in context instead of leaving you to work it out on your own. 3- Behind the scenes, I reworked the admin settings layout and removed database queries that were running on every admin load without adding any value. Combined with a general performance and code quality pass, the plugin is now more closely aligned with WordPress.org's plugin guidelines. None of this shows up in a demo video. It shows up in how a plugin holds up six months after installation, once real traffic and real edge cases start hitting it. What's the kind of improvement you find yourself shipping repeatedly across your own plugins or products, the kind that never makes it into a highlight reel? Plugin page: https://lnkd.in/dF92TpbN #WordPress #AI #Chatbot #RAG #WordPressPlugin #GDPR #OpenAI #Gemini #SoftwareEngineering #WebPerformance

Umar DrazSep 14, 2026

Most WordPress AI chatbot plugins have the same catch. They work fine in the demo, then you find out you also need a paid vector database subscription Pinecone, Qdrant, Milvus just to keep it running. 𝐈 𝐛𝐮𝐢𝐥𝐭 𝐀𝐈 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐀𝐬𝐬𝐢𝐬𝐭𝐚𝐧𝐭 𝐭𝐨 𝐬𝐤𝐢𝐩 𝐭𝐡𝐚𝐭 𝐬𝐭𝐞𝐩 𝐞𝐧𝐭𝐢𝐫𝐞𝐥𝐲. Here's how it works. The plugin extracts text from your uploaded PDF, DOCX, or TXT files and splits it into chunks. Instead of pushing those chunks to an external vector store, it saves the embeddings directly inside your existing WordPress MySQL database and runs a cosine similarity search against them. When a visitor asks a question, it finds the closest matching content, sends it to Gemini or OpenAI, and returns an answer with the source document cited underneath. If nothing matches well enough, you control the fallback response instead of letting the model guess. No extra infrastructure. No recurring SaaS bill beyond the AI provider you're already paying for. It also ships with query logs, token usage graphs, and three widget themes, so you can see what visitors are actually asking instead of flying blind. It's live on WordPress.org now. https://lnkd.in/dF92TpbN If you've built RAG-style search before is storing embeddings in a relational database a reasonable trade-off, or does it fall apart once the document count grows? #WordPress #WordPressDevelopment #AI #Chatbot #RAG #OpenAI #GoogleGemini #SoftwareEngineering #WebDevelopment #OpenSource

Umar DrazSep 5, 2026

Most WordPress site owners think their site is secure because nothing bad has happened yet. That's not security. That's luck, running out slowly. I've reviewed a lot of WordPress sites over the years, and the pattern is almost always the same. The site "looks fine." It loads. It works. Nobody has complained. So the assumption is that everything underneath is fine too. Here's the problem: most WordPress compromises are quiet. No dramatic defacement, no obvious warning. Just a hidden script injecting spam links, a plugin silently sending data somewhere it shouldn't, or an outdated theme with a known vulnerability nobody patched. So instead of asking "has my site been hacked," ask this instead: • Do you actually know how many plugins are installed, and are they all still maintained? • Is your WordPress core, theme, and every plugin on the latest version right now, not last quarter? • Do you have a real user permission structure, or does everyone log in as an admin? • Are you running automated backups that you've actually tested restoring? • Is there a firewall or security layer in front of the site, or is WordPress facing the internet unprotected? • When was the last time someone reviewed the file system for anything that shouldn't be there? If you hesitated on more than one of these, your site probably isn't as secure as you think it is. Not because something is definitely wrong, but because you have no visibility into whether something is wrong. Security on WordPress isn't a plugin you install once. It's an ongoing habit updates, monitoring, and knowing exactly what's running on your site at all times. Which of these would you struggle to answer confidently about your own site? #WordPress#WebSecurity#WordPressSecurity#SoftwareEngineering#WebDevelopment#CyberSecurity#TechLeadership#SmallBusinessTech#WebsiteMaintenance#UmarDraz