Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Media page #21

Closed
4 of 5 tasks
stevepiercy opened this issue Apr 18, 2015 · 15 comments
Closed
4 of 5 tasks

Add Media page #21

stevepiercy opened this issue Apr 18, 2015 · 15 comments
Milestone

Comments

@stevepiercy
Copy link
Member

  • Create page, add to nav, etc.
  • Twitter widget
  • Google Group widget
  • GitHub widget (blocked)
  • Choose Twitter handle and update widget
@stevepiercy stevepiercy added this to the v0.2 milestone Apr 18, 2015
@stevepiercy
Copy link
Member Author

Do we have content for this item?

@pauleveritt
Copy link
Member

It was first conceived two years ago. I suspect we’ve had some new things happen since then. :)

Of course, “news” pages are chronic sore spots in projects. When the newest news is a year old, it’s embarrassing. We can choose to axe this.

—Paul

On Oct 27, 2015, at 4:28 PM, Steve Piercy notifications@github.com wrote:

Do we have content for this item?


Reply to this email directly or view it on GitHub #21 (comment).

@stevepiercy
Copy link
Member Author

Agreed. The closest thing to "news" we have is when we make announcements of releases, and I think we do that more effectively under the new Resources page.

Instead I propose another page to consist of tweets, Google Group posts to pylons-discuss, podcasts, and any other online media mentions. Suggest the name "Media", which translates fairly easily to other languages and cultures and has an implicit context of "Social Media" and "Press Release".

@stevepiercy stevepiercy modified the milestones: v0.2, v0.3 Oct 28, 2015
@pauleveritt
Copy link
Member

Is the idea that these are JS widgets that automatically pull in the information? If not, then we’re back to a hand-curated News section.

—Paul

On Oct 28, 2015, at 5:46 PM, Steve Piercy notifications@github.com wrote:

Agreed. The closest thing to "news" we have is when we make announcements of releases, and I think we do that more effectively under the new Resources page.

Instead I propose another page to consist of tweets, Google Group posts to pylons-discuss, podcasts, and any other online media mentions. Suggest the name "Media", which translates fairly easily to other languages and cultures and has an implicit context of "Social Media" and "Press Release".


Reply to this email directly or view it on GitHub #21 (comment).

@stevepiercy
Copy link
Member Author

Twitter and posts from Google Groups can be JS widgets.

I don't know of any other JS widgets for podcasts or other media mentions, so I think those would have to be hand-curated, if we go that route.

@stevepiercy
Copy link
Member Author

BTW, my proposal at this point is to use the name "Media" for a new page that contains only tweets (of whatever Twitter handle we choose) and pylons-discuss posts as JS widgets, and nothing else.

@pauleveritt
Copy link
Member

I like the name “Media”. I think if you can get Twitter and Google Groups (and perhaps GitHub commits?) as widgets, then it completely alleviates the it-gets-stale argument. Good thinking.

—Paul

On Oct 29, 2015, at 7:22 AM, Steve Piercy notifications@github.com wrote:

BTW, my proposal at this point is to use the name "Media" for a new page that contains only tweets (of whatever Twitter handle we choose) and pylons-discuss posts as JS widgets, and nothing else.


Reply to this email directly or view it on GitHub #21 (comment).

@stevepiercy
Copy link
Member Author

See my private email regarding the Twitter handle.

I can get Google Groups for pylons-discuss.

I don't know of any GitHub JS widget.

@pauleveritt
Copy link
Member

It’s old, but perhaps this GitHub commits widget still works:

https://github.com/alexbeletsky/github-commits-widget

—Paul

On Oct 29, 2015, at 7:57 AM, Steve Piercy notifications@github.com wrote:

See my private email regarding the Twitter handle.

I can get Google Groups for pylons-discuss.

I don't know of any GitHub JS widget.


Reply to this email directly or view it on GitHub #21 (comment).

@stevepiercy stevepiercy changed the title Add News page Add Media page Oct 29, 2015
@stevepiercy
Copy link
Member Author

I think I've gone as far as I can with the access I have to the various sources for widgets.

@stevepiercy
Copy link
Member Author

The Google Group widget does not work for me on localhost:

Refused to display 'https://groups.google.com/forum/embed/?place=forum/pylons-discuss&showsearch=true&showpopout=true&parenturl=http%3A%2F%2Flocalhost%3A8080%2Fmedia.html' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

The Google Group help suggests that if it does not work, then add the website's domain name, trypyramid.com in this case, once it is deployed. This one is in Blaise's hands.

I do not have access to @Pylons. I think @goodwillcoding controls that account. So I used @trypyramid for the mockup.

I tried the GitHub widget Paul suggested, but it didn't work out of the box. I have a feeling this is not possible through javascript alone, but requires oauth and access to the Pylons GitHub account settings to create an Application or whatever they call it.

@goodwillcoding
Copy link
Member

twitter widget:

<a class="twitter-timeline" data-dnt="true" href="https://twitter.com/pylons" data-widget-id="683880296756850688">Tweets by @pylons</a>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>

@stevepiercy
Copy link
Member Author

@goodwillcoding thanks, added in stevepiercy@ff4ac17

@stevepiercy
Copy link
Member Author

twitter handle is now @trypyramid, per stevepiercy@466e55a

@stevepiercy
Copy link
Member Author

Closing. Work is on PR #45.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants