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

Twitter Metadata field support #234

Merged

Conversation

robertjf
Copy link
Contributor

This PR Addresses #191 by adding additional Metadata Fields. The Card type can be selected by dropdown.

@patrickdemooij9
Copy link
Owner

Looks great! I'll take a better look & test it in the following days and let you know if I have any feedback. But really appreciate this PR and the other one that you did!

@robertjf
Copy link
Contributor Author

Thanks @patrickdemooij9 - let me know if I can be of assistance; really itching to get this released so we can use it on a couple of projects :)

@patrickdemooij9
Copy link
Owner

Hi @robertjf
Great PR! Just spotted a few small things. If you want, I can also pick these up but I'll let that decision up to you. Really appreciate the work you do here!

@robertjf
Copy link
Contributor Author

hey @patrickdemooij9 let me know what they are, and I'll jump on them straight away :)

@patrickdemooij9
Copy link
Owner

hey @patrickdemooij9 let me know what they are, and I'll jump on them straight away :)

You should be able to see them above our messages :)

@robertjf
Copy link
Contributor Author

hm. Not seeing them at all..

@robertjf
Copy link
Contributor Author

@patrickdemooij9 are they marked as private by any chance?

@patrickdemooij9
Copy link
Owner

Hmm, I don't see anything related to private in the mobile app. I'll take a look at it tomorrow in the browser. The feedback was:

  • I think the open graph URL should probably belong in the open graph group.
  • Let's put all the Twitter related meta fields in their own group between open graph and extra information.
  • Are you sure that product is a valid Twitter card type? I didn't see it listed in their documentation.
  • The Twitter card type dropdown should probably have an empty option. Currently, there is no way to "empty" your field and use the fallback value.

Hopefully I'll be able to get review points showing for you tomorrow.

@robertjf
Copy link
Contributor Author

great - I'll get to work on those in the meantime.

@robertjf
Copy link
Contributor Author

@patrickdemooij9 I'm about to push up some changes for you - I'm not 100% convinced that the twitter specific fields should be in their own group though; the twitter preview widget is still in the Open Graph group so it's a little disjointed.

Still, I do like the separation. For Facebook I've also added facebook app_id field as well, also in it's own group.

Perhaps we should call the group "Social Media" instead of "Open Graph" and keep it all together?

image

@patrickdemooij9
Copy link
Owner

@robertjf You're right, the preview doesn't really fit then. I think a Social Media Group would be a great idea to do then!

@robertjf
Copy link
Contributor Author

ok, so if we rename the group from Open Graph to Social Media, would that work? and consolidate the fields into that?

@patrickdemooij9
Copy link
Owner

Yes, I think that is the way to go about it

@robertjf
Copy link
Contributor Author

all done :)

@patrickdemooij9 patrickdemooij9 merged commit ad07e56 into patrickdemooij9:dev/Umbraco11 Sep 23, 2023
@patrickdemooij9
Copy link
Owner

PR looks great! I've merged it and I will try to release it somewhere next week. Trying to get a few more changes added for the next version

patrickdemooij9 pushed a commit that referenced this pull request Oct 12, 2023
* 🚧 additional opengraph/twitter fields

* addresses #191 by adding support for Twitter-specific metadata and OpenGraph Url

* added Facebook app_Id and separated twitter fields into their own group

* reconsolidated all social media fields under "Social Media"
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

Successfully merging this pull request may close these issues.

2 participants