danfang/me-api

Future Integrations

Open

#3 opened on May 28, 2015

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (819 stars) (42 forks)batch import
enhancementhelp wanted

Description

Just a dump of integrations you (and I would like to see).

  1. Statistics logger + database. This one excites me a lot. This is a module that doesn't return a response, but aggregates data about your API: who is using it, your most popular content, summaries of various endpoints. Implementation wise, it might change a lot of the way integrations are done currently (e.g. you can't access data cross-integration right now).
  2. Pinterest (unfortunately I think their API is quite disappointing)
  3. Youtube, Flickr, file hosting. More media the people like to promote.
  4. LinkedIn, to provide a standard interface for your professional profile.
  5. Fitbit, Nike band, Jawbone Up.

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
apibackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Node.js knowledgeREST APIs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
This issue is a broad feature request listing multiple potential integrations. A first step would be to examine the current integration architecture in the codebase, specifically looking at how existing integrations are structured (e.g., in /integrations folder). Then, for a specific integration like the statistics logger, research existing solutions and draft a proposal outlining the data model and API changes needed. Reviewing the three comments on the issue may provide additional context from the maintainer.