Skip to content
شغّال
Back to the library

"Burnishing" My Website Live

Day 0324:33:25

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.

  • website
  • web design
  • reference sites
  • branding
  • +4

100 moments from the stream

  1. 0:04:10

    Building the Website from Reference Sites

    The speaker proposed studying and recreating three reference websites as starting points after seeing that a site could be reproduced quickly, then designing his own site and adapting the details to his brand.

    • website
    • web design
    • reference sites
    • branding
    • +1
  2. 0:06:37

    A Temporary Codex Usage-Limit Promotion

    The speaker explained that, as he understood it, a temporary promotion raised Codex usage limits tenfold until May 31, 2026, after which the limits were expected to return to normal.

    • Codex
    • usage limits
    • tokens
    • promotion
  3. 0:08:25

    Planning the Move to Burnish and Railway

    The speaker identified the need for a comprehensive plan to change the previous brand name to Burnish, move from Shopify to Railway, and update the website and project name accordingly.

    • rebranding
    • migration
    • Railway
    • Shopify
    • +1
  4. 0:09:24

    An Opinion on Claude Compared with Codex

    The speaker discussed Claude's restrictive usage experience and expected competition to encourage improvements. After trying Claude and Codex on a similar exercise, he expressed a personal preference for Claude's interaction quality and said it was difficult to replace completely.

    • Claude
    • Codex
    • AI coding tools
    • usage limits
    • +1
  5. 0:11:33

    Safely Renaming a Brand in an Existing Project

    Explains the move to the Burnish name while postponing palette and typography changes, and carefully updating the metafield namespace and other brand-name references without breaking the backend.

    • rebranding
    • brand-name
    • codebase
    • metafields
    • +1
  6. 0:13:37

    Getting Started with AI-Assisted Coding Using Codex

    Advice for a beginner to install Codex, ask it to build a small useful personal project, and repeat that process before progressing to ideas that could help a wider community.

    • Codex
    • vibe-coding
    • beginners
    • AI-coding
    • +1
  7. 0:17:58

    Working with a Coding Assistant Step by Step

    Suggests treating Codex as an interactive assistant: explain the goal, ask what information it needs, and work through the task together step by step. Paid access is framed as an investment to assess against expected usefulness or return, without assuming it suits everyone.

    • Codex
    • prompting
    • guided-workflow
    • AI-coding
    • +1
  8. 0:19:03

    A Qualitative Comparison of Claude and Codex Usage Limits

    The speaker describes using Claude to plan a brand-name change and feels that usage allowances can be consumed quickly by this kind of work. He compares its practical cost with Codex while acknowledging Claude’s strong performance; these are personal impressions, not a benchmark.

    • Claude
    • Codex
    • usage-limits
    • AI-coding
    • +1
  9. 0:21:36

    Warp as a Multi-Terminal Environment for Agentic Development

    The speaker describes Warp as an environment for opening multiple terminals and running different coding tools or agents against the same project, which he finds useful for multitasking. He also notes that it can be downloaded for free, with additional plans available.

    • Warp
    • terminal
    • agentic development
    • multitasking
    • +1
  10. 0:24:49

    An Opinion on Claude Pricing and Usage Limits Compared with Codex

    The speaker argues that Claude’s $20-per-month plan at the time of the recording might be insufficient for token-intensive coding and advises the questioner to consider Codex instead. This is his historically situated opinion about the pricing and limits mentioned then, not a comparative test.

    • Claude
    • Codex
    • pricing
    • usage limits
    • +1
  11. 0:25:55

    Organizing Reference Sites to Study Design and Motion

    The speaker proposes rebuilding several websites inside the repository as study references, aiming to understand their structure, details, and animations rather than relying on screenshots alone. The stated goal is to draw inspiration from those references and then adapt the direction to fit the brand, while the organization and implementation approach remain under discussion and experimentation.

    • web design
    • landing page
    • reference implementation
    • animation study
    • +2
  12. 0:31:37

    Studying Reference Sites to Build an Original Design

    The speaker discusses bringing reference sites into a repository to understand their structure, motion, and implementation details, then using those lessons to create his own version. He frames this as an experiment whose ease and token usage still need evaluation, not as an already proven success.

    • web design
    • reference analysis
    • animations
    • AI coding
  13. 0:35:05

    Preferring Codex over Claude for Website Building

    The speaker says he prefers using Codex for website building and finds part of Claude’s interface frustrating; this is a personal preference, not a tested comparison.

    • Codex
    • Claude
    • website building
    • tool preference
  14. 0:36:12

    Agent File Placement and Token Usage

    Responding to an audience question, he tentatively recommends keeping agents and MCP configuration in the project folder while stressing that he does not have a definitive answer and that placement should suit the workflow. He also gives a general warning to watch token usage.

    • AI agents
    • MCP
    • project structure
    • token usage
  15. 0:37:15

    A Pricing Page That Feels Interactive

    The speaker admires a site whose pricing-section motion makes browsing feel closer to a game. He plans to study several sites in his field to assess how easily their ideas can be reimplemented and how much token usage that may require.

    • pricing page
    • interaction design
    • motion design
    • web inspiration
    • +1
  16. 0:37:54

    Programmatic Marketing Video with Remotion

    He discusses a marketing video started with a Remotion plugin in Codex, postponing final polish because the brand name may change. He also relays others’ opinion that a Claude-related design tool may be better for video and says he intends to try it, without claiming a result.

    • Remotion
    • marketing video
    • programmatic video
    • Codex
    • +1
  17. 0:40:04

    Expanding a Command Center with a Go-to-Market Plan

    He explains that the GitHub-hosted command-center version has become a customizable starting point and that he added a go-to-market section covering marketing phases and tasks. He distinguishes relatively straightforward agent-assisted site building from marketing, which he considers broader hands-on work requiring foundational setup and actions beyond coding.

    • go-to-market
    • marketing workflow
    • GitHub
    • AI agents
    • +2
  18. 0:41:38

    A Command Center for Marketing and Market Validation

    The speaker describes a command-center concept where an agent turns a marketing goal into steps and tasks, adjusts the plan after important decisions, and supports content for several channels. The proposed dashboard would combine traffic, search, and marketing-value signals, using market response to decide whether to proceed, revise the offer, or defer spending.

    • marketing strategy
    • AI agents
    • command center
    • analytics
    • +2
  19. 0:45:26

    Morning Exercise as a Possible Productivity Routine

    The speaker discusses trying morning exercise, relaying a claim he has heard that it may help someone begin work feeling fresher and more productive. He presents it as a personal goal and possible routine, not a tested conclusion.

    • morning exercise
    • routine
    • productivity
    • wellbeing
  20. 0:47:51

    Reviewing Git Ignore Rules Before the Website Build

    The speaker asks the agent to explain why the existing landing-page directory is being ignored aggressively, clarify what relaxing the ignore rules for the drafts path means, and then recommend an approach before work continues.

    • Git
    • gitignore
    • repository setup
    • website development

Got a question about something in this stream?

Ask in the group