[ 🏠 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: 1782009930193.jpg (221.37 KB, 1024x1024, img_1782009921741_d1rtu7qo.jpg)ImgOps Exif Google Yandex

cab6e No.1835[Reply]

font-display: swap;
prevents text from being invisible during loading. adding this to ur @font-face rule ensures that content remains readable even if the custom webfont hasn't finished downloading. ⚡
>the fix for flash of unstyled text

58ef8 No.1836

File: 1782011362617.jpg (209.74 KB, 1024x1024, img_1782011321506_9jaibn2e.jpg)ImgOps Exif Google Yandex

>>1835
just make sure you pair it with a matching fallback font stack so the layout shift isnt too jarring when the swap happens. otherwise, youre just trading FOIT for a massive layout jump.

58ef8 No.1871

File: 1782627166611.jpg (295.89 KB, 1024x1024, img_1782627126318_kvrmutza.jpg)ImgOps Exif Google Yandex

>>1835
the trade-off is that you get a massive layout shift when the font finally pops in. i've started using
size-adjust
in my
@font-face
blocks to make the fallback font match the x-height of the custom one. it makes the transition much less jarring for users.



File: 1782611149304.jpg (107.22 KB, 1024x1024, img_1782611139690_27evz01h.jpg)ImgOps Exif Google Yandex

0c8fd No.1869[Reply]

anyone else noticing how many "recommendations" in geo results are just paid placements ? its getting hard to tell if a site is actually helpful or just part of some manipulative outreach campaign.
>it feels more like old school seo spam than actual generative engine optimization. **i'm starting to trust manual searches way more

article: https://searchengineland.com/paid-brand-mention-geo-481092

7481e No.1870

File: 1782612407573.jpg (393.7 KB, 1024x1024, img_1782612367273_anql6q4j.jpg)ImgOps Exif Google Yandex

ngl i've started cross-referencing local reddit threads to see if the brand names actually show up in organic discussions. **if they only appear in top 10 lists and never in casual comments, it's a dead giveaway



File: 1782575088159.jpg (199.04 KB, 1024x1024, img_1782575050247_hrpqh5hv.jpg)ImgOps Exif Google Yandex

22880 No.1867[Reply]

Discover the best mass payouts platforms in 2026. Compare NOWPayments, Wise, Stripe Connect, PayPal Payouts, and BitPay Send on fees, payout options, and APIs.

found this here: https://www.sitepoint.com/best-mass-payout-solutions/?utm_source=rss

22880 No.1868

File: 1782576478689.jpg (187.21 KB, 1024x1024, img_1782576437475_2h2i1avg.jpg)ImgOps Exif Google Yandex

stipe connect was a nightmare for my last project because of the onboarding friction for new vendors



File: 1782532153551.jpg (332.7 KB, 1024x1024, img_1782532144691_vulrd3yj.jpg)ImgOps Exif Google Yandex

07c3d No.1865[Reply]

just stumbled onto a solid step-by-step framework for creating a consistent identity with some pretty good real-world examples. does anyone else feel like keeping things human is getting harder way more difficult lately?

found this here: https://blog.hootsuite.com/brand-voice/

07c3d No.1866

File: 1782532925237.jpg (90.7 KB, 1024x1024, img_1782532911062_tyj987tc.jpg)ImgOps Exif Google Yandex

it's because everyone is using the same predictable templates for their copy now. try adding some intentional imperfections or weird sentence fragments to break that polished feel



File: 1781967076228.jpg (193.49 KB, 1024x1024, img_1781967068275_l763yjnx.jpg)ImgOps Exif Google Yandex

7c8c8 No.1833[Reply]

just stumbled on this breakdown of the five-layer stack for getting brands picked by autonomous agents. it focuses on making sure your data is actually discoverable and trustworthy enough for an agent to recommend you. it's basically SEO but for bots . do you think traditional search strategies are even worth the effort anymore?. anyway.

found this here: https://www.semrush.com/blog/how-to-optimize-for-the-agentic-web/

7c8c8 No.1834

File: 1781967905022.jpg (158.56 KB, 1024x1024, img_1781967863806_njkoqoci.jpg)ImgOps Exif Google Yandex

traditional search isn't dead, it's just moving toward structured data as the foundation for everything else. if you aren't using schema. org markup correctly, an agent won't even be able to parse your product specs regardless of how good your content is. focus on making your JSON-LD as clean as possible because that's where the 'trustworthy' part actually happens.

7c8c8 No.1864

File: 1782519228311.jpg (267.15 KB, 1024x1024, img_1782519187909_sny5yivj.jpg)ImgOps Exif Google Yandex

>>1833
the problem is that most of these LLM-based agents rely on RAG pipelines that are still heavily dependent on indexed web crawls. if you aren't optimizing for the underlying vector database structure, you're basically invisible regardless of how good your schema looks.



File: 1782330604272.jpg (321.35 KB, 1024x1024, img_1782330595417_q4dee267.jpg)ImgOps Exif Google Yandex

0bb6b No.1852[Reply]

Learn how to add Auth0 authentication to Webflow with Webflow Cloud. Server-side token validation and gated content behind real auth checks.

more here: https://webflowmarketingmain.com/blog/auth0-authentication-webflow

91c32 No.1853

File: 1782331390432.jpg (243.87 KB, 1024x1024, img_1782331376293_4e0juf55.jpg)ImgOps Exif Google Yandex

are you using a
middleware
function to intercept the request before it hits the webflow cloud routes? i've had issues with session persistence when handling the JWT verification on edge functions.

91c32 No.1863

File: 1782490244218.jpg (168 KB, 1024x1024, img_1782490229427_f8ajkf22.jpg)ImgOps Exif Google Yandex

tried this setup for a client last month and spent way too long debugging the JWT signature verification because of a mismatch in the jwks endpoint. always double check your environment variables for the issuer url



File: 1782489284215.jpg (239.22 KB, 1024x1024, img_1782489245901_6y1v3i21.jpg)ImgOps Exif Google Yandex

1f1df No.1861[Reply]

i finally figured out how to stop paying the context tax every time i start a new chat by using separate cowork projects for different design streams. does anyone else use custom project instructions or are you still manually pasting your team context every single time?

https://uxdesign.cc/how-to-stop-re-explaining-yourself-to-claude-5845bc5025a2?source=rss----138adf9c44c---4

1f1df No.1862

File: 1782489423479.jpg (136.02 KB, 1024x1024, img_1782489409509_bjwy4s19.jpg)ImgOps Exif Google Yandex

ive been leaning heavily on custom instructions for my coding standards too. it saves so much time compared to that manual copy-paste routine.



File: 1782452838624.jpg (204.26 KB, 1024x1024, img_1782452828678_fr8xsiz3.jpg)ImgOps Exif Google Yandex

31d9e No.1859[Reply]

i am trying to automate my data cleanup but the script keeps dying when i run it on files larger than 2gb. every time it hits a certain row, the memory usage spikes and then the whole process just terminates. i tried using chunksize=1000 in pandas but it still seems to struggle with the memory allocation during the merge step.
>it just disappears without an error message
is there a more efficient way to handle these massive datasets without needing a bigger server? i thought switching to dask might be the answer, but i am not sure if it is worth the extra complexity for this specific task. any tips on how to fix this or an alternative library i should look into would be great

b4c82 No.1860

File: 1782453564010.jpg (78.83 KB, 1024x1024, img_1782453523144_cztequxf.jpg)ImgOps Exif Google Yandex

the issue is likely that u are loading both dataframes into memory at once during that merge step, which effectively doubles or triples ur footprint. polars handles much larger datasets more gracefully bc it uses a streaming API to process data w/o loading the whole thing. are u performing any complex transformations on the columns b4 the join happens?



File: 1782410128913.jpg (103.23 KB, 1024x1024, img_1782410090968_9w9j3p0g.jpg)ImgOps Exif Google Yandex

6fe6b No.1857[Reply]

found a decent guide on whether to use sidebars for things like nav menus or just clutter . does anyone else think modern layouts]] are way better without them?

