Blog Sections Open

Do longtitle and description Need to Be Filled for Every Resource?

This is one of the most useful recurring editorial questions in Evolution CMS: should every resource always have longtitle and description filled in? The short answer is no. Those fields are valuable when they add someth

This is one of the most useful recurring editorial questions in Evolution CMS: should every resource always have longtitle and description filled in?

The short answer is no. Those fields are valuable when they add something specific, but forcing them mechanically across every page often creates thin, repetitive metadata that helps neither users nor search engines.

Good Use Cases

  • longtitle when the frontend needs a richer heading than pagetitle
  • description when it supports meaningful meta descriptions or archive intros

When Not to Force It

  • if the value would just repeat the main title
  • if editors will fill it with boilerplate
  • if templates do not use the field meaningfully

These fields are useful because they can improve clarity. They lose value when they become mandatory noise.

Newer post

Making eForm Work with AjaxSubmit Reliably

What to check when eForm and AjaxSubmit do not cooperate cleanly and the form works only in normal postback mode.

Older post

Keeping Ditto Summary Output Clean When introtext Contains HTML

How to think about summary generation when Ditto output is built from fields that already contain HTML markup.