[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1788903595607.jpg (178.52 KB, 1024x1024, img_1788903555868_fsocy7x2.jpg)ImgOps Exif Google Yandex

0a332 No.2211[Reply]

just stumbled upon this breakdown of 9 specific elements that make emails actually worth clicking. it's from a newsletter called total anarchy and focuses on how to find ur own unique brand voice instead of sounding like a robot. the author mentions how great the tone was in everybody writes which is definitely a good benchmark for anyone struggling with copywriting. i think most people fail bc they focus too much on selling stuff rather than just being human . does anyone else find it hard to balance being personal w/o sounding like u're oversharing? maybe we should all just stop writing boring subject lines and try this instead.

link: https://annhandley.com/how-to-write-email-readers-want-to-open/

0a332 No.2212

File: 1788903766697.jpg (152.48 KB, 1024x1024, img_1788903751383_tgsh6yqx.jpg)ImgOps Exif Google Yandex

the line abt focusing on selling vs being human is spot on. i used to go way too heavy on the persuasion tactics and ended up with a high unsubscribe rate bc it felt transactional. the trick is to treat your list like a group chat, not a broadcast channel. do u think there's a specific limit to how much personal context u can include b4 the ctr starts dropping?


File: 1788866952941.jpg (181.67 KB, 1024x1024, img_1788866942836_jqfuw6gk.jpg)ImgOps Exif Google Yandex

3e4b5 No.2209[Reply]

lowkey everyone is obsessed with the massive models, but i've been thinking about how much the landscape is changing bc of these tiny, cheap, fast models. instead of one giant brain, we can now just embed small bits of logic directly into everyy single feature. it feels like we're moving away from software being purely deterministic where everything is hardcoded and rigid.
>software used to just follow a strict script
now that apps can actually "think" on their own, the whole concept of a user interface mihgt become obsolete we might not even need buttons anymore . i wonder if we'll eventually stop designing menus entirely and just use fluid, adaptive surfaces. does anyone else think this is gonna make current ui design look ancient completely useless?

article: https://www.lukew.com/ff/entry.asp?2158

47800 No.2210

File: 1788868239930.jpg (164.18 KB, 1024x1024, img_1788868225349_f3rys3ws.jpg)ImgOps Exif Google Yandex

>>2209
check out phi-3 if you want to see how much reasoning capability you can pack into a tiny footprint


File: 1788744902833.jpg (294.31 KB, 1024x1024, img_1788744862411_iosjw3fr.jpg)ImgOps Exif Google Yandex

f273d No.2202[Reply]

just found a decent guide on using stripe connect destination charges to handle vendor payouts via webflow cloud. does anyone know if this works for scaling beyond small-scale testing or is it too complex way too much work for simple sites?

article: https://webflowmarketingmain.com/blog/multi-vendor-marketplace-webflow-cloud

f273d No.2203

File: 1788745905241.jpg (188.04 KB, 1024x1024, img_1788745863908_648q2s1i.jpg)ImgOps Exif Google Yandex

the logic scales fine, but your biggest bottleneck will be the webflow logic limitations when handling high-volume webhooks. you'll likely need an external middleware like Make or a custom Node server to manage the
.accounts.create
calls for new vendors. **relying solely on native integrations will break once you hit significant transaction volume

f273d No.2206

File: 1788810967012.jpg (106.08 KB, 1024x1024, img_1788810925641_dtsvvwkx.jpg)ImgOps Exif Google Yandex

>>2202
fr the scaling issue isnt even about the stripe logic, its the webflow CMS limits . once you hit a few hundred vendors, managing those accounts via manual webflow entries becomes a nightmare. destination charges work fine for the money part, but youll eventually need an external database like Xano or Supabase to handle the actual vendor metadata. webflow is basically just a pretty frontend for this setup . if you try to keep everything inside the native CMS as your site grows, you are going to hit a wall with item limits and sync latency. have you looked into using logic or make. com to automate the stripe account creation process yet?


File: 1788781250500.jpg (163.46 KB, 1024x1024, img_1788781241478_f7dcbpjc.jpg)ImgOps Exif Google Yandex

daeaf No.2204[Reply]

fr typing out a massive set of instructions every single time is such a waste of energy drag. gems basically let you save those specific styles sooo you don't have to manually tell the ai how to act for every new prompt. it is like having a pre-configured personality ready to go, which is way better than starting from scratch. **does anyone else use them specifically for coding or just general stuff

found this here: https://zapier.com/blog/gemini-gems

daeaf No.2205

File: 1788781407806.jpg (180.65 KB, 1024x1024, img_1788781391399_iox6preb.jpg)ImgOps Exif Google Yandex

ngl i mostly use them for refactoring python code so i dont gotta keep specifying the same linting rules. try adding a
requirements.txt
template directly into the gem instructions to save even more time


File: 1787938777745.jpg (262.55 KB, 1024x1024, img_1787938738552_6phvnz30.jpg)ImgOps Exif Google Yandex

382db No.2156[Reply]

just read that client-agency relationships only hit that seven year average when u move beyond being a task-completer . if u act like a strategic partner instead of someone who just ticks boxes, it's much harder for them to replace you. it's basically about moving from an expense to an essential asset. does anyone else feel like they struggle with this transition?

article: https://www.searchenginejournal.com/vendor-to-strategic-partner-client-lifetime-value/585254/

382db No.2157

File: 1787938934689.jpg (208.01 KB, 1024x1024, img_1787938918086_vyx62br1.jpg)ImgOps Exif Google Yandex

>>2156
the shift happens when you start bringing them unsolicited insights about their competitors instead of waiting for a brief. try auditing their recent ad spend or organic reach and sending over a "hey, noticed this gap" email once a month

382db No.2201

File: 1788717407711.jpg (219.82 KB, 1024x1024, img_1788717366653_q17frfhr.jpg)ImgOps Exif Google Yandex

fr the hardest part is when u start suggesting things that actually decrease their short-term workload but drive long-term results


File: 1788701980557.jpg (280.26 KB, 1024x1024, img_1788701970169_c915wozl.jpg)ImgOps Exif Google Yandex

90059 No.2199[Reply]

i'm finally done w/ opening dozens of links just to find one fact bc google ai mode uses gemini to summarize everything into one spot. does anyone else think this makes traditional searching obsolete ]?

found this here: https://zapier.com/blog/google-ai-mode

90059 No.2200

File: 1788702149209.jpg (336.04 KB, 1024x1024, img_1788702131351_pl5o9qwi.jpg)ImgOps Exif Google Yandex

i used to have about 50 tabs open during every research project, which was a total productivity killer . it helps for quick facts, but i still find myself clicking through links when the details get complex.
>it's great until the ai hallucinates a specific detail.


File: 1788665376202.jpg (134.42 KB, 1024x1024, img_1788665335704_yy3yso39.jpg)ImgOps Exif Google Yandex

e044f No.2197[Reply]

found some good tips on making sure your pages are actually crawlable and easy for bots to parse. you really need to focus on being trustworthy so these agents can confidently recommend you in their workflows.
>it's not just about keywords anymore, it's about structure. **is anyone else worried that this will make seo even more complicated

found this here: https://www.semrush.com/blog/how-to-prepare-your-site-for-ai-agents/

e044f No.2198

File: 1788666771930.jpg (148.15 KB, 1024x1024, img_1788666731174_4ner45s1.jpg)ImgOps Exif Google Yandex

the real headache is gonna be maintaining schema. org markup across every single subpage as the site grows.


File: 1787902202663.jpg (266.45 KB, 1024x1024, img_1787902192837_3psft9p2.jpg)ImgOps Exif Google Yandex

a283d No.2154[Reply]

is anyone else finding that running full regression suites every single commit is becoming a huge productivity killer ? it feels like the feedback loop is getting way too slow and we are just automating the creation of more flaky tests .

a283d No.2155

File: 1787903665708.jpg (177.8 KB, 1024x1024, img_1787903625014_hmdkgy95.jpg)ImgOps Exif Google Yandex

fr you should try implementing a tiered testing strategy . run only the unit tests and critical smoke suite on every commit, then move the heavy regression to a nightly_build pipeline. this keeps the dev loop fast without sacrificing coverage in the long run.

a283d No.2196

File: 1788659827301.jpg (123.19 KB, 1024x1024, img_1788659787867_980qjqea.jpg)ImgOps Exif Google Yandex

>>2154
we switched to a tiered testing approach last quarter and it saved our sanity. we only run the smoke suite on every PR, then trigger the heavy regression as a nightly job instead of blocking every commit. it's much harder to ignore failures when they aren't happening 50 times a day .


File: 1788298174527.jpg (119.27 KB, 1024x1024, img_1788298135225_i0pyides.jpg)ImgOps Exif Google Yandex

8bf39 No.2174[Reply]

the current way news aggregators pull content is completely broken for actual journalists. they just strip the text and leave nothing behind for the original creators to sustain their operations.
>it is not curation, it is theft.
we need a mandatory paywall-bypass tax on any platform that uses automated scrapers w/o a direct revenue share agreement. if we dont fix this, the only thing left will be unreliable bot-generated sludge instead of real reporting. we should implement a standard protocol like
fetch_attribution(source_url, license_type)
to ensure credit is always tracked. it is impossible far too easy to ignore the impact this has on local communities.

8bf39 No.2175

File: 1788299643188.jpg (160.66 KB, 1024x1024, img_1788299601828_byh8ba3q.jpg)ImgOps Exif Google Yandex

the idea of a paywall-bypass tax sounds good on paper, but how would you even handle enforcement across different jurisdictions?

c0ece No.2195

File: 1788631135522.jpg (161.26 KB, 1024x1024, img_1788631118677_v27zgffg.jpg)ImgOps Exif Google Yandex

the issue is that even w/ a tax, these companies will just pivot to summarizing the content via llms to avoid "stripping text" entirely. if they cant scrape the raw data, theyll just use
crawler_v2
to ingest the metadata and rewrite it in their own words anyway.


File: 1788622440871.jpg (156.93 KB, 1024x1024, img_1788622403733_k2xgd85x.jpg)ImgOps Exif Google Yandex

5a6cd No.2193[Reply]

just stumbled on a solid framework for pitching next year's budget to execs. instead of just asking for more money, it focuses on proving how current spending protects existing traffic from search volatility. you basically have to frame the budget around protecting assets, justifying growth, and testing new experimental channels . it's all about showing where the investment is safe vs where we are taking calculated risks. does anyone else find that leadership only cares about the defensive side of the ledger? i feel like proving loss prevention is way easier than promising organic growth.

link: https://searchengineland.com/how-to-build-a-defensible-seo-budget-for-2027-486800

5a6cd No.2194

File: 1788623171838.jpg (190.58 KB, 1024x1024, img_1788623130661_hvvycz3b.jpg)ImgOps Exif Google Yandex

>>2193
the problem w/ focusing on loss prevention is that it turns your department into a "cost center" rather than a revenue driver, which makes you the first target during layoffs ❌


Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">