Welcome to the first post on Newby Stack! This article documents the step-by-step process I followed to build and deploy this site - from using Google Gemini to assist with initial planning and code generation, to hands-on editing of the HTML and CSS to my preferred specifications in Notepad++, serving as a procedural guide for setting up a custom, accessible static website on GitHub Pages.
Step 1: Brand Positioning & Naming Strategy
- Prompted Google Gemini for domain ideas incorporating my surname, Newby. Selected
newbystack.com, which is a nod to my technology stack (Oracle, PeopleSoft, Power BI, Jira, SQL, SharePoint, etc.). - Uploaded a skills matrix and nine resume iterations over the last 3 years to determine site content and structuring.
- Generated positioning statements to validate the tone and created the initial "N" and "S" logo mark.
- Refined the core branding concept from "Enterprise Architecture" to Holistic Workflow Architecture to better describe my focus on bridging comprehensive functional and technical enterprise solutions.
Step 2: Scaffolding & Front-End Setup
- Purchased
newbystack.comon GoDaddy and requested step-by-step instructions to build local HTML and CSS files. - Opted for GitHub Pages over traditional paid hosting to maintain a zero-cost, high-performance static architecture.
- Created local site files and edited them in Notepad++, using "Preview HTML" to test layout changes prior to deployment.
Step 3: Visual Polish & Accessibility Optimization
- Redesigned the site styling and color palette around the logo's dark navy and blue visual scheme.
- Implemented full ADA / WCAG accessibility standards across all page elements.
- Replaced the default header image with a Hybrid Logo + HTML Typography layout for clean, responsive scaling.
- Updated the experience page to ensure all historical roles and software platforms were fully represented.
Step 4: Repository Setup & Deployment
- Created a GitHub account and a new public repository.
- Uploaded local HTML and CSS assets directly to the repository and enabled GitHub Pages in site settings.
Step 5: Custom Domain & DNS Troubleshooting
- Mapped the custom domain in GitHub Pages settings.
- Encountered the "Enforce HTTPS - Unavailable for your site because your domain is not properly configured to support HTTPS" error.
- Inspected GoDaddy DNS settings and identified a conflicting 5th "Parked" A record alongside GitHub's four IP addresses.
- Deleted the parked record, allowing Let's Encrypt to verify domain ownership and successfully issue the SSL certificate.