You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a resolution for #163, renaming the "Objective" and "Description" columns to "Abstract" and "Outline", we introduced a "labels" JSON dictionary in #164.
This is a hack that needs to be removed. Similar to the change in thinking introduced by labels in #313, we have two distinct concerns here:
The platform needs a summary to show in restricted spaces such as the proposal list, and a fuller body when the proposal is viewed standalone.
The project editor will want customisable fields (first discussed in Customisable forms #109), but this can be satisfied by offering an template for the body, without using custom fields. The word "body" need not appear anywhere. It could simply be the dominant textarea.
To do:
Remove the labels JsonDict (it may be renamed to part_labels by the time this ticket is picked up) and all code that depends on it
Rename the objective database column to abstract (a migration)
Templates could either be fields stored in the Project model that are copied to a proposal, or they could be actual proposals put into a "template" state. When a new proposal is created, the user will be given the option of copying an existing template.
The text was updated successfully, but these errors were encountered:
As a resolution for #163, renaming the "Objective" and "Description" columns to "Abstract" and "Outline", we introduced a "labels" JSON dictionary in #164.
This is a hack that needs to be removed. Similar to the change in thinking introduced by labels in #313, we have two distinct concerns here:
The platform needs a summary to show in restricted spaces such as the proposal list, and a fuller body when the proposal is viewed standalone.
The project editor will want customisable fields (first discussed in Customisable forms #109), but this can be satisfied by offering an template for the body, without using custom fields. The word "body" need not appear anywhere. It could simply be the dominant textarea.
To do:
labels
JsonDict (it may be renamed topart_labels
by the time this ticket is picked up) and all code that depends on itobjective
database column toabstract
(a migration)Templates could either be fields stored in the Project model that are copied to a proposal, or they could be actual proposals put into a "template" state. When a new proposal is created, the user will be given the option of copying an existing template.
The text was updated successfully, but these errors were encountered: