WordPress.org

Making WordPress.org

Opened 8 years ago

Last modified 3 months ago

#83 assigned enhancement

Twitter account for jobs.wordpress.net

Reported by: mercime Owned by: coffee2code
Milestone: Priority: high
Component: Jobs (jobs.wordpress.net) Keywords: needs-design
Cc:

Description

Allow freelancers and those seeking WP jobs to follow via Twitter.

Ideally, each published job posting will be auto-posted to said Twitter account.

Change History (12)

#1 @mercime
8 years ago

  • Type changed from defect to enhancement

#2 @mercime
7 years ago

  • Cc mercijavier@… added

#3 @samuelsidler
7 years ago

  • Owner set to coffee2code
  • Status changed from new to assigned

I now have @wordpressjobs, which we'll be using for this.

#4 @mercime
7 years ago

Sweet. Thank you :)

#5 @ChrisWiegman
7 years ago

That's pretty awesome. Great call y'all.

#6 @melchoyce
6 years ago

  • Keywords needs-ui added

This is great. When will jobs start getting pushed to the new twitter account?

We should also add an icon and header image (or even just a color) to the account.

#7 @samuelsidler
6 years ago

@coffee2code: Any update here? :)

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


4 years ago

#9 @tellyworth
4 years ago

  • Priority changed from low to high

#10 @estelaris
14 months ago

  • Keywords needs-design added; needs-ui removed

we need more information as to when is this going to be pushed to the Twitter account so we can provide a design

#11 @tellyworth
3 months ago

Would Jetpack help auto-publish to Twitter, or is the Jobs code too custom for that to work?

#12 @coffee2code
3 months ago

I've never looked into what Jetpack's capabilities are for auto-publishing to Twitter, but jobs aren't much like posts and would likely require customizations.

Jobs are a custom post type. The post content would not likely be anything that should be in (or excerpted in) a tweet. Most of the data for a job is defined as post meta, only some of which would be relevant for inclusion in a tweet.

If we're just tweeting the post/job title with a link to the job, then an out-of-the-box auto-publish functionality can likely do that without any customization. But having a bunch of "WordPress Developer [url]" tweets don't seem all that great.

Some ideas:

  • For greater context, prefix tweet to make it clear we're posting a job. E.g. "New job posting: [title] [etc]" or "Just posted: [title] [etc]"
  • Like the jobs front page, we probably want to include the job category, job type, and location.
  • Company name might be good as well.
  • Salary/budget might not be so good to include, but maybe?
  • Probably want some hashtags.

Example:

New job (development): WordPress Developer by Some Company, LLC
Full Time in London, UK
[url to job]
#wordpress #jobs

Considerations:

  • Location is an optional field, so tweet template/constructor should account for it not being present.
  • Tweets provide long-living links to jobs, even though jobs only exist on the site for 21 days max. Do we want to do auto-delete tweets once a job has been removed (either closed or deleted)? Does Jetpack facilitate that as well? Bear in mind that jobs routinely get closed earlier than 21 days (sometimes even after a few hours), so we can't just assume "old" jobs are obviously no longer available since it's possible the most recently posted job could quickly become unavailable.
  • Very relatedly, we want to be able to ensure deletion of associated tweets in cases where a job is posted that is deemed invalid/inappropriate/spam after publication. If not automatic, or at least manually achievable through the site, then it becomes burdensome to grant and manage multiple people having access to the Twitter account or having a bottleneck with moderators asking the privileged few to delete tweets. Not to mention that a multi-step process adds to the time burden for moderators/admins and increases potential for a job being deleted but not the associated tweet.
  • Another way to look at it, retaining tweets for defunct job postings would give Twitter users a bad experience since they wouldn't know which job postings are legitimate without clicking through to the job and either finding the job posting or an error page.
  • Presumably the #needs-ui keyword for this ticket relates to the Twitter profile avatar and header image, and if not, then those would need to be decided upon / designed.
  • We'd need to ensure the necessary Twitter card tags (and open graph tags) are defined for jobs so that appropriate Twitter cards can be generated. (This should be done even if we don't auto-post to Twitter.)
Note: See TracTickets for help on using tickets.