Date of publication: 06/06/2016
Source: GVSO Blog
In the last weekly meeting with my mentors, we agreed to remove the hook that alter the user login. Instead, we decided to use blocks from the Social API parent modules since this is the most basic, flexible and extensible way to render things in the page. This is especially true if you want to provide integration points, and then render based on those on behalf of an unknown number of implementer modules.
Thus, this week on Google Summer of Code I was working to allow site builders implement user login through social network accounts and make this functionality available as a block. For example, the site builder could enable a Social Auth integration, like this version of simple_fb_connect, and customize a block in any region he wants.
Approaching the issue
Notice that the Social Auth Block gets the Immutable Configuration of the Social Auth which store the data provided by the implementer. This data is composed by a route and a path to an image. For instance, take a look at how Simple Facebook Connect supplies this information: https://github.com/GVSO/simple_fb_connect/blob/8.x-2.x-social_api/simple_fb_connect.install.
Regarding the icons, there is an open issue on where to get the images that the implementers will use at https://www.drupal.org/node/2697771. In later versions, site builders will be able to select which kind of icons they want to display (polygon, rectangular, rounded, etc.).
As always, feel free to contact me if you have any question. You can also collaborate with the Social Initiative projects (social_api, social_auth, social_post, and social_widgets). We also have our weekly meetings, so follow the Social Initiative and join us on Fridays.
Stay tuned for the next weekly summary!