The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A JavaScript bug that isn't JavaScript
Found this in a .cshtml file a plain JS comment causing the view to gave a syntax error.
// reports.css @media print
CSC : error RZ1006: The name 'media' does not exist in the current context
πͺπ΅π: Razor scans the whole .cshtml file for @ β even inside // comments β and tries to parse @media as C#.
ππΆπ
: escape it as @@media. Renders as a single @, builds clean.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic π
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Figma to Framer hero section developmentπ§©
Would you like me to show you how your design could look as a fully developed website in Framer?
Design is not mine, credits to @_heyfaisal (on X/twitter)
Nice
Process - Page for a Creative Director & Producer's Website in NYC. Still working through the ways to share her creative skills and professional producer skills in a visual format that reflects here process and portrays the level of unique creative talent she has.
That collage layout with the torn-paper textures makes a "process" page feel like part of her creative work instead of a dry behind-the-scenes explainer. What's been trickiest, picking which artifacts to show, or keeping that loose scrapbook feel from tipping into looking messy?
β’ Sep 1
Every creative pro has some "final_v2_client_approved_remastered" file sitting somewhere on their machine. We've been building Clustta for about three years now to make that file (and the ten versions before it) a thing of the past.
The goal was simple: build an artist-friendly collaboration, version control, and asset management tool we love, and one we hope you'll love too.
Most of the challenge was in blurring the lines between technical version control platforms like GitHub and everyday file-sharing apps like Google Drive, so it feels both fresh and familiar to users coming from either camp. That meant constantly figuring out what features to add, where they belonged in the UI, and so on.
Clustta is open source, is available for general use now, and still very much in active development, so I'll be sharing updates here as we keep building π€
More updates and case studies coming soon.
β’ Sep 1
The real problem here is diffing and storage for binary assets, a 200MB PSD that changed one layer shouldn't cost 200MB every save. Content-defined chunking gets you most of the way. Merge is the other wall, two artists on one file with no text to three-way merge means you're building lock or branch-and-review, not git.