JAMES ZECHMAN

Flowchart for Citizen Science Planning

As a beginning step for creating the Citizen Science Website or App we first set out to create a flowchart which would map the process of using and navigating through the website to gain a better understanding of how the website should work
Flowchart for Citizen Science Planning

Introduction

As a beginning step for creating the Citizen Science Website or App we first set out to create a flowchart which would map the process of using and navigating through the website to gain a better understanding of how the website should work. This process was creating with required registration or logging in in order to keep chunks of code safe from bots or those seeking to grief and disturb the process of editing and cleaning code.

The Flow

Simplicity in mind, the user will start at a home screen which details out what the Citizen Science website is, what the point is, and other bits of information that are relevant and add a professional appeal. From there, they can click on the Login or Register button on the top right and do either.

If the user registers they are brought to an initial tutorial page which teaches them how to correctly use the Citizen Science Website which then, upon completion brings them to the main page, or language selection screen. If the user logs in, it will simply bring them to the main coding page with their last selection of code enabled.

Upon selecting a language, the user is faced with a page with the code references, the textbook for them to type their variation in, and on the right side an upvote/downvote style voting panel for other answers.

On the top right of the screen are three icons for notifications, messages, and account settings.

When the user enters into the account settings they are given four choices, Account Settings, Unlockables, and Leaderboards.

When they click on Notifications it will give them the latest feed relevant to their account.

When they click on messages it will show important site messages as well as messages from other users to their personal account.

Conclusion

As stated before, this site and flowchart was created with simplicity in mind. It is meant to not bog down the users with features but rather create a neat, simplistic area for them to fix code and check their own progress through gamification.