The Plenti CMS is designed to work out-of-the box with zero configuration. It's a "Discoverable CMS" that reads your content source and provides a default editing experience that you can use locally or deploy to a remote site. If you want a different editing experience, you can always define _defaults.json, _schema.json, and _components to customize your editing experience if you so choose.

Autogenerated Field Widgets

  • Dates (docs): 6/7/2008, 6/7/08, 6-7-2008, 6-7-08, 6.7.2008, 6.7.08, Saturday, June 7, 2008, Saturday, Jun 7, 2008, Sat, June 7, 2008, Sat, Jun 7, 2008
  • Time (docs): 14:30, 02:30pm, 02:30 pm, 02:30PM, 02:30 PM, 2:30pm, 2:30 pm, 2:30PM, 2:30 PM, 14:30:45, 02:30:45pm,  02:30:45 pm, 02:30:45PM, 02:30:45 PM, 2:30:45pm, 2:30:45 pm, 2:30:45PM, 2:30:45 PM
  • Number (docs), 1, 01, -1, 1.5
  • Boolean (docs): true, false
  • Text (docs): "Any unrecognized text"
  • Component (custom): [ ]
  • Media (custom): /media/*.[pdf, msword, jpg, jpeg, png, webp, gif, svg, avif, apng]

Change Display

Sometimes you might want to use one of the default widgets for your editing experience, but you want the value to display differently on the frontend of your site. For example, you want a datepicker widget for your editors so you make your default value "1/15/24" but you want it to display as "Jan 15" to visitors. For this, you could use a format the CMS understands in your JSON and then use a Date object in your JavaScript to change the display.