Tehnical game plan for article page refresh and possible new article field(s) in database
This is a subtask for #218. Requesting help with creating a technical game plan for redesigning the article page, and creating any new db fields that might be required.
The ideal for updating article layout is to make it backwards compatible, whereby the current title/author/date/summary/attachment/body
would remain for all existing articles. (Summary is used as description for metatags.)
Most likely new articles will take the format of title/(subtitle)/image/caption/author/date/body
, where subtitle might not be displayed after preview/publish and would only be used for metatag description, although that might be too complicated/confusing for users even with an explanation on publish page.
As to the backwards compatibility, I was forseeing that being handled via an if statement in a php template, something like: if summary field contains content, then display original layout; else/if subtitle field contains content, display new layout.
That was my thinking with how a new subtitle field could be utilized programmatically, beyond its value as content element in a new layout. Also, the subtitle would be text-only and not allow HTML as the summary field does now.
The comment in #218 said there were two title fields already, but I'm not sure if the second one is in use somehow and/or whether it could be repurposed as described above with backwards compatibility in mind.
I do think we may at least need a field for upload #1 (closed) caption. If subtitle can be handled without adding a new field, meeting specs above, that's fine.