Difference between revisions of "Project page"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | Project page is a community that has a common interest. It includes | + | Project page is a '''community''' that has a common interest. It includes |
* Branches of topics | * Branches of topics | ||
* Individual users as community members. | * Individual users as community members. | ||
Line 25: | Line 25: | ||
==Discussion== | ==Discussion== | ||
Discussion about topics and content related to topics in the interest of the community should be aggregated in the page or accessed from the page. | Discussion about topics and content related to topics in the interest of the community should be aggregated in the page or accessed from the page. | ||
+ | |||
+ | ==Tasks== | ||
+ | When tasks are made, they can be assigned to / associated with branches of topics or content communities directly. This way they will be visible in the community page as well as the feed of members of those communities. | ||
{{design-nav}} | {{design-nav}} |
Revision as of 11:54, 31 December 2018
Project page is a community that has a common interest. It includes
- Branches of topics
- Individual users as community members.
- Expert users, usually organisations. Perhaps individuals could also become expert users.
Contents
Topics
- Branches, hierarchies
Topic display
- Included topics can be seen in the project page. What is the data we could show about each topic on the project page?
Members
Members can maintain discussion around the topics of the project, create tasks such as polls or identification drives.
Individual members
- Individuals may become admin members
Organisation members
- Organisations are expected to act as expert members, giving advice and answering questions, sharing content, maintaining bibliographies.
- Organisations may also perform admin tasks, patrol content in their expertise area.
Display on other pages
- The project/community is displayed on topic page header which it deals with.
Discussion
Discussion about topics and content related to topics in the interest of the community should be aggregated in the page or accessed from the page.
Tasks
When tasks are made, they can be assigned to / associated with branches of topics or content communities directly. This way they will be visible in the community page as well as the feed of members of those communities.
About | Technology | Design | Content modules | Tool pages | Projects |
Status
Wikidocumentaries Slack |
Setting up dev environment |
Components |
Active modules Module ideas |
Visual editor | Central Park Archives |