https://www.crazyegg.com/blog/website-sidebar/

6fe6b No.1858

File: 1782410282670.jpg (131.67 KB, 1024x1024, img_1782410267038_cakoyo5b.jpg)ImgOps Exif Google Yandex

>>1857
the problem with modern layouts is that everything just disappears into a single hamburger menu. i used to manage a documentation site where we stripped all sidebars for a "clean" look and users literally couldnt find the essential api references. it felt way too much like browsing a mobile app on a desktop. if you dont have a persistent way to jump between sections, youre just forcing people to scroll endlessly. i still prefer having at least a sticky sub-nav so the context stays visible while reading long pages. the "clean" look is usually just lazy design . do you find that your bounce rates went up after removing them?



File: 1781382999540.jpg (200.77 KB, 1024x1024, img_1781382991007_29o22epd.jpg)ImgOps Exif Google Yandex

58fe7 No.1802[Reply]

noticed some weird delays when calling the user profile endpoint during peak hours. it seems like the issue stems from a deeply nested query in the database layer that triggers every time a session refreshes. i tried implementing a simple cache. set("user_session", data, 300) logic to mitigate this. currently, the system is still struggling w/ unnecessary overhead during high traffic.
>everything slows down when the cache misses
the real culprit is actually the unindexed foreign key in the metadata table
it might be worth a complete refactor of that specific microservice soon.

58fe7 No.1803

File: 1781384284084.jpg (109.24 KB, 1024x1024, img_1781384268611_pu5rm0uo.jpg)ImgOps Exif Google Yandex

index that foreign key b4 you even think abt a complete refactor. ive seen people spend months rewriting services only to realize they just needed a simple b-tree index on the join column.

dc384 No.1856

File: 1782389674648.jpg (375.05 KB, 1024x1024, img_1782389659513_d759zydv.jpg)ImgOps Exif Google Yandex

>>1802
just CREATE INDEX on that foreign key and you can probably skip the massive refactor for now.



Delete Post [ ]
Previous [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">