Updated: Comment #1

Problem/Motivation

At the moment if a d.o issue is posted on twitter, it is just a link with no additional information. It would be really nice if we could get druplicon like functionality whereby twitter gives a basic summary of the issue in the form of a twitter card.

Proposed resolution

Let's add metadata tags to the drupal issue node markup so that twitter (and other sites) can get better information from links.

Add metatags directly to the markup (maybe in a template file)

Remaining tasks

  • Agree on which fields to add to card

    Work in Progress list:
    • Druplicon
    • Drupal
    • Project
    • Title
    • Status
    • Priority
    • Category
    • all tags
  • Install metatag module
  • Add metatags and export to code
  • Review permissions
  • Get code live to d.o
  • Validate and apply to twitter approval
  • Enjoy

Metatag Module
Twitter Card Docs

This issue was inspired by a tweet by @YesCT who noticed github twittercards.
Tweet by YesCT

CommentFileSizeAuthor
#22 drupalorg_metatags.zip1.14 KByanniboi
#12 views remove wrapper around more link add class to the link 2226923 sprint1 drupal dev.png73.31 KByanniboi
#12 Drupal.org drupal_org on Twitter.png87.16 KByanniboi
yesct_tweet.png453.78 KByanniboi
#1 twittercard.png33.86 KByanniboi
#2 dashboard.png151.32 KByesct
#2 search.png248.28 KByesct
#2 issue.png310.27 KByesct
#2 rocketship.png303.44 KByesct

Comments

yanniboi’s picture

yanniboi commented
Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new twittercard.png33.86 KB

I have started working on this on a d.o dev server.

I am implementing a preprocess function to put the metatags in the page header on issue nodes.
We can not test from the drupal servers directly because they don't allow site crawling preventing twiiter to directly check pages for metadata.

So far I have implemented a summary card with the following code:

<?php

function project_issue_preprocess_node(&$vars) {
  $metadata = array(
    'title' => $vars['title'],
    'description' => $vars['body'][0]['value'],
    'card' => 'summary',
    'site' => '@drupal',
    'creator' => '@drupal_org',
    'image' => 'https://drupal.org/files/druplicon.small_.png',
  );

  foreach ($metadata as $name => $content) {
    drupal_add_html_head(array(
      '#type' => 'html_tag',
      '#tag' => 'meta',
      '#attributes' => array(
        'content' =>  $content,
        'name' => 'twitter:' . $name,
      )
    ), 'twitter_' . $name);
  }
}

?>

Using the twitter card validator tool this gives us the following card:

twitter card demo

yesct’s picture

yesct commented
StatusFileSize
new dashboard.png151.32 KB
new search.png248.28 KB
new issue.png310.27 KB
new rocketship.png303.44 KB

to decide what info we should include, we can look at where we have already decided what kind of info to put in overviews.. like

dashboard

issue search results

issue page

rocket ship

yesct’s picture

yesct commented
Issue summary: View changes

1.
Based on that I would suggest:

Project
Title
Status
Priority
Category
all tags

---
2.
I think it would be ok to leave out the trimmed issue summary, but do not feel to strongly about that.

---
3.
Can we color for status?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Why not just use metatag and assign some reasonable defaults for the appropriate content types?

yanniboi’s picture

yanniboi commented
Issue summary: View changes
Issue tags: +d.o support, +Needs architectural review

I have had a look at metatag module on a vanilla drupal install.

It requires ctools and token module (which I would say is reasonable) and has a separate twitter cards sub-module with the relevant specific settings. It has a separate UI module which can be deactivated once sensible defaults per content type have been created and exported to code using ctools exportables. It uses tokens so most node information is accessible from the UI.

All in all, I think using this module is a good idea, and since the UI can be disabled it should not cause any problems once defaults are set.

I think new modules to d.o need performance review?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

@yanniboi: A note of clarification: the UI submodule is an empty holdover from an alpha 3 years ago, it'll be removed post-1.0; the UI cannot be disabled, excluding by permissions.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Component: Drupal.org theme » SEO
Status: Needs review » Active

Should we expand this to also cover other meta tags provided by the Metatag module?

drumm’s picture

drumm
he/him
Location NY, US
commented

For performance, I expect this to load already statically cached items, so it wont have much of a performance impact, relatively. We should pay attention to make sure that is true.

For scope, don't expand it. Other issues can build on this later. If this expanded to include all meta tags, it may never get resolved.

Since the configuration is exportable, that should be done in the drupalorg module, either in Features, or however it works best.

What this does need is a 1.0 release. If there are any security problems, it is good to have the security tram process. And that would be a good general sign from the module maintainers that it is good to use on production sites.

yanniboi’s picture

yanniboi commented
Issue summary: View changes

Ok, if the UI cannot be disabled, we just need to make sure regular users cannot override the defaults when posting/editing issues.

What this does need is a 1.0 release.

I agree with @drumm, @DamienMcKenna do you have a meta/blocker issue to get a full release?

yanniboi’s picture

yanniboi commented
Related issues: +#2175021: META: Plan for Metatag 7.x-1.0-rc1 release

