Skip to main content

Community Blog Guidance

Suggest edit Updated on September 14, 2021

Why Contribute to the Blog?

Contributing content in your area of expertise is a great way to build your brand as a Pega professional.  

“This blog is for us and by us. The posts that we publish will promote engagement by sharing tips, tricks and high impact practices from you, the members of our community. Every member – from every product role and organization type – will have an opportunity to share what works and to explore complex issues that truly matter.” 

After publication, promote your submission through social channels and continue to expand your Pega network.  

What type of content are we looking for?

Audience:

Write with a role in mind: 

  • Business Architect
  • Decisioning Consultant
  • Front-End Developer
  • Lead Business Architect
  • Robotics System Architect
  • Scrum Master
  • System Architect 
  • User Experience Designer

Style and Voice: 

Write like you are writing to a friend, not like you are writing about a topic. 

Intent: 

Write in order to provide value, with the aim of changing the reader. Ask the question "What is it that my reader will be able to do, or do better, as a result of reading this piece?"

Content Template

Use this form to write your first draft: Blog outline template

Pega editor publishes your post on Community Blog

Submission Guidelines

Format

  • Articles are a minimum of 500 words and a maximum of 1,200 words
  • Blogs exceeding 500 words should have a least one subhead
  • In most cases, images should not appear in the body of the text.

Images

  • Pega editors will select all header images for posts on the Community Blog. 

 

 

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us