« back to discussion

Deleted Resources

Hello everyone,

I would like to write a quick post re-emphasizing this particular spot of the FAQ: Why was my resource mercilessly edited or deleted?

Recently, there has been a huge surge of new users for about the last 2 weeks, and there are a bit more resources that have been pruned from Pineapple.

Until the FAQ is updated with a better list, I will outline exactly what I mean here - as I feel it's extremely important for users to know why something was there, and then gone.

First and foremost, Pineapple serves to be a list of very high-quality tutorials, tools, and assets. If something you submit is removed, this does not necessarily mean your resource sucked!

It merely means that it wasn't an ideal fit for here (and one which may be better suited for Reddit or Hacker News).

The most common resource that gets removed are tutorials that aren't very long, or involved.


  • Extensive, developed, and comprehensive "guides" or tutorials.
  • Very excellent, quality screencasts (paid and free)
  • Github repos with a lot of stars that people may not know about.

Not for Pineapple:

  • "disposable" content
  • Very short 'articles'
  • A brief blog post with a paragraph explanation and a code snippet
  • A 3 minute screencast about an obscure feature in a program
  • A short screencast explaining a tiny piece to an immensely vast topic (for example, a 3 minute demo explaining a single function in backbone.js). A much better resource would be an entire series of screencasts for backbone in general.
  • something that has been discussed a huge amount of times in other places (for example... a php snippet to display tweets)
  • A solution to a problem that can be easily googled.
  • "Lists" (such as other aggregated content or lists of the '10 best ice cream cones')
  • etc

Generally speaking, there are probably a million resources out there, and if we added every one, or even most of them, Pineapple would quickly become diluted. Currently, I'd say we have an extremely excellent signal to noise ratio for hidden gems, and they are hard enough to find as it is... even with searching, tag browsing, and a wiki.

I guarantee if you skim through 20 pages you will find something that you will like. We really want to keep it this way.

As an example, we get a lot of github 'personal project' repos with only a few stars. If the first page was continually full of resources like this, it would be increasingly (perhaps exponentially) harder to find the truly mind-altering resources that you are bound to see on here if you look. It doesn't mean your personal project is bad, but just something that may need to be a bit more developed or in-depth before it would be a good fit.

So, you could consider us quite strict on this point, but we like to think of it as doing our part to make sure our thousands of users are provided with the ultimate experience of finding what they need.

There is plenty of room for your contributions. If one gets deleted, don't take it personally :)

Looking ahead: In order to better serve users, our next round of features will also feature some notification system which provides direct feedback to users if a resource was deleted, that way they are not left in the cold.

over 5 years ago, by pineapple

125 Replies

Login or to comment.

« back to discussion

Tutorials are any resources you learn from.

Examples: an intro to html5 screencast, a pdf about git, photoshop effects tutorials, meta-programming in ruby, lambda calculus, higher-order fixed-point combinators.

Tools are websites, apps or services used -on- your project (indirectly), to aid the process.

Examples: A color scheme generator, email marketing software, usability heat maps, css3 code generators, a downloadable png compressor.

Assets are downloadable files used -in- your projects, usually as code, textures, or images.

Examples: a jquery sticky menu, photoshop brushes, background textures, mvc frameworks, twitter bootstrap, 960 grid system.