tfjaeckel

Thank you!

Thanks for adding more color to your original answer.

I like you enforce the commit/ticket relationship. Is this purely an agreed process or do you use other measures to keep things consistent? E.g. we typically add the ticket ref to each commit but at times that gets omitted.

Also, I think that (internal) release tool is something crucial as the team grows. Will check shipit a bit further.

Would you mind expanding a bit on the things you enforce for each of your releases?

I think Slack notifications are really nice to see what's going on right now but not so great to see the state of dozens of service, i.e. what version is deployed to what environment.

Then there is the issue of linking the Git release/tag with the corresponding changes, say from a ticketing system such as Jira. That can be helpful to communicate changes to other people within the organization and to users.

How do you define dependencies for releasing new versions to service? Likely going to happen at some point when you have non-trivial changes to services.

Step Functions are convenient but for the reason you stated we stopped using them. Pricing seems off for what they do, especially when it's in volume.

It's great feedback, definitely more food for thought. Thank you! It's a fine line between cutting features vs. trying to solve too many things at once.

Our current approach to the collaboration part can be seen when you link a Google Drive account. When you want to edit a Google Doc it takes you right there, no need for the GDrive UI. You can actually create a Google Doc from within Shelf.

Also, "good" to hear what you wanted to know but didn't learn immediately from the website. We'll surely be working on making the use cases and functionalities more clear.

All good. That's not really the use case for Shelf. You'd publish final versions of deliverables on Shelf, not necessarily your whole work-in-progress.

Just to share a different perspective, not even to disagree with your view: Think of a marketing team that wants to publish and share presentations to be used by sales reps. Or a team of researchers that wants to curate different types of information (docs, links, videos) for later perusal. Enrich each of those with meta data. These are different use cases, that's where Shelf shines.

Enterpriseready is a good site, agreed. I'll also check Replicated to see how you support on-prem and would gladly take your offer to hear more about your learnings.

Got it. I first thought you wanted that content to disappear altogether. Thanks for clarifying.

Data is secured at rest and in transmission. We take every measure available in Elastic to secure the search indexes themselves.

Thanks for sharing your thoughts on this topic. It's a challenge for all SaaS products I believe but yes, the more business critical the product the more important to address.

Apart from self-host and open source, do you have other suggestions on how to address this on a product level? Would you feel comfortable with structured exports for example?

May I ask what makes Confluence look more professional from your perspective?

Like I mentioned somewhere else, I actually like using Confluence depending on the use case. It tends to require much more attention in making sure things stay organized and well structured. Shelf has this built-in by being more opinionated (for better or worse, depending on what you need).

Thanks for that perspective. Put on the list. Won't let them keep us from making money along the journey.

Thanks! Fixed. :)

Thanks for taking time to try out Shelf! And for providing your feedback as well.

Tags: delimiters are [comma], [enter] and [tab]. 50 tags are the max. 30 characters are the max. We'll see how we can make tagging a better experience. Including suggested tags based on content/previous behavior.

Can you explain what you mean exactly by: expiration on items?

Thanks Jedd for your kind words! We have a great Team that made this happen and is working hard to keep making Shelf better every day. And help cure that pain you share. :)

My use of 'cloud' wasn't very exact, you're right. I suppose most enterprises have or will have their 'own' infrastructure in the cloud and manage it there themselves. I really meant cloud in the way of a SaaS-model.

I see how you could come to that conclusion. At first glance, yes similar. However, Confluence really is a Wiki on steroids. Great to link with Jira, collaborate on Specs or the like. You can use it for document storage but not what it's built for. We use Confluence internally in the Dev Team ourselves and for that it's great.

Shelf is for curated content, not direct collaboration or Wiki. For that, we integrate with what was built for it, such as Google Docs.

Here is a comparison with Confluence, hope that helps: https://shelf.io/shelf-vs-confluence-comparison

Thank you, great detailed feedback on what we can do to make it easier and more pleasant to get the gist of Shelf right away. It's really appreciated.

You're right, Shelf does have some of the Evernote functionality, I guess most notably the web clipper. What we focussed on is more of where Evernote falls short. Which in my opinion is good and easy collaboration across teams.

An advantage of Evernote for now is that Shelf doesn't have offline note-taking. What do you think, is this something hugely important to have?

Ouch! Is it really that many?

Thanks for that input. Totally agree that HIPAA certification is a good approach to prove full coverage of what you've mentioned.

Dropbox is really great for storing and syncing files across devices. It doesn't have a rich set of pre-built filters, you can only store files, not mixed content including links, contacts, etc. So, Shelf is really a complementary solution for Dropbox and can sit on top of it, combining the Dropbox content with other content from a single interface.

Sharepoint is of course very powerful. And that means you typically need a project to make it work. Shelf works out of the box, is opinionated and let's you get started with minimal to no configuration setup.

Yes, we use Amazon S3 for content uploaded to Shelf (encrypted of course) and we utilize ElasticSearch as well.

Totally understand this perspective. I guess it depends on the type of organization and what you're willing to put in the cloud vs. what you want to manage yourself.

Our architecture is generally built in a way with self-hosted in mind but it's somewhere down the road and not something we'll have in the short to mid-term.

Nice validation that the pain really does exist! :)

Thanks for all your feedback, doesn't sound that critical to me at all and really is straight to the core of the challenge. :)

Of course you're right in a way. Tools are only as helpful as the people using them. So, we want to build a platform that makes it as easy and intuitive as possible, to add and organize things in a way that's accessible to others. And as a next step, build in more intelligence that assists in doing this automatically, including connecting and enriching content.

Content is usually already there, it's just often "locked" in different silos like a Dropbox, Email, CRM systems. We see Shelf connecting with the different content providers and pulling the most important content (not all of it).

There are a couple of comparisons with other platforms, the links are (hidden) in the footer of the homepage, here is one of them: https://shelf.io/shelf-vs-confluence-comparison

Yes, that's right. At the moment it's a web app. Adding an installable version, possibly via Electron is something we've thought about and probably makes sense to unlock some functionality a web app just doesn't have permissions to do (such as file system access). You can also install our web clipper which is a browser extension but that's not needed to use Shelf.

Hi, I'm one of the founders of Shelf. We think teams and organizations are wasting too much time locating and sharing knowledge.

Been working on helping solve this this issue for quite a while now keeping things in more of a closed circle of beta users until recently. Why? Because we wanted to build a well rounded product based on customer feedback before opening this thing up.

Anyway, so far we've built Shelf primarily on a NodeJs stack making heavy use of microservices and recently more and more Lambdas with (and sometimes without) the Serverless framework. And we built a web clipper as browser extension for Chrome and Firefox to make it easier to clip and share web content.

Would love to get your feedback on if and how you experience the pain point. Of course feedback on the product itself would be great, too, if you want to give it a spin.

Thanks! Let me check this out a little further.

Still down.

Sad that that's probably true. But then, there are some products that really need a bit more than just a one-liner. At least when talking about B2B. For sure I don't sign up and try a new product without at least getting some idea what it's about from the landing page.