Medellín Web Soluciones site
Firm Django site: services, projects, FAQ, portal, billing and knowledge hub for the agent (architecture/team/quote sync).
MWS commercial presence is also a knowledge backend: sync about/architecture/accepted quotes into the agent, with i18n and admin ops.
The challenge
- 1Unify commercial message and agent knowledge.
- 2Split legacy Angular from Django site.
- 3Keep product checkout separate from services.
The approach
Django site of record
Pages, services, blog, portal, billing.
agent_knowledge
Ingest/sync into assistant RAG.
Clear boundaries
Angular aside; Woo for store.
Django 6 serves the site + agent_knowledge (RAG sync); legacy Angular stays separate; Woo is a separate checkout.
System layers
- 01Django marketing pages
- 02Services catalog
- 03Portal / billing
- 04agent_knowledge + embeddings
- 05Admin hub
- 06WhiteNoise statics
Applied stack
- Django
- Python
- WhiteNoise
- PostgreSQL
- RAG
- Angular
Design decisions
Django as source of truth
Admin, SEO and knowledge in one system.
Selective RAG sync
Agent speaks from curated data, not raw CMS dump.
Decoupled store
Services ≠ product SKUs.
Outcomes
- 18
- Documented services
- RAG
- Knowledge sync to agent
- Admin
- Content operations
Key points
- The site feeds the agent—not silos.
- Agency architecture ready to grow.
- SEO + ops in one stack.
Fit / how to hire
Hire this if you need a technical founder/lead who unites the marketing site with the AI agent's knowledge ops—one technical owner, not a patchwork of vendors. Boutique full-ownership engagement, with an optional retainer.
Book a technical call
