MateWishKey: Finishing the website

Overview

The video is a live “finishing the website” session where the host guides a novice (the site owner) through deploying an existing site with a GitHub repo and migrating the domain to be controlled under the owner’s Cloudflare account. The goal is low/no downtime and ongoing website updates using AI coding agents.

Key technological actions / workflow (domain + deployment)

• GitHub repo installed on the site (site codebase already connected).
• Safest domain migration approach:
  • Use a Cloudflare account
  • Move the domain under the owner’s Cloudflare control
• Goal: keep the website running with zero/low downtime during the transfer.

Cloudflare process

• Add the domain in Cloudflare (the Free plan is mentioned).
• Handle migration edge cases like:
  • “zone already exists”
  • pending name server updates
• Set up Cloudflare access/workers context that involves:
  • Account ID
  • API token / worker token
  • Worker-related configuration steps (Cloudflare Workers / Pages context)

Security detail about tokens

• API/worker tokens are shown as secrets that are visible only once.
• Tokens can be refreshed if exposed.

AI coding agent usage (building + maintenance)

• Multiple “agents” are used for parallel tasks, including:
  • One agent for photo processing and site content updates
  • Others for deployment, site validation, firewall/security checks, and debugging

Workflow concepts emphasized

• Work in the correct project folder, using commands like cd and cd ...
• Use agent modes:
  • Plan mode: agent provides a plan first; it does not execute immediately
  • Bypass permission / execution mode: agent performs changes after planning/approval
• The agent workflow includes verification in a browser (“don’t just say done—verify”).

Deploy approach

• “Always deploy” when the agent finishes updates.
• Refresh the live website to confirm changes.

Troubleshooting approach

When something fails, provide more context, especially:

• Include the URL
• Provide screenshots that show full context (error page + URL)

Media / assets handling

• After migration, the host notes the site had a loss of images, likely because image storage/assets needed to be moved—not just code.
• A “photo cleaning” preview quality is shown, with later cautions about where images live:
  • Some may be in local folders rather than in GitHub.
• Guidance includes whether to:
  • Keep images for safer future work
  • Delete assets only if you’re certain—otherwise avoid confusing the agent with deletions

Shared website management (future collaboration)

If the owner wants shared management with a colleague:

• Suggest using a dummy shared email (workable for small setups)
• Note that sharing credentials isn’t best practice for large teams; proper access roles would be preferred.

Email + domain identity

• Discussion of custom-domain email options:
  • Google (Gmail/custom domain) is recommended for business benefits (drive/files, scheduling, etc.)
  • Cloudflare email service is mentioned as an alternative, but the host steers toward Google paid for business usage
• The host promises to help configure the custom email onboarding later.

Questionnaire / form-building feature (planned site expansion)

The host guides building a client questionnaire with an Excel-like scoring model and multi-step sections.

Key captured requirements:

• 200+ questions
• Client answers provided in one go
• Clients can continue if they accidentally close the browser
• Collect name + email
• Scoring is optional at the end; scoring likely matches an existing Excel sheet
• “Iterative” form structure: six different iterations/design variants considered

Paid services caution:

• “Resend” (email sending) is described as paid
• Prefer free options via Cloudflare when possible

Plugins / development utilities

The host recommends installing development plugins in the AI coding environment, including:

• Front end development
• Context 7 (also requested)

Reasoning: plugins help the agent follow best practices and reduce the need for manual tooling research.

Resource usage / limits

Cloudflare/agent usage and limits discussed:

• Usage resets on a schedule (daily + weekly)
• Cost/model notes:
  • Opus is more expensive but still adequate for small personal website development
  • Other model suggestions exist (set/sonet)
• A Cloudflare workers/pages constraint is referenced:
  • Free tier includes a request allowance (described as many requests, not necessarily visitors)

SEO follow-up

• The host plans to later run SEO updates and share SEO best practices with the agent, such as:
  • tagging images/pages
  • keyword setup

Main speakers / sources

• Host / guide: “Mate Vishki / MateWishKey” (recurring mentor leading the deployment and agent workflow)
• Primary site owner / student: the Budapest-based person running/providing requirements for the website
• AI agents: multiple unnamed coding agents (“agent number 1/3/4”) interacting with Cloudflare, the codebase, and troubleshooting