wunderio / wunderhub Goto Github PK

A status board for people. Are they in work, on holiday, off sick, at lunch? Possible to integrate with cato to update it?

from @steveparks

Inspired by the way wunderkraut.se have done it internally on their site.

We need to work out a way to indicate the canonical origin of the content, so that SEO is not punished.

Currently picture property is just a string and other versions of the user's picture have named like picture_thumb. It would be great when picture would be an object with thumb, medium, large and original in it.

I don't know how to rewrite Views' output because when I tried that I figured out that arrays are displayed comma-separated :/

Im working on user importing to WunderSites from WunderHub and I spotted some issues:

1. To be able properly use users in other sites (like WunderSites), should include email field as well, so it can be used in sites as real email and also as username.
2. In api/team there is two entries with uid=342 and two accounts for Aleksi Johansson.
3. Im not able to see my own entry there (uid=355).

E.g. learning from improvements made to the UI in the JARS project

I'm investigating the possibility of exposing user data through search_api so that I can easliy create a REST endpoint using views to search for skills and other data (to be defined properly).

Here are some questions:

• Is search api with elasticsearch integration the best way to go about this?
• Is using views to provide the REST end point a good idea?
  • Architecturally we're very restricted by the views way of doing things.

We're using this approach: https://www.drupal.org/node/2132779 for supporting a JSONP call, but using CORS seems like a better approach if it reaches core at some point: https://www.drupal.org/node/1869548

Contrib module: https://github.com/previousnext/drupal_cors

Need to add content translation so non-En sites can create content in different languages.

It would be great to get WunderHub user accounts to authenticate against the user's WK Google account, so passwords and access permission are managed in one central location.

Icing on the cake: automagic Hub account creation/blocking when a person joins/leaves WK

All API endpoints filter are based on UUID or similar. It would be nice if something like /api/team/lewis returned a result. It would open the door for better public facing urls and natural language tasks with cato.

Cf. http://www.wunderkraut.com/blog/a-medium-like-editor-for-drupal-8/2015-03-17

If you look at the current team page on wunderkraut.com. The smaller images aren't just resized, they are cropped around faces. It would be good to have that from the hub so we can emphasize faces more than bank space.

record people’s skills and interests - ideally with a weight on each one so we now what level they’re at. would display on the site as a tag cloud

from @steveparks

Cf. https://api.github.com/

Users need to have CRUD (minus D?) operations exposed to an API endpoint.

This needs to be as secure as possible. Drupal 8 currently supports the follwong types of authentication out of the box:

• Oauth 1
• HTTP Basic Authentication

Are there other modules available to provide authentication providers?
Is OA1 or HTTP Basic Auth enough?

Profile links to:
Twitter
Github
Drupal.org
Anything else?

Currently we're using 😬 drush .make files, but it'd be great to switch stuff around to use Composer instead.

Currently an <img> tag lives inside picture on /employees, we should display the full URL to the picture.

site.make at hub.wunder.io is set to install on Drupal 8.0.0-beta4, but current D8 beta is 8.0.0-beta14*.

* subject to change 😉

We need to update the WK hub profile and modules to work with latest updates to D8.