mike douges✓

@douges

🏒 🇦🇺 @paper

446 Abonnements3K Abonnés10.6K Posts
  1. mike douges✓@douges
    mike douges
    RT @codrops: Our community can't get enough of @paper right now: devs are designing with their agents, and designers are shipping apps! We've fallen for it too, and it's become the tool we design with at Codrops 💙 So we gathered our favorite tutorials, tips and tools into one guide. Start here: #ai #mcp #design
    0607
  2. mike douges✓@douges
    html-in-canvas captureElementImage is incredible
    40101.1K
  3. mike douges✓@douges
    hey
    Télécharger
    Harcourt Allen @harcourttt
    the best jumpscare getting off BART
    2022700
  4. mike douges✓@douges
    yeah they're shaping up to be pretty amazing. whoever is working on them must be incredibly good looking and intelligent
    Stephen Haney @stephenhaney
    I wanted to share more about Components in @paper to help everyone plan for the upcoming launch. We've been hard at work and we have something truly next level to ship soon. 1. Components dev is going very well. We don't set hard deadlines, we're a "release it when it's good" kind of product, but I'd estimate ~1 month or so. Certainly before EOY. 2. Creating one shared world from your codebase to the canvas and back is the priority. We don't want to just repeat the abstractions from existing design tools; we want to fix the fragmented workflow between developers and designers. But we also don't want to add cognitive load or engineering concept while you're designing. Principle: designing with components should feel familiar, designer-first, and then also happen to align to your codebase effortlessly. No tool has ever pulled this off yet. 3. The initial components release will be mature and include: slots, variants with props, React in, React out, and full agent support. Components from your codebase can also run real code, so components can have logic, dates, and math. 4. Agents can read and write components quickly, accurately, and with low token usage. To your agent, components in Paper just look like React, which means they already know exactly how to use them. I'm so excited to share Paper components with the Paper community. Thanks for your patience as we do the R&D necessary to ship something next level 🙏
    4023878
  5. Stephen Haney✓@stephenhaney
    I wanted to share more about Components in @paper to help everyone plan for the upcoming launch. We've been hard at work and we have something truly next level to ship soon. 1. Components dev is going very well. We don't set hard deadlines, we're a "release it when it's good" kind of product, but I'd estimate ~1 month or so. Certainly before EOY. 2. Creating one shared world from your codebase to the canvas and back is the priority. We don't want to just repeat the abstractions from existing design tools; we want to fix the fragmented workflow between developers and designers. But we also don't want to add cognitive load or engineering concept while you're designing. Principle: designing with components should feel familiar, designer-first, and then also happen to align to your codebase effortlessly. No tool has ever pulled this off yet. 3. The initial components release will be mature and include: slots, variants with props, React in, React out, and full agent support. Components from your codebase can also run real code, so components can have logic, dates, and math. 4. Agents can read and write components quickly, accurately, and with low token usage. To your agent, components in Paper just look like React, which means they already know exactly how to use them. I'm so excited to share Paper components with the Paper community. Thanks for your patience as we do the R&D necessary to ship something next level 🙏
    651140332.5K
  6. mike douges✓@douges
    mike douges
    RT @trq212: I think most people multi-tasking with agents could benefit from slowing down most of the stuff you're doing wont really matter- what's your P0? what would it look like if you gave it your full attention?
    0411016
  7. mike douges✓@douges
    mike douges
    RT @jesper_alpacka: Tried @paper from a developer POV, made their shaders interactive and brought them to the DOM. Read the story on @codrops 👇
    0509
  8. mike douges✓@douges
    mike douges
    RT @uuuuuulala: somehow ended up in @codrops’ Developer Highlights and I’m very, very flattered 🙃
    05012
  9. mike douges✓@douges
    mike douges
    RT @oliverhamrin: Got so inspired by this post that I dropped everything to make a Paper Mono poster series. For the love of design.
    Agu Seguí @agusegui
    want to see how the whole Paper Mono launch video was made? everything is code but I didn't touch any of it here we go 🔥
    04709
  10. mike douges✓@douges
    mike douges
    RT @agusegui: want to see how the whole Paper Mono launch video was made? everything is code but I didn't touch any of it here we go 🔥
    019405
  11. mike douges✓@douges
    i wrote about this technique a few years ago for @threejs here part 2 never came though, haha
    3Dgamedev @unity3dvfx
    Getting painterly 3D anime foliage to look like Studio Ghibli instead of a noisy mess is one of the hardest challenges in Blender. 🌳🎨 @VFX_Therapy shared an in-depth breakdown by @trungduyng covering the exact workflow for painterly in in Blender.
    008451
  12. 3Dgamedev@unity3dvfx
    Getting painterly 3D anime foliage to look like Studio Ghibli instead of a noisy mess is one of the hardest challenges in Blender. 🌳🎨 @VFX_Therapy shared an in-depth breakdown by @trungduyng covering the exact workflow for painterly in in Blender.
    Télécharger
    53603.9K96.9K
  13. mike douges✓@douges
    mike douges
    RT @vladmoroz: Paper Mono! sooo excited to finally release our free and beautiful mono font it works incredibly well for design, coding, and even prose, and it’s packed with features: variable font weight, coding ligatures, duospacing (!) for long-form text, and more. sound on:
    019508
  14. mike douges✓@douges
    free the components
    101284