Blog Sections Open

Should `longtitle` and `description` Be Filled for Every Resource?

Filling every available field is not the same as improving a page. `longtitle` and `description` help most when they are used deliberately.

The old question was short but important: should every resource have longtitle and description filled in?

The Sensible Answer

Not automatically. Those fields are valuable when they have a clear purpose.

  • longtitle is useful when the page needs a richer on-page headline than the shorter navigation or system title
  • description is useful when it supports meta output, summaries, cards, or listings

When They Become Noise

If editors are forced to fill them just because the fields exist, the result is often duplicated text, weak summaries, or placeholders nobody maintains.

Best Practice

Make these fields part of the workflow only if the site actually uses them. Once they are tied to SEO snippets, cards, or previews, teams are much more likely to maintain them well.

Newer post

Protecting a Subscriber Database in MODX Revo

A practical security note on subscriber data, mailing lists, and why backups and access rules matter as much as the newsletter tool itself.

Older post

Fixing `easy2` Installation Errors in Older Dmi3yy Fork Builds

A practical note on installation failures caused by SQL syntax differences such as ENGINE declarations in older environments.