[{"data":1,"prerenderedAt":693},["ShallowReactive",2],{"navigation":3,"blog-page":30,"blogs":40},[4],{"title":5,"path":6,"stem":7,"children":8,"page":29},"Blog","\u002Fblog","blog",[9,13,17,21,25],{"title":10,"path":11,"stem":12},"From Mockup to Market: My End-to-End Product Design Process","\u002Fblog\u002Ffrom-mockup-to-market","blog\u002Ffrom-mockup-to-market",{"title":14,"path":15,"stem":16},"How I Built My Design System from Scratch","\u002Fblog\u002Fhow-i-built-my-own-design-system-from-scratch","blog\u002Fhow-i-built-my-own-design-system-from-scratch",{"title":18,"path":19,"stem":20},"From Mockup to Market: SolarGPT","\u002Fblog\u002Fmockup-to-market-solargpt","blog\u002Fmockup-to-market-solargpt",{"title":22,"path":23,"stem":24},"The Psychology of Color in UI Design","\u002Fblog\u002Fpsychology-of-color-in-ui-design","blog\u002Fpsychology-of-color-in-ui-design",{"title":26,"path":27,"stem":28},"The Case for Slow Design in a Fast-Paced Digital World","\u002Fblog\u002Fslow-design-in-fast-paced-digital-world","blog\u002Fslow-design-in-fast-paced-digital-world",false,{"id":31,"title":32,"body":33,"description":34,"extension":35,"links":33,"meta":36,"navigation":37,"path":6,"seo":38,"stem":7,"__hash__":39},"pages\u002Fblog.yml","Latest Articles",null,"Some of recent projects, thoughts, designs, etc.","yml",{},true,{"title":32,"description":34},"Svkn-HBEbXtM262B0BGStKW8iiD470HfeCx1OQKgw0E",[41,186,557,610,660],{"id":42,"title":18,"author":43,"body":48,"date":178,"description":179,"extension":180,"image":181,"meta":182,"minRead":183,"navigation":37,"path":19,"seo":184,"stem":20,"__hash__":185},"blog\u002Fblog\u002Fmockup-to-market-solargpt.md",{"name":44,"avatar":45},"Admin",{"src":46,"alt":47},"\u002Fnysgpt-badge.png","NYSgpt",{"type":49,"value":50,"toc":172},"minimark",[51,55,58,63,66,69,72,89,92,96,99,107,139,150,160,163,169],[52,53,54],"p",{},"Building SolarGPT has reinforced something I already suspected: the hard part of an AI product isn't the model, it's the scaffolding around it. The data sources you trust, the questions you let users ask, the agent workflow that turns prose into SQL — those decisions compound. Get them right and the product performs well, very well. Get them wrong and it does not.",[52,56,57],{},"This is a walkthrough of how SolarGPT (solar.nysgpt.com) actually came together, including the dead ends.",[59,60,62],"h2",{"id":61},"phase-1-framing-the-product","Phase 1: Framing the Product",[52,64,65],{},"The temptation with anything energy-adjacent is to build everything: rooftop solar, wholesale markets, grid , etc., all wrapped into one. It was hard to resist that urge.",[52,67,68],{},"The correct approach turned out to be a singular focus on solar first.",[52,70,71],{},"Two question, two answers:",[73,74,75,83],"ul",{},[76,77,78,82],"li",{},[79,80,81],"strong",{},"\"Should I install solar on my roof?\""," — ROI, panel counts, capacity, carbon offset. For this question slow-moving, annual averages work.",[76,84,85,88],{},[79,86,87],{},"\"What is solar generation worth?\""," — Statewide? By county? By town? Zip code? To my neighborhood? My block? That's how far we drilled down.",[52,90,91],{},"We did this to empower collective action by endusers: a civic org., school district, municipality, if one mid-sized organization looks at it's rooftops the benefits are in the tens of millions.",[59,93,95],{"id":94},"phase-2-data-architecture","Phase 2: Data Architecture",[52,97,98],{},"Before any UI work, I spent real time mapping data sources to product questions. This is the part most people skip, and that's because it's a pain in the ass, but this is the part that determines whether the agent will give a useful answer.",[52,100,101,102,106],{},"The current Postgres setup (",[103,104,105],"code",{},"solargpt"," schema):",[73,108,109,115,121,127,133],{},[76,110,111,114],{},[79,112,113],{},"KPI views"," — pre-aggregated answers to the most common rooftop questions",[76,116,117,120],{},[79,118,119],{},"NREL 2024 tables"," — NREL's scenario-based long-run electricity values",[76,122,123,126],{},[79,124,125],{},"EIA 860 \u002F 861 \u002F 930"," — plant locations, service territories, hourly grid ops",[76,128,129,132],{},[79,130,131],{},"NYISO queue data"," — interconnection pipeline, parked for Phase 2",[76,134,135,138],{},[79,136,137],{},"Project Sunroof tables"," — county\u002Fcity\u002Fpostal\u002Ftract-level rooftop potential",[52,140,141,142,145,146,149],{},"A specific lesson that cost me a half-day: EIA's ",[103,143,144],{},"facility-fuel"," endpoint has generation time-series but no lat\u002Flon. The Plant file from EIA-860 has lat\u002Flon but no generation. To do anything map-shaped you have to join them on ",[103,147,148],{},"plant_code",". GridStatus does this; so now does SolarGpt.",[52,151,152,153],{},"Similarly for balancing authority polygons — county dissolution from EIA-861 service territory data technically works, but the DOE ArcGIS FeatureServer publishes the 71 BA polygons directly in WGS84 GeoJSON with no auth required. One query string and you're done: ",[154,155,159],"a",{"href":156,"rel":157},"https:\u002F\u002Farcgis.netl.doe.gov\u002Fserver\u002Frest\u002Fservices\u002FHosted\u002FControl__Areas\u002FFeatureServer\u002F0\u002Fquery?where=1%3D1&outFields=*&outSR=4326&f=geojson",[158],"nofollow","ArcGIS",[52,161,162],{},"That's a start. We'll disclose more on the AI Layer later, but for now I'd leave you with this:",[164,165,166],"blockquote",{},[52,167,168],{},"AI products live or die on the boring infrastructure underneath the chat box. The model is the easy part now. Picking the right data, shaping the right workflow, and saying no to the wrong scope — that's work.",[52,170,171],{},"More to come...",{"title":173,"searchDepth":174,"depth":174,"links":175},"",2,[176,177],{"id":61,"depth":174,"text":62},{"id":94,"depth":174,"text":95},"2026-05-13","A detailed breakdown of how I'm building SolarGPT — from data architecture decisions to agent workflows to spec-driven design — with the tradeoffs and course-corrections along the way.","md","\u002Fgea-regions.avif",{},8,{"title":18,"description":179},"gHb8hi78MYMLQybiZbtyEsHLY5GuEmQZowxwiGlx9DA",{"id":187,"title":10,"author":188,"body":192,"date":551,"description":552,"extension":180,"image":553,"meta":554,"minRead":183,"navigation":37,"path":11,"seo":555,"stem":12,"__hash__":556},"blog\u002Fblog\u002Ffrom-mockup-to-market.md",{"name":189,"avatar":190},"Emma Thompson",{"src":191,"alt":189},"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1701615004837-40d8573b6652?q=80&w=1480&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D",{"type":49,"value":193,"toc":520},[194,197,200,204,207,212,215,220,224,227,231,234,245,249,252,256,259,263,266,293,297,300,326,330,333,337,340,344,347,358,362,365,376,380,383,394,398,401,405,408,422,426,429,443,447,450,454,457,461,464,468,471,475,478,489,493,496,507,510,514,517],[52,195,196],{},"Creating successful digital products isn't about following a rigid formula—it's about developing a flexible framework that adapts to the unique challenges of each project. After refining my approach across dozens of products, I've developed a process that consistently delivers results while leaving room for creativity and iteration.",[52,198,199],{},"In this article, I'll walk through my end-to-end design process, from initial discovery to developer handoff, using my recent work on the EcoTrack application as a case study.",[59,201,203],{"id":202},"phase-1-discovery-research","Phase 1: Discovery & Research",[52,205,206],{},"Every great product starts with understanding the problem it's trying to solve. For EcoTrack, our challenge was creating an engaging way for users to track their environmental impact without feeling overwhelmed by guilt or complex data.",[208,209,211],"h3",{"id":210},"user-interviews","User Interviews",[52,213,214],{},"I began by conducting interviews with 12 potential users across different demographics, focusing on their current habits and attitudes toward sustainability. These conversations revealed a crucial insight: most people wanted to make environmentally friendly choices but felt paralyzed by the complexity of calculating their impact.",[164,216,217],{},[52,218,219],{},"\"I care about the environment, but I have no idea if using a paper bag is actually better than plastic, or if my reusable water bottle makes any difference.\" — Interview participant",[208,221,223],{"id":222},"competitive-analysis","Competitive Analysis",[52,225,226],{},"Next, I analyzed existing sustainability apps, creating a feature comparison matrix to identify gaps and opportunities. Most competitors focused on carbon footprint calculations but failed to provide actionable guidance or positive reinforcement.",[208,228,230],{"id":229},"defining-success","Defining Success",[52,232,233],{},"Before opening Figma, I collaborated with stakeholders to define clear success metrics:",[73,235,236,239,242],{},[76,237,238],{},"Increase daily active usage by 40%",[76,240,241],{},"Improve user-reported understanding of environmental impact",[76,243,244],{},"Drive measurable behavior changes in at least two sustainability categories",[59,246,248],{"id":247},"phase-2-ideation-conceptualization","Phase 2: Ideation & Conceptualization",[52,250,251],{},"With a solid understanding of the problem space, I moved into the creative phase of the process.",[208,253,255],{"id":254},"sketching","Sketching",[52,257,258],{},"I always start with pen and paper, rapidly exploring different approaches without the constraints of digital tools. For EcoTrack, I filled three sketchbooks with concepts ranging from gamified experiences to data-heavy dashboards.",[208,260,262],{"id":261},"information-architecture","Information Architecture",[52,264,265],{},"Based on research insights, I developed a user-centered information architecture that prioritized simplicity and actionable information:",[267,268,269,275,281,287],"ol",{},[76,270,271,274],{},[79,272,273],{},"Dashboard"," — Personalized overview with immediate impact insights",[76,276,277,280],{},[79,278,279],{},"Daily Tracker"," — Simple logging of activities with immediate feedback",[76,282,283,286],{},[79,284,285],{},"Impact Journey"," — Visualization of progress over time",[76,288,289,292],{},[79,290,291],{},"Action Center"," — Customized recommendations based on user behavior",[208,294,296],{"id":295},"design-principles","Design Principles",[52,298,299],{},"I established four core design principles to guide all decisions:",[73,301,302,308,314,320],{},[76,303,304,307],{},[79,305,306],{},"Simplify complexity"," — Translate environmental impact into understandable units",[76,309,310,313],{},[79,311,312],{},"Celebrate progress"," — Focus on positive reinforcement rather than guilt",[76,315,316,319],{},[79,317,318],{},"Enable informed choices"," — Provide context for decision-making",[76,321,322,325],{},[79,323,324],{},"Design for habit formation"," — Create satisfying interaction loops",[59,327,329],{"id":328},"phase-3-prototyping-testing","Phase 3: Prototyping & Testing",[52,331,332],{},"With the conceptual framework in place, I moved into the iterative cycle of prototyping and testing.",[208,334,336],{"id":335},"low-fidelity-wireframes","Low-Fidelity Wireframes",[52,338,339],{},"I created wireframes focusing on user flows and information hierarchy, deliberately keeping the visual design minimal to focus feedback on functionality and structure.",[208,341,343],{"id":342},"user-testing-round-1","User Testing (Round 1)",[52,345,346],{},"Testing wireframes with 8 participants revealed several key insights:",[73,348,349,352,355],{},[76,350,351],{},"Users wanted more immediate feedback when logging activities",[76,353,354],{},"The impact visualization wasn't intuitive for most users",[76,356,357],{},"People were confused by technical environmental terminology",[208,359,361],{"id":360},"mid-fidelity-prototypes","Mid-Fidelity Prototypes",[52,363,364],{},"Based on testing feedback, I refined the concept and developed interactive prototypes with more visual detail, focusing on:",[73,366,367,370,373],{},[76,368,369],{},"Simplified data visualization using familiar metaphors",[76,371,372],{},"Immediate positive reinforcement for logged activities",[76,374,375],{},"Progressive disclosure of more complex environmental information",[208,377,379],{"id":378},"user-testing-round-2","User Testing (Round 2)",[52,381,382],{},"A second round of testing showed significant improvements in usability, but highlighted new challenges:",[73,384,385,388,391],{},[76,386,387],{},"Users wanted to compare their impact with friends or community averages",[76,389,390],{},"Weekly summaries were more motivating than daily statistics",[76,392,393],{},"The onboarding process felt too lengthy",[59,395,397],{"id":396},"phase-4-visual-design-refinement","Phase 4: Visual Design & Refinement",[52,399,400],{},"With the core experience validated, I moved into high-fidelity visual design.",[208,402,404],{"id":403},"visual-language","Visual Language",[52,406,407],{},"I developed a visual language that balanced approachability with credibility:",[73,409,410,413,416,419],{},[76,411,412],{},"A nature-inspired color palette with clear functional color coding",[76,414,415],{},"Custom iconography that simplified complex concepts",[76,417,418],{},"Typography that prioritized readability across devices",[76,420,421],{},"Micro-interactions that provided satisfaction and reinforcement",[208,423,425],{"id":424},"design-system","Design System",[52,427,428],{},"To ensure consistency and facilitate development, I created a comprehensive design system including:",[73,430,431,434,437,440],{},[76,432,433],{},"Component library with documented states and behaviors",[76,435,436],{},"Responsive layout guidelines",[76,438,439],{},"Animation specifications",[76,441,442],{},"Accessibility standards",[208,444,446],{"id":445},"final-prototype","Final Prototype",[52,448,449],{},"The final prototype brought together all elements into a cohesive experience, which we tested with a broader user group before moving to development.",[59,451,453],{"id":452},"phase-5-implementation-iteration","Phase 5: Implementation & Iteration",[52,455,456],{},"The design process doesn't end when development begins—it evolves.",[208,458,460],{"id":459},"developer-collaboration","Developer Collaboration",[52,462,463],{},"I worked closely with developers throughout implementation, participating in code reviews and adjusting designs to address technical constraints while preserving the core experience.",[208,465,467],{"id":466},"analytics-implementation","Analytics Implementation",[52,469,470],{},"We integrated analytics to track our success metrics, setting up dashboards to monitor key interactions and user journeys.",[208,472,474],{"id":473},"post-launch-iteration","Post-Launch Iteration",[52,476,477],{},"After launch, we established a regular cycle of analysis and iteration:",[73,479,480,483,486],{},[76,481,482],{},"Weekly reviews of user feedback and behavior data",[76,484,485],{},"Bi-weekly design sprints to address emerging issues",[76,487,488],{},"Monthly feature planning based on usage patterns",[59,490,492],{"id":491},"results-learnings","Results & Learnings",[52,494,495],{},"Six months after launch, EcoTrack has exceeded our initial success metrics:",[73,497,498,501,504],{},[76,499,500],{},"52% increase in daily active usage",[76,502,503],{},"78% of users report better understanding of their environmental impact",[76,505,506],{},"Average user has adopted 3.4 new sustainable habits",[52,508,509],{},"The most valuable lesson from this project was the importance of making abstract concepts tangible. By translating complex environmental data into personal, actionable insights, we created an experience that not only educated users but empowered them to make meaningful changes.",[59,511,513],{"id":512},"conclusion","Conclusion",[52,515,516],{},"Effective product design is never a linear journey—it's a continuous cycle of learning and refinement. By staying focused on user needs while maintaining a flexible approach to problem-solving, we can create products that not only meet business objectives but genuinely improve people's lives.",[52,518,519],{},"I'd love to hear about your own design process and how you approach similar challenges. Feel free to reach out with questions or share your experiences in the comments below.",{"title":173,"searchDepth":174,"depth":174,"links":521},[522,528,533,539,544,549,550],{"id":202,"depth":174,"text":203,"children":523},[524,526,527],{"id":210,"depth":525,"text":211},3,{"id":222,"depth":525,"text":223},{"id":229,"depth":525,"text":230},{"id":247,"depth":174,"text":248,"children":529},[530,531,532],{"id":254,"depth":525,"text":255},{"id":261,"depth":525,"text":262},{"id":295,"depth":525,"text":296},{"id":328,"depth":174,"text":329,"children":534},[535,536,537,538],{"id":335,"depth":525,"text":336},{"id":342,"depth":525,"text":343},{"id":360,"depth":525,"text":361},{"id":378,"depth":525,"text":379},{"id":396,"depth":174,"text":397,"children":540},[541,542,543],{"id":403,"depth":525,"text":404},{"id":424,"depth":525,"text":425},{"id":445,"depth":525,"text":446},{"id":452,"depth":174,"text":453,"children":545},[546,547,548],{"id":459,"depth":525,"text":460},{"id":466,"depth":525,"text":467},{"id":473,"depth":525,"text":474},{"id":491,"depth":174,"text":492},{"id":512,"depth":174,"text":513},"2025-04-23","A detailed breakdown of my iterative design methodology, from initial research to final handoff, with practical tips for designers at every stage.","https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F1050312\u002Fpexels-photo-1050312.jpeg?auto=compress&cs=tinysrgb&w=1260&h=750&dpr=1",{},{"title":10,"description":552},"CDWNWgtx3hCIt749zuw2sfgA2mN5rNXUtBLTjjH0nz4",{"id":558,"title":22,"author":559,"body":561,"date":603,"description":604,"extension":180,"image":605,"meta":606,"minRead":607,"navigation":37,"path":23,"seo":608,"stem":24,"__hash__":609},"blog\u002Fblog\u002Fpsychology-of-color-in-ui-design.md",{"name":189,"avatar":560},{"src":191,"alt":189},{"type":49,"value":562,"toc":601},[563,566,569,572,575,578,595,598],[52,564,565],{},"Color is one of the most powerful tools in my design arsenal, yet I find it's often reduced to mere aesthetics or brand guidelines. After conducting a series of A\u002FB tests for the Wavelength music app redesign, I've gathered some fascinating insights about how color psychology directly impacts user behavior.",[52,567,568],{},"When we initially launched the app, we used a vibrant purple as our primary action color. The color looked great with our brand palette, but our conversion metrics were underwhelming. On a hunch, I proposed testing different primary colors while keeping all other elements identical.",[52,570,571],{},"The results were striking: switching to a specific shade of blue increased our call-to-action conversion by 34%. Even more interesting was how different user segments responded to color variations—younger users engaged more with vibrant tones, while our 35+ demographic showed stronger preference for more subdued colors.",[52,573,574],{},"Beyond conversion metrics, I discovered that color significantly affected how users perceived waiting times. By implementing a softer color progression in our loading animations, users reported that the app felt faster, even though the actual loading times remained unchanged.",[52,576,577],{},"I've since developed a framework for color decision-making that goes beyond aesthetics:",[267,579,580,583,586,589,592],{},[76,581,582],{},"Consider the emotional response you want to evoke",[76,584,585],{},"Test color choices with your specific user demographics",[76,587,588],{},"Use color to create visual hierarchies that guide users naturally",[76,590,591],{},"Consider cultural associations of colors for international audiences",[76,593,594],{},"Ensure sufficient contrast for readability and accessibility",[52,596,597],{},"The most valuable lesson I've learned is that there are no universal \"right\" colors—only colors that effectively communicate your message and guide users toward their goals within your specific context.",[52,599,600],{},"Next time you're selecting a color palette, think beyond what looks good and consider what your colors are actually saying to your users.",{"title":173,"searchDepth":174,"depth":174,"links":602},[],"2025-03-15","Exploring how strategic color choices can influence user behavior, evoke emotions, and enhance the overall user experience of digital products.","https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F40799\u002Fpaper-colorful-color-loose-40799.jpeg?auto=compress&cs=tinysrgb&w=1260&h=750&dpr=1",{},5,{"title":22,"description":604},"fN5DAgIRMQc3gJh92rH6lK6TjZLKEQivx8hu2JR3VJI",{"id":611,"title":14,"author":612,"body":614,"date":653,"description":654,"extension":180,"image":655,"meta":656,"minRead":657,"navigation":37,"path":15,"seo":658,"stem":16,"__hash__":659},"blog\u002Fblog\u002Fhow-i-built-my-own-design-system-from-scratch.md",{"name":189,"avatar":613},{"src":191,"alt":189},{"type":49,"value":615,"toc":651},[616,619,622,625,628,642,645,648],[52,617,618],{},"After years of starting each project with a blank Figma file, I finally took the plunge and created my own comprehensive design system. The process was both challenging and incredibly rewarding, and I wanted to share my approach for other designers considering the same journey.",[52,620,621],{},"I started by auditing five of my recent projects, identifying common patterns and components that appeared across different designs. This revealed inconsistencies in my work that I hadn't noticed before—seven slightly different button styles, inconsistent spacing rules, and text styles that varied without clear purpose.",[52,623,624],{},"Rather than creating a rigid system upfront, I built it iteratively through a real client project. For the EcoTrack app, I documented each component as I designed it, creating a living system that evolved with the project's needs.",[52,626,627],{},"The core of my system includes:",[73,629,630,633,636,639],{},[76,631,632],{},"A flexible color system with semantic naming conventions",[76,634,635],{},"Typography scales based on the golden ratio",[76,637,638],{},"Component variants with clear usage guidelines",[76,640,641],{},"Spacing and layout rules that maintain consistency across devices",[52,643,644],{},"The biggest challenge wasn't technical but psychological—learning to trust the system instead of reinventing solutions for each new problem. But the payoff has been enormous: my design process is now 40% faster, client revisions have decreased significantly, and handoff to development is much smoother.",[52,646,647],{},"If you're considering building your own system, my advice is to start small with core elements, test them on real projects, and document as you go. A good design system should feel like a trusted collaborator, not a set of restrictions.",[52,649,650],{},"I've attached a template of my component documentation method below—feel free to adapt it for your own workflow!",{"title":173,"searchDepth":174,"depth":174,"links":652},[],"2025-03-05","A practical guide to creating your own design system, from initial audit to implementation, and the lessons learned along the way.","https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F196644\u002Fpexels-photo-196644.jpeg?auto=compress&cs=tinysrgb&w=1260&h=750&dpr=1",{},6,{"title":14,"description":654},"v4KwBTVJ90ic2ZwJ_5bpusUulPf4DMyWsNxXMwW-oUQ",{"id":661,"title":26,"author":662,"body":664,"date":686,"description":687,"extension":180,"image":688,"meta":689,"minRead":690,"navigation":37,"path":27,"seo":691,"stem":28,"__hash__":692},"blog\u002Fblog\u002Fslow-design-in-fast-paced-digital-world.md",{"name":189,"avatar":663},{"src":191,"alt":189},{"type":49,"value":665,"toc":684},[666,669,672,675,678,681],[52,667,668],{},"I recently took on a project that challenged everything about my usual design process. A small literary journal wanted a digital platform that encouraged readers to slow down and engage deeply with content—the exact opposite of most websites optimized for quick consumption.",[52,670,671],{},"This got me thinking about what I'm calling \"slow design\"—an approach that intentionally creates space for contemplation rather than rapid interaction.",[52,673,674],{},"For the Wordsmith Journal, I experimented with subtle animations that respond to reading pace, typography that encourages focus, and navigation that reveals content gradually rather than all at once. The result feels more like turning pages in a physical book than scrolling through a typical website.",[52,676,677],{},"User testing revealed something fascinating: readers spent 3x longer with articles and reported higher satisfaction and better recall of content compared to the journal's previous site. By designing for attention rather than distraction, we created a digital experience that honors the thoughtful nature of the content itself.",[52,679,680],{},"I'm now incorporating elements of slow design into all my projects, asking: \"Where can we create moments of pause? How can we reward attention rather than just capturing it?\"",[52,682,683],{},"In our rush to optimize for engagement metrics, I think we've forgotten that sometimes the most meaningful digital experiences are the ones that don't demand immediate action but instead create space for thought.",{"title":173,"searchDepth":174,"depth":174,"links":685},[],"2025-01-28","Why designing digital experiences that encourage users to slow down and engage deeply can lead to more meaningful interactions and better outcomes.","https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F4050314\u002Fpexels-photo-4050314.jpeg?auto=compress&cs=tinysrgb&w=1260&h=750&dpr=1",{},7,{"title":26,"description":687},"9OTFhmAzfBv-1QHV4dF2dlp66O1Hbpnr3OvsEco7dGc",1778733315911]