Skip to content

Problem-oriented projects #190

@jbothma

Description

@jbothma

I'd like to encourage participants to work in a problem-oriented way. Approaching a project more like

  1. identifying what problem they want to solve
  2. identifying a number of options for addressing the problem
  3. implementing on one or more of those options

as opposed to just diving into tech and solutions.

I think one way to do that is to make the process of defining the project guide them that way.

What I have in mind is to add two more project description sections to the current single description section. These two would be rendered with the h1 headings

  • Problem statement
  • Potential solutions

The current description box would be headed

  • Additional information

Screenshot_2021-05-29_22-55-47

What are your thoughts on the idea and the proposed implementation? Is this something you'd be interested in merging?

Perhaps the functionality should be optional - not sure if it should be on by default for new dashboards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions