Add separate wiki for each project (feature)

[nelinnemann]

Having a separate wiki for each project will make it possible to add meeting notes, documentation, etc. to each project.

This will help immensely so to keep everything in one place.

[ari]

Actually I've long thought that would be a good idea. The wiki should extend gracefully. At the beginning it is just a large text field to describe the project (or milestone). But then you can extend it into multiple pages and give it more depth.

There is really very little point at a generic wiki. We already have superior CMS tools for that sort of thing. But focussed around the projects... yes.

[nelinnemann]

Sounds like you already have it planned :-)

[ari]

It has been in my head. But nothing more than that... if you want to contribute code I'd be more than willing to merge it (with unit tests). But first we need UI design concepts. Where does this text display? Do we need a project home page which is more like a summary of the project than a bunch of editing screens.

[nelinnemann]

Well I would really like to contribute but my experience with ruby are equal to zero :-)

But I was thinking somthing simple like the following

[ari]

Ruby I can handle. But 80% of the challenge is creating the UI. For example, look at this old feature concept I did: https://github.com/ari/jobsworth/wiki/Dependencies

Your idea will not work. The task list is not a list per project or milestone. So which wiki would you be going to? And why would wiki be buried on the task list page?

[nelinnemann]

Then I do not get it because when you press the "Projects" at the top it leads you to the "Project list" page.

I can then press the project that I wish to see the overview of so the wiki is part of that project.

Did you notice my wiki text next to the Gantt button?
The idea was to have a wiki button similar to that which takes you to the wiki of that specific project.

[nasa42]

Feature for release 5.0?