Feature proposal #6336
closed
Implement Community API library
Added by krileon over 7 years ago.
Updated about 3 years ago.
Start date:
13 December 2016
Description
The idea behind the API is to pull GJ away from being a singular community. Basically it'd work exactly like CB Gallery where a singular Gallery API endpoint can output an unlimited number of galleries. With GJ the API would be called Community and have an Asset column. This will allow generating and outputting as many communities as a site needs or wants with per community configuration.
- Priority changed from Normal to High
This should be able to clone CB Gallery API and adjust as needed. Essentially Albums are Categories and Items are Groups. Use the same methods as CB Gallery for tracking parameters across pages.
The default asset for the Community API and for existing entries should be "global".
Integrations need to somehow extend this so they too are a part of the Community API. This means the parameters for the integrations would also need to be handled here as well. Maybe add a trigger to the constructor to add those parameters? Still need some sort of functionality to the integration functions. Maybe a ->integration function for calling those integrations? Maybe just reading too much into this as those integrations are just acting on triggers is all.
- Status changed from Assigned to Rejected
- Target version deleted (
4.0.0)
- % Done changed from 0 to 100
This doesn't really seam necessary. There isn't really a reason to isolate groups from other groups and if you need to you can use the category system to do that.
Also available in: Atom
PDF
Updated by