Anima - Vibe Coding for Product Teams — Build websites and apps with AI that understands design.
Build websites and apps with AI that understands design.
Promoted
hi @grantkiely, I've just signed up but I'm now stuck on a loading page at https://youneedawiki.com/app, is there any way to fix this? :o the product looks great and I can't wait to use it!
@alex_dobrenko@grantkiely thank you so much! I've just taken this for a whirl and I absolutely love it. there are plenty of other applications for it besides a wiki, and that makes it super fun. great job on this grant :D
@theodorasarahabigail
Thank you so much Theodora! I appreciate your patience with the log in.
You are right, there are some applications outside of a wiki that I had not even considered!
I’m also looking to add more features! You can see them here: https://ynaw.nolt.io
Hey @grantkiely, congratulations to the launch! It looks great. Is there an option to invite people just in the view mode? I think it could also be used as a lead magnet for a free ebook/online course...
@paulpreisler Thanks Paul and great suggestion. I am currently working on a way to do this and I should have it in place within a week's time. If you like I can send you a pm with the timeline and then an update when it's ready.
Report
@paulpreisler@grantkiely Congratulation, Grant!!
I also wait for the update that @paulpreisler requested. I am a teacher and it is very useful to publicly see my student´s work, but only to see. Only my students can edit.
Thank you and congratulations from Spain.
@estebanrules Great point Damian! I also ❤️wiki's and there are a lot of good options out there.
What I think distinguishes You Need A Wiki from others is it's primary focus on Drive/Docs integration first. Docs is a powerful editor so I wanted to keep that and extend it for team wiki's.
Because of this integration you can do things like:
- Set up a wiki quickly with your existing Docs (no copy, pasting and reformatting)
- If your team already knows how to use Docs, they can start adding to the wiki straight away. Your team members don't have to learn how to edit a wiki in a new interface.
- All your changes are saved to Drive so if you change your mind down the track everything is stored there.
There are probably others but I think these are the biggest pros/distinguishers from other wiki's.
@grantkiely Cool. The low barrier to entry could actually be huge for us - for example we have used Gollum in the past but Sales and Marketing are not able to use it (understandably). We will demo the product next week.
Hi Grant - I've been looking for a solution to "crowd edit" my next book, Indistractable. What's the limit on users per wiki? Last time I tried to use gDocs and it crashed after about 50 people in the doc at a time. Thanks!
@nireyal Hi Nir! I've followed up with you via email about both this and batch adding users. This sounds really cool, would love to be able to do it in YNAW!
Report
Hey, great idea. I've been looking for some kind of internal knowledge base but didn't really want to have to deal with another platform for info to be updated in. Is it compatible with Team Drives? Also, is the pricing for viewers or editors?
@boogsau Hi Matthew, pricing is for both viewers and editors, public viewers are not included in this. It's not currently setup to handle team drives but I could definitely look into it for you!
Report
converting comments to footnotes is one way to go, I guess. Shouldn't the identity of the commenter be included?
@stoweboyd I agree this could be handled in a nicer/more intuitive way, I've noted this down on my feedback list. Thanks Stowe!
Report
@grantkiely Best might be something that sort of emulates Google Docs comments, which are attached visually to the sentence or paragraph the comment is made on, and displayed in a right panel. But you do it as a sort of threaded discussion at the bottom of a paragraph, alternatively.
This is amazing and have always thought Google should start providing a CMS layer on top of team’s Drive data.
I have a brainstormed this problem space with a couple of friends and few things you can think of to super charge this:
1) add a “staleness” signal to help with trusting the data. With that, can you use this to actually motivate people to keep it up to date?
2) leverage editors of the data from metadata and integrate with chat to get quick help because all information is never documented :),
3) Multiple contents: in reality, there will always be multiple data sources like slack channels, GitHub PR, Jira issues, Invision comments and google docs. How can this wiki be more heterogenous - that’s a long game but something to think about.
Tried to share everything we thought of. Good luck!
We abandoned the idea because it’s hard to sell to small businesses because GDrive just works for them. Enterprises have too much decision makers and is a whole different sales problem.
So how do you plan to grow it? What are some of your acquisition strategies?
You Need A Wiki
You Need A Wiki
Growmodo
You Need A Wiki
You Need A Wiki
You Need A Wiki
BetterPT
You Need A Wiki
BetterPT
You Need A Wiki
Nir and Far
Nir and Far
You Need A Wiki
You Need A Wiki
You Need A Wiki
GenY Resume
You Need A Wiki