Stubs are listings created by the Peels team on behalf of (usually) local government food scrap drop-off points. Here’s an example of one.
They differ from normal listings in the following ways:
Think of them like stubs on Wikipedia; they’re placeholders until someone else (hopefully an owner or authority) takes over. That’s why the language around stubs on Peels is about encouraging the owner of the place to take over the listing.
Stubs are designed to be helpful, not to simply populate the Peels map. So only add a stub if the location is permanent, the information is correct, there are external links, and you feel strongly that the owner or manager of the space would endorse the public coming over to drop scraps off uninvited. Think city-run food scrap drop-off points with an official website to link to.
To keep stub listings manageable, we maintain separate Peels accounts dedicated to separate parts of the world:
And so on. We might split listings into more granular area accounts (like states) if and when the listings get out of hand.
These stub accounts have is_admin column on the profiles table set to TRUE. That then exposes a stub setting on the ListingWrite component, which corresponds to a is_stub column on the listings table.
As mentioned up top, stubs are meant for community drop-off points. I suppose we could only show the stub setting on ListingWrite if the selected listing type is community, but maybe there’s a use case for stub business listings, too.
Check out other stubs on Peels, particularly around Chicago, USA, and Brisbane, Australia. Use those as reference.
Assuming you’re an admin, you can add a stub by adding a community listing and turning the aforementioned stub setting to true.