zevir

I have an open source CLI tool for provisioning preview environments. I want to get it in front of relevant developers. What are the most effective methods for doing this? Thank you!

We've released an SDK (sdk.livecycle.io) that helps front-end teams collaborate better and do reviews faster by adding a Figma-like review experience to PR preview environments.

I'm looking for people in the FE/Jamstack community who are open to reviewing the product.

Are there people you know of/follow that do a great job with these kinds of reviews?

Does anyone here fit that description?

Open to compensating the relevant reviewers for their time (but not their opinions... those have to be authentic :-)). TIA!

I put together this landing page for our new SDK - https://www.sdk.livecycle.io/ Can anyone give some quick (constructive) feedback? - Do you understand clearly what we do and why it's useful? - If not, what would you change?

THANK YOU.

I have lots of written content organized under main categories and tags (multiple tags per category). Im looking for a simple site builder/template that allows me to present this in a clean, minimalist but functional way without all the fancy bells and whistles that the mainstream site builders promote.

Any help would be very much appreciated!!!

Thanks!

I'm trying something new by asking the HN community for some help. Let's see how this goes.

I'm working on a startup called Livecycle - http://livecycle.io/ - a platform that adds a contextual collaboration layer on top of PR preview environments.

Our current offering generates collaborative preview ends per-PR.

We’re now working on an SDK so that we can add this rich collaboration to any existing preview environment as well.

And here’s where I need some help - I’m trying to better understand how devs/teams are using PR preview environments today (what platform do you use to create them? Do they help you facilitate collaboration between technical and non-technical stakeholders? If you could add the Livecycle collaboration functionality to your existing environment, would that be a benefit to you?).

To make life a bit easier, I've collected a few specific questions here so anyone relevant can send us quick responses - https://tinyurl.com/livecycle-sdk.

THANK YOU for your consideration! If you have time to share your experience and wisdom, it would be tremendously helpful for us . We'll even send a gift card and some swag to the first few qualified respondents.

Does anyone use deploy previews (AKA 'preview environments' or 'ephemeral environments') on a regular basis to see/share github pull requests?

What platform do you use for this?

What are some use cases/workflows in which this capability helps you the most?

What's missing from these solutions that you wish they offered you?

Thanks!

Everyone knows that developers hate it with a passion when people try to sell stuff to them.

But many developers are also very generous in testing new products and offering candid feedback to the makers.

My question is - what is the cheat code for striking that balance? What gets developers to sign up and try your dev-oriented product in an authentic way? - Are there specific platforms or communities where developers are more receptive to these requests? - Maybe a specific type of pitch that is more effective? - Perhaps a specific medium that most developers prefer?

I'm very interested to hear what's worked well for you.

Thank you!

For those working in tech/software development teams - do you also find that there's a lot of tension between developers and designers?

They need to work together but it always seems like a challenge. From the tools they prefer (Figma vs. Github) to the pace/workflow to the language and communication.

What are the biggest pain points you've seen?

What are some great tips for bridging the gaps during a typical workflow?

Thanks!