DEV Community

Cover image for Sagma vs Sagma Gen 2.0: What’s Changed in the New Zendesk Theme?
FreePixel
FreePixel

Posted on

Sagma vs Sagma Gen 2.0: What’s Changed in the New Zendesk Theme?

Choosing a theme for a support portal involves more than just comparing how two homepages look. Things like how easy it is to navigate, the structure of the content, customization options, licensing, and ongoing maintenance can all affect how a team manages its support experience. This makes Sagma vs Sagma Gen 2.0 a useful comparison for teams using Zendesk or thinking about a new design for their support portal.

The original Sagma Theme and Sagma Gen 2.0 are built for the same general purpose, but their product offerings are different. Gen 2.0 has many visual options, two editions, different levels of access to the source code, a 14-day trial, and an included creative workspace. The original version is simpler and may still meet the needs of teams that don't need those additions. Knowing the differences between the options can help you decide which one is best for you.

Key Takeaways

  • Sagma vs Sagma Gen 2.0: The original Sagma has a simpler product structure, while Gen 2.0 adds more configuration and customization options.
  • Gen 2.0 offers four visual variants - Amethyst, Aquamint, Crimson, and Ember.
  • Gen 2.0 is available in Standard and Developer editions, with different levels of source-code access.
  • Gen 2.0 includes a 14-day free trial, while the original Sagma has a simpler purchase model.
  • The right choice depends on your content structure, customization needs, technical resources, and budget, not simply on which version is newer.

What Is the Original Sagma Theme?

Sagma is a theme that can be used in many ways. It is designed for organizations that use Zendesk. It is organized in a way that makes it easy to find common support content. It includes sections such as "Getting Started," "Guide," "Knowledge Base," "FAQ," "Community," "Training," "Forum," and "Contact."

The theme can be used by all kinds of industries and organizations, including technology, education, travel, food, startups, IT, medical, construction, marketing, fashion, government, NGOs, and other businesses.

Its simple structure can work well for teams that mainly need to organize documentation and support resources in a familiar Help Center format. The available layout also includes promoted articles, a help forum, and a status dashboard.

The product page reviewed for this comparison lists the original Sagma Theme at US$99, with US$299 shown as the original price. Because the prices and deals on these items can change, it's a good idea to check the product page for the latest price before you buy.

What Is Sagma Gen 2.0?

Sagma Gen 2.0 is the newer version of the theme, with several additions to its product structure and customization options.

It is available in two editions and four visual variants. You can try it for 14 days for free. There are different levels of access to the source code, depending on the edition.

The theme is designed for Zendesk Guide and is meant to help organize support content. It also gives teams more choices around the visual starting point and technical customization.

For teams with developers, the difference between the Standard and Developer editions is particularly important because the level of access to source code is not the same.

Sagma vs Sagma Gen 2.0: What Has Changed?

The main differences become easier to understand when the two versions are considered feature by feature.

Four Visual Variants in Gen 2.0
One of the more visible additions in Gen 2.0 is the choice of four handcrafted variants:

  • Amethyst
  • Aquamint
  • Crimson
  • Ember

Each variant provides a different visual starting point for the support portal.

This can be useful for teams that want to begin with a style that is closer to their existing branding rather than working from a single default appearance. The original Sagma product information reviewed for this comparison does not show the same four-variant offering.

The choice of variant does not replace the need for good content organization. Regardless of the visual style, categories, search, navigation, and article structure remain important parts of the overall support experience.

Standard and Developer Editions
Gen 2.0 separates the product into two editions, giving teams different levels of access to the theme's source code.

The Standard Edition lets you see some of the source code, but not all of it. You can set important settings using the Admin UI.

The Developer Edition lets you see the source code. To do this, click on the Edit Code option in the theme customization area. You can also manage important settings through the Admin UI.

This distinction is important for teams that expect to make significant technical changes.

If the administrators use the available configuration settings, they may not need additional source code access. Teams that work on templates or other theme code may have different needs.

Creative Suite for Visual Assets
Gen 2.0 also includes Diziana Creative Suite, a workspace for working with visual assets.

The included tools give you access to images, illustrations, icons, and SVGs. You can customize these assets and insert them into Help Center content. The product information also says that free daily credits for microstock assets are available for up to three years.

For teams that often use visual assets in support articles and other Help Center areas, this can make part of the content workflow easier.

However, it is not necessary to create a useful support portal. Teams that already have their own design resources or asset workflow may not need this additional functionality.

Pricing and Editions

Pricing is one of the clearest differences between the two products.

The original Sagma product page reviewed for this article lists the theme at US$99, with US$299 displayed as the original price.

Gen 2.0 is listed in two editions:

  • Standard Edition: US$299 one-time
  • Developer Edition: US$349 one-time

