Remove hard-coded, redundant Title field from config items.

[ChristopherChudzicki]

If a ConfigItem does not have a Title field, Studio automatically adds one to the top.

But, because we want Draft first (not Title) every config item already has an explicit title field.¹.

Let's remove the hard-coded default field:

ocw-studio/static/js/lib/site_content.ts

Line 388 in f651376

export function addDefaultFields(

Footnotes

1. At least after https://github.com/mitodl/ocw-hugo-projects/pull/259 is merged ↩

[Ferdi]

I remembers this was by design but I dont remember the details

#279

[ChristopherChudzicki]

@Ferdi Thanks, #279 makes sense to me:

• we base the filename on Title + things need a filename => content collections must have a Title.

I'd favor having the Studio config validator throw an error if there's no Title field rather than having the frontend modify the config. Maybe just something to keep in mind if/when we do #973—In light of #273, I don't think it's worth tackling now.