Wow! This looks awesome. After signing up and playing around with it; I can actually see this fitting in to my real workflows. I see you guys have integrations coming soon, and the only request I would have is Asana support.
Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
11–20 of 39 posts
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#12Nicely put. It's been a while since I saw a product so nicely curated.
Well done.
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#13Nicely put. It's been a while since I saw a product so nicely curated. Well done.
Thanks! Let us know if there is anything we can do to make it better :)
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#14Wow! This looks awesome. After signing up and playing around with it; I can actually see this fitting in to my real workflows. I see you guys have integrations coming soon, and the only request I would have is Asana support.
Glad to hear that!
Just added that to our backlog :) Wondering how you envision those changes within Toybox being displayed/integrated in Asana?
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#15Your hn demo is super interesting. It would be cool to see designers fix popular websites ( cough reddit) and then be able to release those changes to the public.
Replying to myself -
It would actually be excellent "tool/side-project marketing" (like unsplash.com was for crew.co). If you set up a demo page like that, gave access to certain designers, and let them use your tool for free to showcase their redesigns of major sites.
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#16Wow this is really neato! Often times, I find myself not only changing CSS, but editing the HTML. Does that work in Toybox?
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#17Your hn demo is super interesting. It would be cool to see designers fix popular websites ( cough reddit) and then be able to release those changes to the public.
Replying to myself - It would actually be excellent "tool/side-project marketing" (like unsplash.com was for crew.co). If you set up a demo page like that, gave access to certain designers, and let them use your tool for free to showcase their redesigns of major sites.
Yea that is awesome. Definitely going to set that up! Thanks so much :)
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#18Wow this is really neato! Often times, I find myself not only changing CSS, but editing the HTML. Does that work in Toybox?
At the moment, our WYSIWYG allows you to edit the CSS properties of any element. The only HTML element you can edit via Toybox at the moment is changing text.
Would love to hear how you'd envision editing the HTML? Wondering what types of edits you're currently making to the HTML via the console?
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#19This is cool and solves some of the issues around staying organized when creating a final polish punchlist that come up, even when I'm doing the design and dev myself :-).
Couple thoughts -
When adding a new comment, I was surprised that mine became "1" which reflowed all the numbers. Seems like it would be helpful to append the comments so that the numbers stayed static.
Also, it would be neat if I could change the styles of all the similar elements at the same time. For example, when editing the .storylink class, it would be neat if I could choose to edit all similar elements or just that specific instance (like I can in the normal inspector). That would make it easier to preview my changes and make what I am trying to change clearer to the developer.
Another feature this brought to mind would be a way to preview all the colors in use on the page, kind of reverse engineering SCSS color variables. That way a designer could preview what changing orange --> green across all uses might look like before committing to it. The designer could also suggest a new color be added to the palette. In a dream world, this would also work for all font styles in use. Basically creating a reverse style sheet so you could see and consolidate minor differences. Maybe this is what you mean by style and component linting?
Finally, it would be cool to have "versions" or "groups" of the edits. We often debate whether we should go one direction or another, and being able to flip between a few options without fully coding a solution would be neat.
Cool project and good work!
Re: Launch HN: Toybox (YC S18) – Communicate changes to sites without writing code
#20This is cool and solves some of the issues around staying organized when creating a final polish punchlist that come up, even when I'm doing the design and dev myself :-). Couple thoughts - When adding a new comment, I was surprised that mine became "1" which reflowed all the numbers. Seems like it would be helpful to append the comments so that the numbers stayed static. Also, it would be neat if I could change the…
1. Can't agree more with the numbering issue. We're going to be fixing that ASAP :)
2. We're currently working on adding the ability to edit just one element or all that are associated with that class. Should be live in a few days!
3. Yes and yes. We're super interested in this idea as well. We've been testing out showing all the style elements in use on any given page ( i.e. on this page you're using these 5 grays, 4 type styles etc.). With that information, we can allow users to "add" those elements to their saved styles and see if something on the page doesn't match. For instance, the red we use is #C8080A but I can now see that in these 8 places we're using a red that doesn't match. Would love to hear your thoughts around this!
4. There is actually a "History" tab located on the side-panel where you can view the changes made to that page over time. Let me know if that's what you meant and how we could improve the visibility/usability of that!