what's the procedure to get whitelisted for using https://developers.google.com/gmail/markup/reference/article schema?
your published form is only working for actions and as I would like to mostly use e-mail notifications for new news (for categories user specificly requests after double opting in) i'm wondering how this is done.
also with regard to your article schema, do you plan to make it compatible with article schema (https://developers.google.com/structured-data/rich-snippets/articles) .. both links claim to be schema.org compatible.
Thank you,
Primoz
You will have to submit a form and provide a email with the schema you're trying to implement. I've noticed the form doesn't include "article" in the selection. I would just state in the description that you're interested in article schemas.
Be sure to check out their guidelines:
https://developers.google.com/gmail/markup/registering-with-google?hl=en#email_sender_quality_guidelines
For your last question, on the bottom of the Article documentation it states "Note: Some of the schemas used by Google are still going through the standardization process of schema.org, and therefore, may change in the future."
You can also refer to: https://developers.google.com/gmail/markup/reference/schema-org-proposals
Related
I am new to the Inheritance process, I try to create a dynamic Work Item
Where selection on one field value will Show/Hide another field.
In the TFS 2018 i could fill the values Using different global lists - which are not available any more.
Using Azure DevOps Server 2019.
I tried using the Rules page on the process template and couldn't find this option - this is the only documentation i found
https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/custom-rules?view=azure-devops
Currently the answer is no cannot show\hide fields.
Found a question on Microsoft site - no realy an answer but some sort of workaround...
https://developercommunity.visualstudio.com/idea/545504/hide-custom-fields-in-the-inherited-model.html?childToView=604861
haven't tried it yet
I'm afraid that there's no such option supported in TFS&VSTS rules now. Until now, we just support some of conditions and actions option which list on the doc.
You can raise your feature demand here to promote development of richer features.
Note: After suggest raised, you can vote and add your comments for this feedback. When there are enough communities vote and add comments for this feedback, the product team member will take this feedback seriously
I'm a beginner for rails application, I have troubled some issue which is display related post, I already show post separately according to id I have not any idea how to show related post.
Below my code for show post separately according to id:
def postDetails
#details= Post.find(params[:post_id])
end
Now how can I rich this solution?
This is not an answer, so I'll delete if required.
--
Your question is highly ambiguous, meaning that it's open to interpretation in many different ways. Whilst not a problem, when it comes to application functionality, you need to be as specific as possible.
Contrary to the new buzzwords of "full stack engineer", "devops" etc - the core of computing is to design functions & algorithms which "compute" data. Your case is exactly the scenario where a professional developer would outline a spec, and work towards implementing it.
To answer your question as broadly as you asked it, you have to define how you wish to "relate" your posts.
There are several options (all involve data sampling) --
define each post by "tags" or similar categorization
create an algorithm to parse the title, pull out keywords & search for them
have users specifically define which posts are "related"
As you can see, there is one constant with the above - you need a "benchmark" to associate data. Be it keywords, tags, associated posts - you have to be able to identify the data you want.
Thus, you'll have to define the pattern you wish to employ. I can talk through each option; it would be too much to write without knowing how you want to do it.
my first entry here.
I'm trying to add a comment system to our Posts model. However, I am not sure of the best way to go about it for a number of reasons. I'd like the comment system to be similar to that on Forrst.com but i'd rather have visitors who comment not need an account as the site is our company site not a large community.
Outline of features are:
Visitor can comment on post, entering name, email and comment.
Our team members can comment, i'd like these to be styled differently so would like the system to know it was from one of our team, they will be logged into the system when leaving a comment.
Visitors and team members can reply to a comment. The system needs to know which comment it was in reply to.
Lastly i'd like the system to know if the comment was written by the post author.
I have looked and been trying out acts_as_commentable_with_threading which seems perfect except everyone needs a user account to leave a comment, something I am trying to avoid unless anyone has other thoughts on that?
I have also implemented this myself by creating a comments model and using awesome_nested_set for the threading. Within the comments model I have a user_id which is only populated if the user is logged in (meaning they must be a team member), this seems a little messy though.
Does anyone have any thoughts on this?
Oh, and I would love each person to be notified of a reply to their comment (if pos).
Thanks in advance.
There are lot of tools available to post comments and working with ruby on rails.
http://ruby-toolbox.com/categories/rails_comments.html
also you can customize according your own requirement instead of writing a messy code.
If you do not want to integrate a third-party service like Disqus, you have Juvia The Comments and Commontator. Also you can count with opinio as alternative. but only with Rails 3 and at the moment and as notice the development seems stalled.
I am about to start working on my second ever Rails application and could do with some advice. It will probably help in my head typing this question anyway!
The application's purpose is to track and monitor marketing campaigns. That makes it sound way more professional that what it actually is though.
An example usage:
Add list of possible client leads to application
Create a new "campaign" in the application
Choose who on the list of possible client leads should receive the
campaign
If and when a response is received it should then be possible to go into
that client lead's profile and mark
as "Positive Response" or "Negative
Response" etc..
Once the campaign is completed it should be marked as complete, I should be able to view in a campaigns profile who was a recipient of it and likewise if I view a client lead's profile I should be able to see which campaigns were sent to them and when.
That's the general idea of the application. I have made the framework and pushed it to GitHub:
http://github.com/dannyweb/Marketing-Manager
I am trying to get an idea of what models I would need, what sort of associations they should have etc.
I am unsure whether to use something such as acts_as_taggable and give each client lead a tag which relates to a campaign name?
If anyone can offer their thoughts or ideas on how this should be structured it would be greatly appreciated.
As it's my second Rails application - I am still very much a beginner, so please be kind! The application will remain open source on GitHub if anyone is reading this and would like to use the application.
Thanks,
Danny
I think you shouldn't turn to plugins (like acts_as_taggable) just yet. I'm going to give you some pointers but not much, because figuring out what works or doesn't is exactly what will help you learn more about rails.
So, you will have a 'Client' model and a 'Campaign' model. They have an N->N relationship (A campaign can involve multiple clients, and a client can be a part of multiple campaigns).
Therefore, you'll also need another table, which will have the 'client_id' and the 'campaign_id'. You also want to store on this table wether the client replied to it, so it'll need a 'replied' boolean flag on it as well. If you call this table 'campaign_messages', then client will need to link to campaigns using 'has_many :campaigns, :through => :campaign_messages'.
With these in place, you'll be able to list all clients on a campaign or all campaigns of a client easily. You'll also probably not need REST resource for the campaign_messages, only clients and campaigns.
That's all the detail I'm going to provide you. I think it'd be better if you just followed your approach now and asked how it could be improved instead.
Cheers and good luck
As a part of the signup process for my online application, I'm thinking of tracking the source and/or search keywords used to get to my site. This would allow me to see what advertising is working and from where with a somewhat finer grain than Google Analytics would.
I assume I could set some kind of cookie with this information when people get to my site, but I'm not sure how I would go about getting it. Is it even possible?
I'm using Rails, but a language-independent solution (or even just pointers to where to find this information) would be appreciated!
Your best bet IMO would be to use javascript to look for a cookie named "origReferrer" or something like that and if that cookie doesn't exist you should create one (with an expiry of ~24hours) and fill it with the current referrer.
That way you'll have preserved the original referrer all the way from your users first visit and when your users have completed whatever steps you want them to have completed (ie, account creation) you can read back that cookie on the server and do whatever parsing/analyzing you want.
Andy Brice explains the technique in his blog post Cookie tracking for profit and pleasure.