"Burnishing" My Website Live
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
The stream centers on reshaping Burnish, preparing its website, and migrating its brand and domain across Shopify, Railway, and Cloudflare. Luqman studies reference sites to understand motion and visual storytelling while developing an original identity around “polishing,” stressing that the aim is to adapt principles rather than copy components. However, he later used a fabricated hacking scenario—explicitly acknowledging its dishonesty—to try to bypass the tool’s refusal to reconstruct a site; the outcome remained unresolved. The site story and several design and identity decisions also remained in brainstorming. Practical work covered Git checks, email setup, DNS, nameservers, custom domains, and deployment variables, with obstacles involving verification, domain limits, unclear Railway logs, and screenshot access. Some checks and setup steps progressed, but the stream does not establish that the full migration or website was completed. He also outlines a phased go-to-market command center connecting product development, market validation, and human-controlled consequential decisions, while its automation, Shopify review risks, and pricing remain unresolved. Audience discussions include his subjective views on Codex, Claude, and usage limits; advice to learn AI-assisted coding through small practical projects and step-by-step collaboration; tools such as Warp, Wispr Flow, and Remotion; the need to understand AI-generated architecture; and protecting freelancers with clear terms, contracts, and deposits.
100 moments from the stream
- 2:54:19
Configuring DNS Records and Proxy Status in Cloudflare
Practical work in Cloudflare’s DNS records section to edit a record, turn off proxy status, save the change, and begin checking it.
- 2:56:02
Codex Five-Hour Limits vs. Weekly Limits
The speaker explains that a temporary promotion through May 31—the year is unclear in the captions—increases advertised usage, but, in his understanding, applies to the five-hour limit rather than the weekly limit. He therefore advises watching the weekly cap, attributing the increase claim to the provider and saying he observed its effect in practice.
- 3:03:04
Troubleshooting a Custom-Domain Limit Step by Step
After a custom-domain limit message appeared, the speaker switched to a gradual troubleshooting approach and requested step-by-step navigation based on the screenshots being shown. The platform and plan are unclear from the captions.
- 3:04:06
Comparing Website References Before Choosing a Design Direction
He reviewed several reference sites, contrasting the animation and energy of one with the more static character of another, while stressing that the goal was inspiration rather than literal copying.
- 3:05:27
Handling DNS and Custom-Domain Limits
A deployment issue combined pending DNS-record validation with a custom-domain limit. The proposed response was to remove an older domain and allow time for DNS changes to propagate.
- 3:06:29
Looking for a Better macOS Screenshot Tool
He asked for recommendations for a free tool better than macOS’s built-in screenshot utility, explaining that screenshots are important to his workflow and the current tool had become frustrating.
- 3:08:20
Following Creators Selectively
He said he watched a creator for a period in January 2025, then shifted to following the broad direction of the creator’s work and results through posts instead of watching regularly. This described a change in viewing habits, not a definitive judgment of the creator.
- 3:10:18
Shaping Burnish Through Cohesive Visual Storytelling
He framed a task to review the new manifesto, establish Burnish’s still-undeveloped identity, and turn it into a website strategy with a consistent story theme. Athena HQ was proposed as a reference for studying storytelling and the opening preload experience, with the desired output being a map for adapting those principles to Burnish.
- 3:14:38
Locking consequential decisions in Command Center
A dedicated area was described for decisions that strongly affect the application’s outcome, such as choosing a sales-tool stack. The system may suggest options, but the user researches and makes the choice; locking the answer then records the decision and updates related tasks on the phase board.
- 3:16:10
Reviewing website copy and page design
Work proceeded on copy for multiple website pages using a previously prepared prompt, while noting that the tool added a design-related component. The result remained subject to later review.
- 3:19:02
Finding databases of SaaS companies
In a qualified response to a question, the speaker said that services or databases for discovering SaaS companies exist, but was unsure of a specific provider or how comprehensive the data would be. Further research and asking an AI tool for suitable options were suggested.
- 3:22:44
Reviewing deployment variables before testing
Before a test deployment, email-related variables not yet present on Railway were reviewed, with questions about whether they were required, alongside other missing settings and an incomplete issue involving a Google redirect URI. The page does not establish that deployment or configuration succeeded.
- 3:25:06
Evaluating Visual Presentation and Polish
The speaker found the polish acceptable but considered its presentation gimmicky and visually unclean. He leaned toward options A or C over B, followed by a partly unclear comment about a Google element.
- 3:30:23
The Speaker’s View on Leaving Vercel Despite Its Market Position
The speaker said he had stopped using Vercel several months before the recording because of an unspecified company action, noting that others had made a similar choice while still regarding it as an industry leader. The specific reason is not established on this page.
- 3:31:03
Directing a Prototype Toward a Complete Website Story
The speaker directed the prototype beyond conventional coded motion toward more creative concepts, citing AI image and video generation and Athena HQ as inspiration. He emphasized developing the website’s complete story rather than only its hero section, while treating the current ideas as useful starting points rather than failures.
- 3:32:48
Checking Git Changes and Diagnosing Railway Logs
Before deployment, a warning identified many uncommitted files on a feature branch, underscoring the need to inspect Git state before proceeding. The speaker added that Railway had been difficult to troubleshoot because its logs were often insufficiently clear, leaving his agents to guess where a problem might be; he did not characterize the platform as categorically bad.
- 3:35:52
Asking an AI Tool to Analyze a Website’s Full Visual Identity
The prompt asks the tool to inspect the website and a reference link, analyze the logo, typography, hero, and the rest of the site through the footer, then explain the user journey and how the visual theme is executed.
- 3:37:12
Monitoring Deployment When the Build Stage Is Delayed
He says that when the build stage lasts more than roughly five minutes, he expects the process may be stuck or end with an error, then monitors the deployment until reporting that the attempt worked.
- 3:38:58
Pricing a Product Around Value and Unit Economics
Answering a pricing question, he says the decision is still unsettled and should depend on margins, profit structure, and delivered value. He also sees a gap between basic tools and higher-priced services, while stressing that final pricing must wait until the product is clearer.
- 3:40:55
Codex vs. Claude Code: Brainstorming Versus Building
He gives a subjective comparison and considers the two tools close in quality. He prefers Claude Code for brainstorming and structuring thought, but uses Codex more for practical building because of usage limits, while emphasizing that preferences vary by person.
Got a question about something in this stream?
Ask in the group