Problem/Motivation

We want to know how the front end forms should work. We probably want to have slightly different forms and options for different contexts.

Proposed resolution

[TBC]
Create multiple form displays for the same entity that have different fields to be filled in and decide on the different workflows we want to support.

Remaining tasks

  • Decide on workflows
  • Decide on fields/options
  • Create follow up issues

Comments

yanniboi created an issue. See original summary.

yanniboi’s picture

Form displays

I think we want to have different form displays for different types of submissions. The first thing that comes to mind is different forms for:

  • Modules
  • Themes
  • Distributions

However another thing to consider is, do we want to have an entirely different one step form for these three contexts, or do we want to have a single multistep approach or 'wizard form' where there are different options depending on previous choices?

Form groups

Another question would be how we layout the form. I think we want to group fields together in containers or tabs or something. In which case we want do decide whether to group things programmatically in the code or whether we use a UI tool like 'field group module'.

Form fields

So far we have fields in three different groups.

Drupal

  • Source
  • Version
  • Project Identifier
  • Install project?
  • Patches

Webserver

  • Webserver
  • Interpreter
  • Database
  • Secondary Databases

Instance

  • Runtime
  • Instance Image
  • Use snapshot cache

[Hidden] - used for background processing

  • ...
rachel_norfolk’s picture

Status: Active » Postponed (maintainer needs more info)

Is this still an active issue? Trying to ensure the queue has relevant issues in it and this one has not seen activity since before major changes to the platform.

Please set to active if still relevant. Please set to Closed (outdated) if not.