Back in 2018, I launched Notion Pages on Product Hunt, it was the #2 product of the week. Shortly after, I joined Notion to support the community. Our community has written books about Notion, created mascots, hosted hundreds of events, started full-time businesses around Notion, and much more. Many of the highest-ranking products on Product Hunt in the past two years have been Notion templates. Going back in time, Notion launched

My name is Bertha, I hail from Johannesburg in South Africa. I initially started my career as an Engineer, I had been doing it for over 15years when I decided to completely switch careers and start programming and coding. I am completely self-taught from online courses, programs, and on-the-job training. With that said, the dev house I founded has developed pretty amazing software over the years (in my mind). One of our latest products is Skhokho - https://skhokho.io/ Our Ship, upcoming page can be found here - https://www.producthunt.com/upco... have been learning a lot from this community, I read a lot of threads - trying to figure out how to get the most out of Product Hunt and prepare for a good enough product launch in the next couple of weeks. One of the things that comes out a lot in the discussions is - Building a Community. You hear it all the time - build your community, mailing list, and following. I would like to ask the guys who have been doing it for a long time or guys who have managed to build successful communities - how? How do you start from scratch Which platforms have worked best How do you keep your community engaged What daily, weekly practical steps do you take to actively build your community What worked, what did not work

Hello, PH! Share your goals for this week (any number you may have) so the community can provide some advice or motivation! I'll start: 1. Polish some pages for my latest project 2. Publish my second blog post 3. Update the GUI for the service itself

TL;DR - post a link to you Ship page, get feedback from the community We're launching on PH soon, and have already set up our Ship page, which got me thinking - "there are a ton of Ship pages laying around, but no one collects quality feedback on them". So here's my answer - post your Ship page on this thread + your email and I'll send you a quick Loom video of me viewing your page and giving my feedback. If a few other people join me, well, we got ourselves some quality feedback sessions from real users (or in other words, a PMs dream )

Hey there! Today I brought a reminiscent question :) What was your dream job when you were a child? Are you currently working on anything similar? Would your child version be proud of you? Let's share some memories!

Yesterday I read a lengthy discussion on YC HackerHews that no-code is just "a buzzword". So here are my two cents 1) No Code is BIG. Gartner estimates that "by 2024, low-code application development will be responsible for more than 65% of application development activity". So no-code is something we should take very seriously because as a trend and as an industry it will only grow. The capabilities for product development are huge, while no code & low code tools will only improve in functions. For example, I founder a no-code startup, called WeLoveNoCode (https://welovenocode.com/) which helps startup founders hire no-code developers and build products 10x faster. We got $1M funding, grow to $150K MRR, and made 2000+ projects. It's not a joke, this market is huge! 2) No code is USEFUL No-code is the art of creating solutions (native apps, websites, web apps), which could have been written with code but instead using visual methods (without coding). Most no-code tools use a visual drag-and-drop interface. In addition, a lot of them have pre-built templates that you can customize. There is also a slight difference between "low-code" and "no-code." With "low-code," you can do many things with a drag-and-drop interface; however, some coding is required for a finished product. So you ANYWAY need some background in coding. Low-code is typically great for people with intermediate technical skills. No code is a new way of building products, very different products. It's not magic. What can be built with no-code? * Mobile apps, * web apps, * websites, * workflow * automation, * marketing tools, * payment systems and the list goes on. Basically, "typical" products & MVPs benefit the most from no code. So the founder can build something in weeks, really fast. For example, WeLoveNoCode connects founders with the best no-code developers to create their software and apps without a single line of code in like ten days. You can do all of these on a monthly subscription plan. 2.) No code has proven its place already and it has A LOT of the advantages: * will save you money * you can build and test your ideas quickly * anyone can use it > Designers, product managers, marketing managers now can make their ideas tangible products. Just like a new thing, tools have to be learned, and they all have their learning curves. However, it will take you much less time and resources to learn how to use no-code tools. Unlike low-code tools, no-code tools have a limit to how much you can customize them. So if you want to change every aspect of your product or build very complex products, no-code tools may bring some limitations. However, there's so much innovation and growth with these tools, so I expect fewer barriers in a few months.

Back in 2018, I launched Notion Pages on Product Hunt, it was the #2 product of the week. Shortly after, I joined Notion to support the community. Our community has written books about Notion, created mascots, hosted hundreds of events, started full-time businesses around Notion, and much more. Many of the highest-ranking products on Product Hunt in the past two years have been Notion templates. Going back in time, Notion launched

We know that productivity is a daily challenge for remote workers. I am guilty. So I am curious how you guys keep productivity at peak (or at a functioning level, at least) while working remotely? A good night's sleep and a cup of coffee/matcha are great boosts for me. How about you?

We were wondering - should we set our whole team as the makers of our product / only the founders / some other option? What do you guys think?

Hey Product Hunters, We launched our product yesterday and received many comments about machine translation vs. human translation: https://www.producthunt.com/post... It's a topic that fascinates me and I've been collecting fun machine translation failures for a long time, let me share with you some of my faves I speak some Mandarin Chinese and that's a great language for machine translation failures 1. There is this Chinese set phrase (= to be jealous; literally to eat vinegar ), and machine translation gets it right. But if we use this phrase in a sentence Oops! This awkward moment when Are you still jealous of your ex? turns into Will you still eat the vinegar of his ex-girlfriend? 2. Another Chinese to English translation example (sorry, didn't keep the Chinese version, but I do have the Google translate screenshot): I hope you ll be beautiful in the future . Lol what? The original Chinese phrase said I hope you ll have a great ( beautiful ) future . 3. One of the key problems is that machine translation often doesn't get the context. It becomes especially serious if you translate standalone words (like UI or other short strings of text). In one of translations there was a single word wasted. It was a game context, so apparently it would mean "killed", but it could also mean "spent in vain", "drunk" and many other things. A human translator can assume the correct meaning based on other strings of this translation, or simply ask you for more details - but the machine won't. It will go for the most common version - in this case, it will be "spent". 4. Another one was when I had an article about games translated from English into Turkish - by a native speaker. I ran the finished translation through Google Translate to check stuff like links and figures in place. And I came across this: "( te bu nedenle,) oyun geli tiricileri i in yerelle tirme s recini olabildi ince ba a r tmayan bir i haline getirebilmek ad na, (tasar m s recinin en ba ndan itibaren uygulanabilecek bir tak m kurallar i eren bu listeyi haz rlad k.)" - Google Translate said "...in order to make the localization process as a headache as possible for game developers". (WAIT, WHAT??) The Turkish version actually means less troublesome as much as possible, less of a headache as much as possible , but Google translate was telling me the opposite Please share your opinion and favorite machine translation mistakes in the comments! Also, it would be great to hear your feedback about our human translation platform: https://www.producthunt.com/post... Thanks!

Hi Hunters! I noticed many great examples of "Launch Day Dashboard", like an amazing Thursday landing with live diagrams and statistics and "live social mentions wall". But on our first launch of Sembly Personal, we decided not to use additional Dashboards, for internal use Makers was checking the PH "Launch Day" page and GA for the site. Is the launch dashboard appropriate for B2B products? Share your experience, how did you share live launch statistics with the audience, and did you share at all? P.S.: Built-in counter banners are not counted as a dashboard :)