Ideas for a 0.7 refresh #3

New issue

Open

opened 2023-06-29 14:31:17 +00:00 by loleg · 0 comments

loleg commented

2023-06-29 14:31:17 +00:00

Owner

Not sure yet where else to put this, but after some brainstorming this week, here are some very compelling structural changes I would like to see in the next major Dribdat release:

The "Pitch" text area becomes "Challenge", and is no longer really used by the project teams, unless they need to change something in the project definition.
The README goes to the top and becomes the main content of the Project.
Add possibility to sync multiple README sources, so you could mix a description and a repository, or even several repositories.
Guide the user to enter URLs from supported sources (Etherpad, Gitea, ..), with a YAML configuration an admin could extend.
Make it possible here to also auto-create an Etherpad or Excalidraw based on the project title.
Improve the readability of the Log, which becomes even more important for documentation.
Add an optional combined Log view to the Report.
Stages add the inputs, such as adding your Source or API key or Screenshot, directly to the Post form - no need to navigate to Details.
Collaborate on a refresh of the Stages with our community, write a bit more documentation on how to update this.
In the Resource area things stay the same - except that you can just select your Stage, and we make it clear which one is 'template'.
The Stages should also include a link, for example, to an evaluation form for teams to complete at the end. They see this (logged in) on the project page.
Add multiple Demo links.
Gallery view scrolls therough demo links, and all image attachments.

Not sure yet where else to put this, but after some brainstorming this week, here are some very compelling structural changes I would like to see in the next major Dribdat release: 1. The "Pitch" text area becomes "Challenge", and is no longer really used by the project teams, unless they need to change something in the project definition. 1. The README goes to the top and becomes the main content of the Project. 1. Add possibility to sync multiple README sources, so you could mix a description and a repository, or even several repositories. 1. Guide the user to enter URLs from supported sources (Etherpad, Gitea, ..), with a YAML configuration an admin could extend. 1. Make it possible here to also auto-create an Etherpad or Excalidraw based on the project title. 1. Improve the readability of the Log, which becomes even more important for documentation. 1. Add an optional combined Log view to the Report. 1. Stages add the inputs, such as adding your Source or API key or Screenshot, directly to the Post form - no need to navigate to Details. 1. Collaborate on a refresh of the Stages with our community, write a bit more documentation on how to update this. 1. In the Resource area things stay the same - except that you can just select your Stage, and we make it clear which one is 'template'. 1. The Stages should also include a link, for example, to an evaluation form for teams to complete at the end. They see this (logged in) on the project page. 1. Add multiple Demo links. 1. Gallery view scrolls therough demo links, and all image attachments.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: dribdat/dribdat#3

No description provided.