I would say that you should probably not put all these people in the same team. Although it would be an interesting experiment.
I'm going to have to imagine your product and team setup a bit, but usually I have found you get:
Developers - you want them to implement features for your product
This is the backbone of your scrum team because you have introduced scrum to either stop them doing whatever they think is good today, or to cut down on a overly long waterfall process
Testers - you want these guys to be your acceptance test for the features
You can put testers in a scrum team and many people do. But I find it moves them away from the 'acceptance of feature' role and into a test automation role. This puts pressure on the PO to write detailed specs rather than relying on test to pick up problems and raise them as bugs
Designers - you want these guys to sell you their cool designs
You can put these guys in the team, 'Design page X' is a nicely scrum-able task
Product Manager - you want this guy to think up how to improve the product
You should put them on the team as the product owner
Support - you want these guys to keep customers happy
I wouldn't put these guys on the scrum team. I don't think you can tell customers to wait for their help request to go in the backlog and be prioritized, and if you did you would need a team to do it nicely.
Content writers - you want to update the content on your website
I wouldn't put them on the scrum team. one of the features of your product should be 'Content management interface' once this is complete the content writers should be able to use it to do their stuff regardless of the scrum.