Nevermind, I found the Meta: #2175021: META: Plan for Metatag 7.x-1.0-rc1 release

yanniboi’s picture

yanniboi commented
Related issues: +#2019745: "Unknown taxonomy_term" or "Unknown node" - No way to create new default metatag

Installing metatag on drupal.org (dev site) is causing this error: #2019745: "Unknown taxonomy_term" or "Unknown node" - No way to create new default metatag

This will need to be fixed in the 7.x-1.0 release.

yanniboi’s picture

yanniboi commented
StatusFileSize
new Drupal.org drupal_org on Twitter.png87.16 KB
new views remove wrapper around more link add class to the link 2226923 sprint1 drupal dev.png73.31 KB

OK, good news, my personal dev domain was approved by twitter so I can post to twitter and see the resulting twitter cards.

I installed metatag on a drupal.org development clone, set the markup tags, copied the raw page source to my server and tweeted a link. The attached image is the resulting twitter card:

yesct’s picture

yesct commented

I think #12 is good enough for a start.
Now we just have to update the issue summary for next steps/remaining tasks (release, evaluate security, performance analysis?) and what might block this. (I'm a little confused about if the plan is to use meta tags, etc on d.o, so updating the issue summary would be great... or do we need more feedback first?)

I think when things need to get deployed on d.o there needs to be instructions in the issue summary also...

killes@www.drop.org’s picture

killes@www.drop.org commented

I don't want twitter to have any of the content I create, please make sure you take care of that.

yesct’s picture

yesct commented

@killes I'm not sure what we can do. d.o has the content.
And individuals post links to twitter... which happens without this issue.

i dont think adding the meta tags to d.o gives the content to twitter, but I might not be understanding.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

@killes: April fools? :p

For anyone checking in on this, adding Twitter Cards support will not notify Twitter that content has been posted, it only provides a way of customizing what is displayed when a d.o link is pasted into Twitter and someone views the tweet containing the link on either the website or one of the Twitter apps that supports nested meta data (the official app, etc); it's 90% identical to the Open Graph stuff that Facebook uses.

killes@www.drop.org’s picture

killes@www.drop.org commented

@DaminMcKenna: not at all, but thanks for the explanation.

basic’s picture

basic commented
Component: SEO » Other
tvn’s picture

tvn commented

Metatag module was installed on Drupal.org yesterday for another issue. "Metatag: Twitter Cards" sub-module is not enabled yet. Whomever is interested in moving this further can request the fresh D.o dev site and work on configuration needed.

yanniboi’s picture

yanniboi commented
Assigned: Unassigned » yanniboi

Great! I'll take this one please! :)

tvn’s picture

tvn commented

The dev site will be ready in ~1,5h. The url will be https://twitter-drupal.redesign.devdrupal.org/.

yanniboi’s picture

yanniboi commented
StatusFileSize
new drupalorg_metatags.zip1.14 KB

I have started to implement this on the dev site, however I cannot test this, because the http access authentication on the dev server prevents twitter from crawling the site.

How would the process of pushing this to drupal.org work anyway? Would the config go into a feature? Or would someone manually alter the metadata config?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Needs work

@yanniboi: Per the documentation, the "twitter:creator:id" meta tag should be a numeric string, not the Twitter user name. I think it'd be useful to update the global settings, possibly via hook_metatag_export_default_alter(), rather than just the project_issue. Also, it might be worth setting "twitter:site".

drumm’s picture

drumm
he/him
Location NY, US
commented
Project: Drupal.org infrastructure » Drupal.org customizations
Version: » 7.x-3.x-dev
Component: Other » Code

This project has a few features exported in the features directory. That is probably the best way to get the configuration deployed.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Assigned: yanniboi » Unassigned

@YesCT: Thanks for pinging me.

Metatag 1.0-rc1 is out, so we should start looking at this.

We have the following meta tags at our disposal:

  • Twitter card type: should be "summary".
  • Creator's Twitter account: should this be the account of the person who started the issue?
  • Description: I think the default should be fine, i.e. the node summary.
  • Image URL: Druplicon? Also the width and height tags.

Other tags aren't relevant.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: » #2402211: META: Add appropriate meta tags to drupal.org for all entities

I've added a master issue to identify all "things" that need meta tags: #2402211: META: Add appropriate meta tags to drupal.org for all entities

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented

#2478807: Adjust metatag settings to include [node:title] in description and/or enable Metatag: Open Graph was opened as a short term solution

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

To clarify: this issue is just for focusing on Twitter Cards meta tags for the project issue content type, #2402211: META: Add appropriate meta tags to drupal.org for all entities is an umbrella issue for going through each entity type and identifying the appropriate meta tags for each.

FYI I'll be around during DCLA week if anyone wants to sit down with me and work out some of these? Not sure I'll have time until then anyway ;)

tvn’s picture

tvn commented

Hey Damien,

I'd love to work with you on this at DC LA, either at pre-sprint before Con or during the Friday code sprint. Let's do it!

wmostrey’s picture

wmostrey commented

In the meantime the metatag module has been installed so I guess it's just a matter of configuration?