The working problem
JAWS.tech needed to connect a long telecommunications career, JAWS Resources, real estate, practical AI work, ICE SPA and future projects without reading like a collection of unrelated businesses. It also needed to stay inexpensive, editable and deployable on an ordinary static hosting account.
Where AI assistance helped
AI assistance was useful for reviewing a large brief, mapping the information architecture, drafting restrained page copy, creating reusable HTML patterns, centralising changeable configuration and generating validation checks. It reduced repetitive work and made it easier to compare the implementation against a long acceptance list.
Those gains did not remove the need to inspect the source files. The CV was reviewed privately, the older instruction document was reconciled against the latest brief, and the workspace’s hosting and deployment records were checked before the site structure was created.
Where human judgement controlled the outcome
- Personal fields in the source CV were excluded from the public website.
- Planned Costa del Sol activity was labelled as planned, not established.
- In-development domains were shown without broken external links.
- Unsupported certifications, testimonials and business results were left as explicit placeholders.
- The existing live website, DNS and cPanel document root were not changed.
Why the technical structure is deliberately simple
The site uses semantic HTML, one CSS design system and small vanilla JavaScript files. There is no framework, build process, paid component, backend or tracking script. The result can be previewed from a local static server and later copied to ordinary cPanel hosting after a separate backup and approval process.
Frequently changing information — email, website domains, availability wording, venture status and featured insights — lives in one configuration file. That keeps routine changes small and reviewable.
What still needs to happen
Before the site can replace any existing public JAWS.tech files, it still needs final content approval, approved photography, a public-safe CV if required, confirmation of the AI Sin Miedo domain spelling, a backup of the current live document root and an authorised deployment window.
Draft takeaway
The useful pattern was not “let AI build a website”. It was to give AI a bounded implementation role while source evidence, privacy, status clarity and deployment authority remained explicit controls.