onassar

Hey all - I built out a UI library for Typesense so that I can get up and running quicker when deploying new search experiences. It's vanilla JS, has a small footprint, and deploys as a Web Component (low-likelihood of conflicting with existing code). Feel free to ask any questions.

That's a cool idea. I wonder if one thing we could do here is to go through the Issues on the respective editor's GH page, and look for some "will not fix" issues. Documenting that could help devs figure out what might be a blocker for them.

Do you mean being able to one-click copy some integration code?

Hey @marcosgrala - yep we are. We want to eventually either link to our integration on GH, or show snippets of how we instantiated the different instances :)

Hey all - we frequently need to use wysiwyg editors for projects, and one thing we often get stuck on is previewing different ones to see how they work, what they look like, and if they fit the needs of our project.

To make this easier, we built a tool to compare different editors. With it you can: - Quickly see a demo of 10 different editors - Favourite or add them to a compare page to see them side-by-side - Filter by certain licenses (e.g. MIT) - Filter by editors that are “block based”

Would love your feedback here (especially if there are editors you want us to add). We also open-sourced the editors integration here: https://github.com/bitcomplete/labs-wysiwyg-editors

That's super helpful thanks. We had a similar piece of feedback re:transcript. Hope to add that one soon.

Thanks for the comment @beardyw

Agreed that being nimble and able to adapt to the situation is the best. One thing we found was just speaking out loud helped us figure out how we wanted to articulate ideas or questions. So Prep Coach is meant, in a way, to just help you get out of your head.

Hey all -

We’ve been working on Prep Coach over the last few months. Here’s the problem we saw: we would run into situations at work where we need to have a “tough” conversation (e.g. giving constructive feedback to a colleague or manager, asking for a raise, etc).

One thing we’ve found we do is kind of “talk to ourselves”; prepare in our heads how we’ll handle certain questions, or phrasings.

So we wanted to build a product that lets us actually _talk out loud_ while it’s recorded, and then have the product give us feedback on what we’ve said.

That’s what Prep Coach is: you choose a Scenario, and it’ll present you with some prompts. You then record a response. Prep Coach will then take all your responses, process them, and then give you actionable feedback (e.g. “Be more specific when you talk about XX” or “This was great, but you went off track a bit related to the topic”).

This is our first version, but we’d love for you to try it out and send over some feedback.

Yeh gr8 call. We debated how to include Tailwind, since it's slightly different. But including a collection of Tailwind-based frameworks makes sense.

Happy December all!

We built a quick-and-easy way to compare CSS frameworks, by viewing demos of the frameworks in action.

The goal is to make it easier for developers to previous frameworks side-by-side (we've also open sourced the demo files, so if you have a bit of time we'd love a PR with any frameworks we're missing: http://github.com/bitcomplete/labs-css-frameworks)

Would love any comments on which other frameworks you'd like us to add, or features to make the the decision process a bit easier.

Thanks for sharing this @westurner

Oh CORS… we’re still figuring out an approach on how to handle static assets that have restrictions. Sorry about that, but I assure it’s one of the top things we are going to address.

Thanks @Dev_Olly! Feel free to leave a comment if you run into any issues!

We looked into this, and we couldn't find a way to do so, but we've open sourced the data (here: https://github.com/bitcomplete/labs-delta-viewport-tester-vi...) so if you are able to find a way to do so, that could be a great option.

This is awesome: thanks for these resources! We'll take a look at Cloudflare Browser Isolation for sure. We've played with screenshot tools at specific viewport dimensions etc, but it's not often the right fit for when we're doing interactive frontend responsive updates. That aside though, the screenshot APIs could be a great integration to be able to download/save screenshots of specific viewports.

:)

Thanks for this @alwa. It definitely helped me better understand the question. I commented below @doctorpangloss but agreed: portrait/landscape mode are vital, and that's already on our roadmap.

Haha funny analogy. What you and @alwa said makes sense: thanks for sharing that. It's related to Caveat #1 I mentioned above, but I like the idea of being able to toggle on/off the header/footer, to simulate real-world scrolling behaviour. I got that added to our list.

Thanks @kmfsousa! Feel free to leave another comment if you have any ideas, or run into any issues :)

Really sorry to hear your first impression wasn't great @altdataseller It has to do with limitations around performance/memory. In some instances, loading large documents in multiple iframes at the same time could cause mobile safari to crash. We have plans on how to address this, but we thought that seeing as frontend responsive testing is most likely going to be done on a Desktop-like device, we would prevent possibly crashing your mobile browser and show you a video walkthrough of how it works on desktop. Happy to chat more about this offline if you want: hello@viewport-tester.com

Interesting: can you elaborate on this? Would love to better understand it, so we can consider adding this.

@ivanjermakov I know: it's a bummer that it doesn't work on mobile. We initially _did_ make it work (and responsive), but we ran into performance/memory issues. This is related to how much memory can be allocated on mobile devices, and since we open multiple iframes, it caused a lot of problems.

We have a specific plan on making this work on mobile, but for this initial version, we decided that making it limited to Desktop was okay (since, realistically, people who are doing frontend responsive testing, are most likely doing it on a wider display).

This absolutely could work with HTML emails. One challenge with Email On Acid's is you do need to have an account with them, and it is limited to emails. We find most of our viewport testing is related to landing pages, etc.

Thanks! If you run into any issues or have any ideas, please share :)

Great question! Right now, it doesn't take into consideration the browser or device address/bottom bars. We documented that here: https://github.com/bitcomplete/labs-delta-viewport-tester-vi... (Caveat #1).

We plan to address this in the future, but at the moment, Viewport Tester works in a similar way to Chrome's native Device Inspector: it resizes the viewport to the exact dimensions.

Thanks for sharing this @Brajeshwar! This is a great tool and one we played with. One primary motivation for us, that caused us to build a web-based Responsive UI testing tool, was we wanted to be able to easily share issues/links with our team. It has it's limitations, but there's something super-handy about being able to test a URL, find an issue, and then link directly to that experience on Slack, Linear, Jira, etc.

Unfortunately we don't have support for mobile Safari yet. It has to do with some performance challenges related to drawing multiple iframes to the page. Hope to get that fixed soon.

Thanks for the comment @account42 Agreed that a really-great responsive site is one where specific viewport dimensions don't matter. One thing we've run into (and want to test for) is users mentioning they're using a specific device and having issues.

In those cases, it's helpful for us to really quickly choose from a list the device, and view the site. That way, we don't need to know the exact dimensions of the device, and can also test a possible fix for that device against other viewports.

Haha funny! Yeh we disabled that, in part, because it can result in an infinite loop.

Can you share the URL you're testing?