wisvch / committee-website-vision Goto Github PK

When this system comes into place, many committees will be recommended to use the newly created elements. For these elements documentation will be created, there will probably be a lot of extra questions about how to implement them correctly, despite documentation being available.
Will explaining and helping with these elements also be a task of the core group or will/should this be done by another group/other users. Maybe even a forum, or just a slack group.

First of all, I really like this idea. But upon reading it, something popped up in my head.
How do we prevent the core development team from simply becoming the 'committee website creation team'. The technology we use might be very new to some committee members, especially the first year committees. Are you not afraid that there will be so many questions regarding the reusable components that the committees simply stick to their own known frameworks, or that they ask so many questions that the core development team basically guided them through it and did about 80% of the work?

How should we prevent this?
A possible solution could be loads of documentation I guess.

I guess this question is related too #3
However, I think this issue is more related to making the distinction between the type of support the core team will give, and how far the core team will go in helping the committee fix the issues

Will there be the option for users that are not in the core group to create extended elements of the elements that are created by the core group?

As a member of the coming board we really love your idea and vision.
I worked on a different version of your proposal and we would love your opinion. It is not finished yet and if you don't have time to look into it, we would understand.
You can find it here
It is a very difficult problem due to certain aspects of website development. Everyone does it different and we also don't have the golden key unfortunate.

Thanks in advance!

Team expansion is mentioned at the bottom of the document, though there is not stated how the team of 5 is going tot be kept in place. I think that maintaining the knowledge is the most important part of this project, because if the knowledge would get lost somehow, all Committee websites are in trouble.
I suggest adding a more specific description on how to maintain the knowledge, eg:

• When to ask new people.
• What to do if someone wants to quit as a developer.
• Describe how knowledge is passed over, will there be tutorials or something like that.