28
edits
Websites/Blog: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
= FAQ = | = FAQ = | ||
'''How will this central content platform look like?''' | |||
Our new workflow will be built around our main Mozilla Blog: Each team’s blog will have its own content category (e.g. Privacy, Security, Identity etc.). All categories will be accessible from the main Mozilla Blog landing page. Once someone clicks on the category, your team’s blog will show up. Of course your blog will still have its own URL and will be accessible just as it was before. For users, this means that they will be able to access all content in one place, the Main Mozilla Blog. For you and your teams, this means that your workflow will be simplified and you will receive more traffic. | |||
'''Will the design of my blog change?''' | |||
The design of all blogs will be updated with the main look and feel of the Mozilla brand. A good example of how this will look like is the Mozilla Privacy Blog (blog.mozilla.com/privacy), <br>which has already been overhauled and now matches our overall Mozilla Blog design. This way, we will be able to maintain and update the design across all content areas <br>as a whole all at once and don’t have to update blog designs individually. | |||
'''How will my blog be integrated into the main Mozilla Blog?''' | |||
Your blog (e.g. Security or Privacy) will be listed as a category on the right rail of the main blog's Wordpress theme. The workflow will allow the bloggers to continue to file posts under as many categories as they please, but will keep all of Privacy content in one folder and all of Security content in a different folder. This way teams won't bump into one another. | |||
'''Will my blog’s URL still be available? Will my categories and links to my blog posts still be there? ''' | |||
Yes, your blog will still available at your URL (e.g. blog.mozilla.com/privacy). All links will still be working and redirecting to your blog posts. Team categories and archives will not change or be lost. Content will be organized by team and in silos – your workflow will not change by much at all, changes will be hardly noticeable for you. | |||
'''How will this affect my blog’s traffic?''' | |||
We'll help you get your message out to the world Blogs rolled up under the main Mozilla Blog will receive more traffic. We will also work on improving your blog’s SEO, content, and metrics as an ongoing project. We will be able to do more and better content strategy and coaching across bloggers@mozilla.org. We will still be able to measure your blog’s traffic separately. | |||
'''What happens to my blog’s content? How will it be migrated?''' | |||
The PR team will migrate your existing content over to the new platform. Once this is done, the blog will go through our regular QA. After the relaunch, you will receive your new log-in details for you and your team and are ready to kick-off blogging again. Your author details will not change. But even as people move on and teams change, all of our content will always have an organized home. | |||
'''Will users still be able to subscribe to a single blog’s / category’s RSS feed?''' | |||
Yes, each blog and category (e.g. Privacy or Security) will still have their own RSS feed users can subscribe to. <br> | |||
= Overview = | = Overview = | ||