Both Gen 2.0 editions include free upgrades to future versions according to the product information reviewed.

The pricing shown here is based on the product information available during the comparison and may change with future updates or promotions.

Rather than looking only at the price difference, teams should consider whether they actually need the additional edition options, visual variants, source-code access, and included creative tools.

Trial, Support, and Updates

Gen 2.0 includes a 14-day free trial, and the product information states that no credit card is required to start it.

According to the information reviewed, both the original Sagma and Gen 2.0 include 90 days of email support for the relevant product.

Gen 2.0 is also described as actively maintained and includes free upgrades to future versions.

These details are important when choosing a Zendesk Theme, especially for teams that want to check the theme before buying it or need help setting it up.

Licensing and Zendesk Requirements

The original Sagma information specifies a license for one Zendesk Help Center.

Gen 2.0 specifies a license for one Zendesk Help Center or Brand.

Both versions also have requirements around the Zendesk subscription. The product information says that users should have Zendesk Guide Professional or higher, or an eligible old Zendesk Guide subscription that lets you import and edit theme code.

Before choosing either version, it's a good idea to check what your current Zendesk account can do. The subscription and customization options that are available can affect how the theme is installed and maintained.

How Do These Changes Affect Help Center Design?

A theme controls the presentation of support content, but it is only one part of the customer experience.

Good Help Center design should make it easy for customers to understand the available resources and find the information they need. Search, categories, navigation, article organization, and responsive behavior all contribute to that experience.

Before changing themes, review how your current support content is organized.

Consider questions such as:

  • Are the main categories easy to understand?
  • Can customers search quickly?
  • Are related articles grouped logically?
  • Does the layout work well across different screen sizes?
  • Are visual elements helping users navigate the content?
  • Does the current theme require custom code to maintain?

These questions can help determine whether a theme change would solve an actual problem or simply change the appearance of the portal.

What Should You Check Before Choosing?

A theme preview can show the overall appearance, but it does not tell you everything about how the theme will work with your existing support setup.

Review Your Content Structure
Look at your categories, sections, articles, FAQs, and navigation. The theme should support the way your information is organized.

Check Your Zendesk Plan
Confirm that your current subscription supports the theme functionality and customization options you need.

Consider Development Requirements
If developers will maintain the theme, source-code access may be an important consideration. If administrators will primarily use the available settings, extensive code access may not be necessary.

Review Existing Customizations
If your current Sagma installation contains custom CSS, templates, or other modifications, identify them before considering a transition.

Consider Long-Term Maintenance
Think about who will manage the theme after implementation. A theme should be manageable not only during setup but also when content, branding, and support requirements change.

Which Version Makes More Sense?

The original Sagma may be a good choice for teams that prefer its current structure, need a simple support theme, or are looking for the lower listed purchase price.

Gen 2.0 is a good option for teams that need different visual starting points, more source code access, different licensing editions, or the included creative workspace.

Not every organization needs to choose one of these options. The decision depends on the team's content structure, technical resources, branding requirements, existing customizations, and budget.

For a Zendesk Help Center, the more important question is whether the theme supports the way your team creates, organizes, and maintains support content.

Conclusion

The two versions are different in more ways than just how they look. Gen 2.0 has four visual options, Standard and Developer editions, different levels of source code access, an included creative workspace, a 14-day trial, and free upgrades to future versions.

The original Sagma has a simpler product structure and may work well for teams that don't need these additions. Gen 2.0 offers more options for teams that need customization or development.

When comparing Sagma vs Sagma Gen 2.0, start with your current setup instead of thinking that the newer version is automatically better. Before deciding whether to make a change, review your Zendesk plan, content structure, customizations, technical resources, and feature requirements.

FAQs

1. What is the main difference in Sagma vs Sagma Gen 2.0?
The main differences include Gen 2.0's four visual variants, two editions, different levels of source-code access, included Creative Suite, 14-day trial, and free future upgrades.

2. Is Sagma Gen 2.0 compatible with Zendesk?
Yes. Sagma Gen 2.0 requires a Professional or higher plan, or an eligible legacy subscription that supports custom theme imports and code editing.

3. What editions are available for Sagma Gen 2.0?
Gen 2.0 is available in a Standard Edition at US$299 and a Developer Edition at US$349. The Developer Edition provides full source-code access.

4. Does Sagma Gen 2.0 include Creative Suite?
Yes. Gen 2.0 includes Diziana Creative Suite, which provides access to visual assets such as images, illustrations, icons, and SVGs for use in Help Center content.

5. Should I replace my existing Sagma theme with Gen 2.0?
Not automatically. If the existing theme meets your requirements, there may be no immediate reason to switch. Gen 2.0 is more relevant when you specifically need its additional visual options, source-code access, editions, or included creative tools.

Top comments (0)