Showcase Questionnaire

[cannikin]

We've talked about having a "startup showcase" on the new site, highlighting some startups using Redwood. @noire-munich came up with a list of questions we could send to startup founders they could answer in a sort of interview format:

Introduction

• Who are you and what's your background?
• What problem are you addressing?
• What solution are you bringing?

Redwood

• Is redwood supporting the migration of an existing project/business or is it a brand new project?
• How does Redwood help? ( that's as cheap as it gets and I'd feel more comfortable removing it )
• How did you come across Redwood?
• Is this your first Redwood project?
• Ultimately you had to choose Redwood over something else: what was the ultimate contender and how did you make your choice?
• Are you using a vanilla setup or custom? Feel free to elaborate
• How many minor versions did you have to jump until v1rc and how has that affected your project?
• Which tool or feature from vanilla Redwood proves to be the most helpful?
• How is your project hosted?
• Are you using Redwood to the full extent of its features and if not, why?
• What gets you thrilled about its future?

Team

• Do you have a team?
• Are you recruiting?
• How about onboarding with Redwood?
• Is previous Redwood knowledge a requirement to work on your project?

Community

• Are you or one of your team collaborating to Redwood in any way?
• How has Redwood community added value to your project?
• How do you meet the community? (edited)

I think it could work that way:

• Such a list could be shared to startups selected for highlights
• Each person in charge of this will select their weapon of choice: text based or video, or even podcast if relevant
• Questions should be selected upon the answer's value, at the discretion of the person answering them.
• Result would be peer reviewed before or during final production - some would want to do this alone, others would need someone to help go through it so they can focus on answering.
  sprout wise, each startup will have their dedicated page. Depending on how they preferred to handle this, we can host a video, display some text or link to external content if necessary. Both external content and video would mean only storing links, and as for the text we would keep it as simple as it gets

[cannikin]

If they want to respond in text format it'd be great if they could provide a few screenshots of their app to include in the writeup. If they're doing a video response they could demo the app live.

[noire-munich]

Also, I thought that this could be coded as well for people going the written down way. It could be like a form to fill online and then it becomes an "application" -> team gets a notification on slack and can discuss triage ( accepted as highlight, accepted as showcase, rejected ).
If accepted, goes into edit mode until publication.

[agiannelli]

This is awesome! What are our next steps and how can I help? :)

[cannikin]

add it to the hosted version of the website & eventually go live
--> @cannikin how is this going to unfold?

Each Showcase page could be totally different based on how each person responds (text, video, audio...) so I'd say let's just create a regular page/component for each and not worry about trying to pull them from a database: that schema could become a nightmare to maintain as new response formats come in. And we can pre-render each page to make them even faster.

[cannikin]

Maybe I read "hosted" wrong above... if we're talking about site hosting, I assumed we'd get a database somewhere (we've got a couple on AWS already) and then deploy the site to Netlify.

[noire-munich]

@cannikin That was the "hosted" I meant indeed :p.
Is this up to you or shall we get someone else on it?

[cannikin]

Yeah I can set up the DB and connect it to Netlify. We could do that now I suppose, and start having builds running so we can check on it at a public URL and a feel for the responsiveness of the site. I'm on it!

[noire-munich]

That is so cool \o/
One step forward liveliness!

[realStandal]

Good evening to all of y'all,

I've gotten a showcase listing page to the point of sharing for feedback. It's simple and 100% static, which I'm assuming was the goal for the launch (at least).

2022-03-02.20-55-09.mp4

@zakmandhro and @KrisCoulson as people who'd have their projects showcased, I'm keen on y'all's thoughts towards having your project's brand be front stage, and the title and description being hidden behind the hover interaction (for visual users).

I think making sure we get the right assets for each project is a worthwhile step to add. I just stole borrowed these from each project's site. Or if projects want to create/stylize their own 🤷 the full resolution of each image is 500x280 I'm keeping most rectangular banners at 180x50, and then Teamstream (square-ish? ones) is ~120x120.

Again, open and welcoming criticism :)

[zakmandhro]

This looks good. How are you thinking about "hover to reveal tagline" experience be on touch surfaces?

[realStandal]

This looks good. How are you thinking about "hover to reveal tagline" experience be on touch surfaces?

Thank you!

Testing just through the browser, it behaves just like a link or button would -> the content will reveal when the press is held.

There isn't anything visually significant to prompt that as an action - so that's reason enough for me to try a different approach. Here is a quick attempt at that, building each card to be more inline with the ones on the homepage (I've also resized the images to 500x220):

[noire-munich]

Pretty neat @realStandal .
Is it possible to have both versions one for mobile and the other for desktop? Are you using a responsive hook or css breakpoints?

[realStandal]

I'm just using Tailwind's breakpoints for responsiveness. We could but imo I think the same problem still exists on desktop - where it isn't clear that more information is a hover away.

[noire-munich]

We could but imo I think the same problem still exists on desktop - where it isn't clear that more information is a hover away.

Agreed