← Website design

your business. your website.

A clear start for
your next website.

Know what you own, see how we'll work together, and tell us what your website needs to do.

You own the accountsWe handle the buildYou approve the launch

built around ownership

Your website stays yours.

Your business controls GitHub, Cloudflare, your domain, and billing. Retro Forge Studios gets invited access to build and maintain the website. Expand each section for the practical steps.

01

What you own and how access works

A practical guide for clients working with Retro Forge Studios. It explains ownership, invited developer access, setup responsibilities, deployment, launch and ongoing maintenance.

The recommended arrangement

Your business owns its GitHub organization, Cloudflare account, domain and supporting services. Retro Forge Studios works through invited access using its own logins. You retain billing control, account recovery and the ability to appoint another developer.

Asset or serviceClient controlsRetro Forge Studios access
Domain registrationRegistration, renewals, billing and recoveryDelegated access when needed
GitHub organization and repositoryOrganization ownership, source code and historyWebsite repository access
Cloudflare account and PagesAccount administration, hosting and billingHosting configuration and deployment
Forms CMS booking and paymentsBusiness accounts, subscriptions and dataInvited access as agreed
Analytics and Search ConsoleBusiness property ownershipAppropriate management access
AI development toolsApproval of project data shared with AIDevelopment within agreed scope

Ownership terms

Account ownership and intellectual-property ownership are separate. The project agreement should define ownership of delivered code, copy, designs, reusable templates and third-party licenses. Use individual logins and invitations rather than shared passwords.

02

Client account setup checklist

Complete these steps before development starts. Existing business-owned accounts can be used when access and recovery details are current.

GitHub ownership

Create or use a personal GitHub login with an email you control. Enable two-factor authentication and save recovery codes.

Create or use the business GitHub organization. Keep a client representative as Owner; add a second trusted client owner where practical.

Create a private website repository such as business-name/website, or authorize Retro Forge Studios to create it within your organization.

Invite retroforgestudios to the repository. Start with Write access. Grant repository Admin only when configuration or access-management tasks require it, then review that permission.

Organization Owner access is normally unnecessary for the developer. Repository roles can be assigned to outside collaborators. See reference 1.

Cloudflare ownership

Create or use a business-controlled Cloudflare account. Enable two-factor authentication and save recovery information.

Keep a client representative as Super Administrator. Add your own billing details if paid services are needed.

Invite jgregory@retroforgestudios.com through account member management. Review roles and resource scopes.

Suggested starting role: Workers Platform Admin includes Pages and other developer services. It is broader than one website. Review available scopes, especially if the account holds other systems. Super Administrator should not be granted simply to manage a website. See references 2 and 3.

Domain and supporting services

Confirm registrar access and identify who manages business email, DNS and current hosting.

Identify analytics, forms, booking, CRM and payment services. Create new business-owned accounts and invite the developer as needed.

Supply brand assets and approved content. Name one person who approves scope, design changes and launch.

03

Developer setup and release workflow

For a typical business website, use the native Cloudflare Pages GitHub integration. Both the source repository and Pages project should live in the client environment.

Retro Forge Studios setup checklist

Accept invitations and verify the correct client GitHub organization and Cloudflare account before creating resources.

Create the project in the client repository. Add a README covering local development, builds, deployment and maintenance.

Have the client GitHub owner approve or install the Cloudflare Workers and Pages GitHub app for the selected website repository.

In the client Cloudflare account, create a Pages project connected to Git and select the client repository.

Set the framework, build command, output directory and runtime version. Explicitly set main as the production branch.

Configure branch and pull-request previews. Add required variables and secrets to the correct production or preview environment.

Test a real commit through preview review and production deployment. Document how to restore a working version.

How changes reach the live website

StepAction
1 RequestThe client describes the change and business purpose.
2 DevelopRetro Forge Studios develops with AI on a separate branch.
3 PreviewPush to GitHub. Cloudflare builds a review URL.
4 ReviewTest the result and collect approval where required.
5 PublishMerge into main. Cloudflare deploys the live website.

Agree whether every change requires approval or routine maintenance may be released under ongoing authorization. Git integration provides previews and deployment status. See reference 4.

AI and confidential information: Explain which tools receive code or content. Limit access to required repositories where supported. Keep passwords, production secrets and customer records out of prompts and source control.

04

Launch responsibilities and checks

The client approves business content and release timing. Retro Forge Studios implements and verifies the website.

TaskRetro Forge StudiosClient
Scope and designDocument scope, sitemap and implementationApprove budget, scope and design
Copy and imageryPrepare agreed material and layoutsSupply or approve accuracy and usage rights
Forms and notificationsConfigure and test real deliveryConfirm recipients and follow-up process
Quality checksTest mobile, keyboard use, accessibility and browsersReview key visitor journeys
Existing URLsMap and implement redirectsIdentify valuable existing pages
Search setupConfigure metadata, sitemap and indexingApprove business and location details
Analytics and integrationsConnect and testOwn accounts and approve access
Domain and DNSPlan and implement changesApprove timing and provide access
Go liveDeploy and verify the live websiteGive final launch approval

Domain and email continuity

Record existing DNS before changes. Preserve email records including MX, SPF, DKIM and DMARC.

Add the domain through Pages Custom domains. Confirm HTTPS and choose the preferred www or non-www address.

A Pages apex domain such as example.com requires Cloudflare nameservers. A subdomain can use external DNS with the appropriate CNAME setup. See reference 5.

Preview privacy

Protect previews containing confidential or unfinished material. Preview protection does not automatically protect production. Confirm production access separately if the site includes private content. See reference 6.

05

Maintenance and client handoff

Define the ongoing service arrangement before launch so ownership, maintenance and future changes remain clear.

Agree who handles content edits, technical updates and urgent incidents.

Specify maintenance fees, included work, revision limits and response expectations.

Record who pays subscriptions and approves upgrades or additional usage.

Document repository, hosting, domain, integration and billing locations.

Record environment-variable names and purposes. Keep secret values and recovery codes in a client-controlled password manager.

Document deployment, rollback and recovery procedures.

Back up databases, uploads and CMS content where applicable. Git history does not back up these systems automatically.

Confirm the client can invite a replacement developer without your involvement.

At the end of the engagement, remove developer access and revoke or rotate credentials issued for that work.

Suggested client agreement description

Your website source code and hosting will be held in accounts your business controls. Retro Forge Studios will receive invited access to build, launch and maintain the site. You retain account recovery, billing control and the ability to appoint another developer. Ownership and licensing of delivered work will be defined in our project agreement.

Before development begins

Convert discovery answers into an approved brief: goal, audience, sitemap, features, visual direction, content responsibilities, integrations, budget, timeline, revision allowance and launch acceptance criteria.

Official setup references

  1. GitHub repository roles ↗
  2. Cloudflare account roles ↗
  3. Cloudflare member management ↗
  4. Cloudflare Pages Git integration ↗
  5. Cloudflare custom domains ↗
  6. Cloudflare preview deployments ↗

let's get the brief right

Tell us what you're building.

Start with your contact details, then share as much as you can. Only name, email, and business name are required. You can discuss the rest with Johnny.

Project details
Where are you with account setup?

Optional. Check what is already available. It's fine if you need help with all of it.

A little discovery goes a long way.

37 optional questions, grouped to make the conversation easier. “Not sure yet” is a useful answer.

0 of 37 answered

Business fit scope and budget
Audience and messaging
Visual direction
Pages and content
Features and integrations
Existing site and launch
Project brief and next steps

Optional. Add decisions you've already made, responsibilities you've discussed, or questions we should cover together.

Your answers are emailed to Johnny at Retro Forge Studios to discuss your project. Please don't include passwords, API keys, or customer records. See our privacy policy.

This starts a conversation. It isn't a contract or permission to change your accounts.