KNOW IT SOLUTION Corporate Website

This is our own company site — KNOW IT SOLUTION at knowitsolution.com. It is not “pretty pages for show.” It is meant to be an organizational marketing surface: sales and marketing can update copy in a CMS without waiting on a developer every time a service blurb or case study changes.

In short: visitors get a credible company site (services, work, articles, contact). The internal team manages content in Directus. Thai is primary; English lives under /en.

Why we rebuilt it

The previous site worked, but updating services, publishing new cases, or writing articles was awkward when content was tied to code or an older structure.

So we rebuilt around three plain goals:

• Brand first — the home page should read as KNOW IT immediately, not as a generic SaaS dashboard
• Content as a system — services, blog, and portfolio come from a real CMS
• Solid SEO baseline — meta, sitemap, legal pages, plus signals for AI crawlers

What this project actually does

From an “what can an organization use this for?” angle, the package covers:

• Standard company pages — home, services, about, contact with map and social channels
• Blog / knowledge — posts with tags, SEO title/description, and a featured image
• Portfolio — gallery of work that can link to a case article (one project, many screenshots)
• Bilingual — UI + content for th/en as separate locales
• Publishing tooling — the postweb/ folder helps push project/knowledge entries into Directus in th+en and validates meta before publish

What this repo does not include: customer admin CRUD, logged-in portals, or internal apps. Those are separate products. This surface is the public company site only.

Stack (and why this shape)

We picked a stack our team knows well and that organizations can extend without odd vendor lock-in:

• Frontend: Nuxt 4 + Vue 3 + Nuxt UI + Tailwind CSS v4 — SSR/SSG fits crawlable marketing sites and keeps components maintainable
• CMS: Directus 11 (headless) — editors get a clear admin UI; the site only fetches published content
• Database / Cache: PostgreSQL 16 + Redis 7 — a production-friendly combo Directus supports well
• Local / Ops: Docker Compose runs postgres / redis / directus for local development

The important architectural point: the website and the content store are separate. You can redesign the frontend without migrating every article, or change how portfolio is displayed without replacing the CMS.

If an organization adopted this pattern

Imagine your company wants a similar corporate site. A practical path looks like this:

1. Stand up CMS + schema — static pages, services, team, blog, portfolio, site settings (logo, contact, social)
2. Stand up the frontend — fetch only published items; wire i18n, SEO head, sitemap
3. Hand content ownership over — marketing/sales edit text and images; developers own templates and the pipeline
4. Build a publish habit for work — finish a project → capture real screenshots → write a short case → push to the site (we use a checklist in postweb for this)

What the organization really gets is not only “a nicer website,” but a channel that stays fresh — promote a new service, add an approved customer case, or share team knowledge without opening a ticket for every paragraph.

Practical caveats when you take this into production:

• Do not publish customer secrets, internal pricing, or credentials in public articles
• Staging should be noindex — do not let search engines index experiments
• Name a content owner (who approves before publish)
• Portfolio shots should be real screenshots — never invent fake imagery

What we shipped in this round

• Full company site: home, services, about, contact
• Blog and portfolio that can link together (read the story → browse that project’s screenshots)
• trust-corporate visual direction (brand blue + amber CTA) per DESIGN.md
• Internal publishing tooling under postweb/

Know IT’s role

We owned the full path for this company site — visual direction, Directus schema, Nuxt frontend, SEO baseline, and publishing tooling. The goal is twofold: a solid front door for the company, and a concrete reference we can walk customers through when they ask how a similar corporate site would be built, which stack fits, and how team responsibilities split.

See it live

Visit knowitsolution.com — the gallery screenshots are real pages from this build. If your organization wants something in this direction, reach out through the contact channels on the site.