infrastructure/extensions-website
4
8
Fork 10
Code Issues 20 Pull Requests 2 Projects Releases Wiki Activity

Add Open Graph support #192

New Issue
Closed
opened 2024-06-19 16:16:05 +02:00 by Pablo Vazquez · 6 comments
Pablo Vazquez commented 2024-06-19 16:16:05 +02:00
Owner
Copy Link

At the moment, sharing a link to an extension on social media or chat does not include any information through open graph.

Example of a link to an add-on shared on Telegram:
link shared

Add Open Graph support, with at least the following tags:

Global tags:

  • og:site_name

Extension details page:

  • og:title: Page title
  • og:image: Extension's featured image
  • og:image:alt: Extension's tagline
  • og:description Extension's tagline
  • og:url Absolute URL ( extension.get_absolute_url)

Apparently, X nowadays will fallback to OpenGraph so no need to add explicit twitter tags. We can see how it looks without them, otherwise we add it.

At the moment, sharing a link to an extension on social media or chat does not include any information through open graph. Example of a link to an add-on shared on Telegram: ![link shared](/attachments/87683e10-ffe8-4943-8709-dfacc44ae2ab) Add [Open Graph](https://ogp.me/) support, with at least the following tags: Global tags: * `og:site_name` Extension details page: * `og:title`: Page title * `og:image`: Extension's featured image * `og:image:alt`: Extension's tagline * `og:description` Extension's tagline * `og:url` Absolute URL ( `extension.get_absolute_url`) Apparently, X nowadays will [fallback to OpenGraph](https://developer.x.com/en/docs/twitter-for-websites/cards/guides/getting-started#opengraph) so no need to add explicit `twitter` tags. We can see how it looks without them, otherwise we add it.
image.png
88 KiB
Pablo Vazquez added the
Type
Feature
 label 2024-06-19 16:16:05 +02:00
Márton Lente was assigned by Pablo Vazquez 2024-06-19 16:16:05 +02:00
Oleg-Komarov commented 2024-06-20 09:51:37 +02:00
Owner
Copy Link

seems like this change should also resolve #170?

seems like this change should also resolve #170?
Pablo Vazquez commented 2024-06-20 11:43:13 +02:00
Author
Owner
Copy Link

seems like this change should also resolve #170?

Yes, once the current issues are fixed.

> seems like this change should also resolve #170? Yes, once the current issues are fixed.
Márton Lente commented 2024-06-20 12:27:40 +02:00
Owner
Copy Link

The above list of Open Graph tags have been implemented for detail pages, while keeping the fallback defaults for static pages. Example sharing previews:

I also think it fixes #170 as well.

Alternatively we can create a og:image placeholder for detail items and static pages that don't have a feature image, e.g. by making a pixel version of the dark placeholder image we currently use, or by creating a generic 'Blender Extensions' cover image that also works for static pages.

The above list of Open Graph tags have been implemented for detail pages, while keeping the fallback defaults for static pages. Example sharing previews: I also think it fixes #170 as well. Alternatively we can create a `og:image` placeholder for detail items and static pages that don't have a feature image, e.g. by making a pixel version of the dark placeholder image we currently use, or by creating a generic 'Blender Extensions' cover image that also works for static pages.
Pablo Vazquez commented 2024-06-20 15:52:08 +02:00
Author
Owner
Copy Link

The above list of Open Graph tags have been implemented for detail pages, while keeping the fallback defaults for static pages.

@martonlente Thanks!

Alternatively we can create a og:image placeholder for detail items and static pages that don't have a feature image, e.g. by making a pixel version of the dark placeholder image we currently use, or by creating a generic 'Blender Extensions' cover image that also works for static pages.

The cover image would be best, since it can be used as fallback for every page.

Similar to how we do it in Open Data:
blender open data

> The above list of Open Graph tags have been implemented for detail pages, while keeping the fallback defaults for static pages. @martonlente Thanks! > Alternatively we can create a `og:image` placeholder for detail items and static pages that don't have a feature image, e.g. by making a pixel version of the dark placeholder image we currently use, or by creating a generic 'Blender Extensions' cover image that also works for static pages. The cover image would be best, since it can be used as fallback for every page. Similar to how we do it in Open Data: ![blender open data](/attachments/fc92e341-a4d8-4127-8e17-65850427e47b)
image.png
160 KiB
Oleg-Komarov commented 2024-07-19 18:14:12 +02:00
Owner
Copy Link

This seems to be working now. Should the issue be closed? (just keeping the tracker organized)

This seems to be working now. Should the issue be closed? (just keeping the tracker organized)
Márton Lente commented 2024-07-19 18:40:08 +02:00
Owner
Copy Link

Yes, I think the Open Graph support has been completed as outlined in the issue, and it should be safe to close it.

Yes, I think the Open Graph support has been completed as outlined in the issue, and it should be safe to close it.
👍 2
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Normal
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Type
Breaking
Breaking change that won't be backward compatible

  
Type
Documentation
Documentation changes

  
Type
Enhancement
Improve existing functionality

  
Type
Feature
New functionality

  
Type
Report
Something is not working

  
Type
Security
This is security issue

  
Type
Suggestion
New ideas and proposals

  
Type
Testing
Issue or pull request related to testing

No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Márton Lente
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/extensions-website#192
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?