msp-website-setup

Create a COMPANY-INFO.md brief, initialize a git repo with main and dev branches, push to your git hosting provider, then connect the repo to a static hosting platform. Pushes to dev create preview deployments; merges to main deploy to production on the client's custom domain.

The SOW should state scope, price, timeline, content responsibilities (who writes copy and supplies photos), acceptance criteria for launch, and the ownership model. No website work starts before a signed SOW under the client's MSA.

The client owns their domain, content, and site code. Registrar and hosting accounts are in the client's name with the MSP as administrator, and the repo transfers to the client or their successor at offboarding.

Yes, if the site collects any personal data through forms capturing names, emails, phone numbers, or messages. A privacy policy page must be live before launch whenever the site collects visitor information.

Stale .git lock files occur when sandboxed environments fail to unlink them; remove HEAD.lock and index.lock before retrying. Force-with-lease rejections happen when remote-tracking refs are outdated; fetch with an explicit refspec first.

The baseline is WCAG 2.1 AA intent: alt text on meaningful images, logical heading order, sufficient color contrast, and keyboard-navigable menus and forms. Check these before launch to avoid accessibility demand letters.