Several options for tag based endpoints.

Option1.md

We can roll the new featured tag[s] into /discover

Pros: No extra HTTP requests on the client

Cons: Kind weird, especially with pagination. Larger payload sizes.

GET /disover

{
  "projects": [{ /* Projects with the featured flag set to true */ }, ...],
  "featuredTags": {
    "mozfest2015": [{ /* projects tagged mozfest2015 */ }, ...],
    "makerparty2016": [{ /* projects tagged mozfest2015 */ }, ...]
  }
}

Option2.md

New featured tag route

Pros: only one extra request, dedicated featured tag route

Cons: pagination is still strange, one extra request

GET /discover/tagged

{
  "mozfest2015": [{ /* projects tagged mozfest2015 */ }, ...],
  "makerparty2016": [{ /* projects tagged mozfest2015 */ }, ...]
}

Option3.md

route to get featured tags, route to get projects with a tag

Pros: A way to expose featured tags without fetching projects too. easier pagination

Cons: Much more HTTP Requests

GET /discover/tags

{
  tags: ["mozfest2015", "makerparty2016"]
}

GET /projects/tagged/mozfest2015

{
  projects: [{ /* projects tagged mozfest2015 */ }, ...]
}

core functionality:

• add description with tags
• tag as link
• list of projects with tag

# something we might try: - an "advertisement" that encourages people to browse a theme and maybe contribute a project - not a core feature - might be a good idea. might be a bad idea we change or dump

Question: should client or service wrap tags with link html?

Client. Both sides will need to share a common regex... 👍