July 6th, 2009 by Arjan Olsder Posted in Analysis & Editorial | No Comments »
Last Friday we visited DGADAG, an event from the Dutch Games Association. The event started with a keynote called Journalists are lazy. It featured tips that are important when contacting the press.
When it comes to news, make sure you deliver it. Journalists will not spend a whole lot of time to find your release on the net. Also, make sure when you e-mail journalists, to have their addresses in BCC. Getting a journalists private e-mail account is always better then a general e-mail account.
The following pointers are important when creating a press release;
- Don't make press releases too big
- Place important news first
- Don't use more text then needed
- Do use enough text to make sure your message is clear
- Check your spelling
- Put the text in the body of the e-mail
- Include a word file as well for copy/paste actions
- Don't use PDF or any other type of file that is not easy to copy/paste from
- Remain objective; anything that has nothing to do with the core subject will be removed anyway and so, cause more work for the journalists
Providing assets? Mind these pointers as well;
- Make sure 300DPI artwork is available for print publishing
- Link to large assets (i.e. make a portal for them)
AND OVERALL: Never irritate a journalist!
MGB Comment – We don't need 300DPI materials, but make sure we have your logo in Vector.
This keynote was delivered by Eric Bartelson and Matthijs Dierckx Kuijper from Control Magazine.
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs