Website Redesign Staff

Website Redesign Staff work together on a new website for KQM's 4th anniversary.

Welcome to the KQM Website Redesign team! This onboarding document outlines the responsibilities of the Website Designer and Developer roles, supplies you with a list of resources, and provides a checklist to make sure you are prepared.

Onboarding Checklist

Follow this checklist and complete each task carefully:

Introduce yourself in the Discord channels called #website-redesign and #lounge (if you want).
Double check that your email and other information is correct in the Staff Contact Sheet.
Check your email for an invite to ClickUp.
Complete the ClickUp Onboarding Task with your name on it.
Complete the Website Redesign Staff Onboarding Task on ClickUp (which includes the checklist items below).
Read the KQM Staff Guidelines.
Read the Strike System and Hiatus System.
Learn about the responsibilities of your role.
Read through the guiding principles of the Website Redesign team.
Familiarize yourself with the documents that are pinned in #website-redesign.
Bookmark resources or keep them accessible.
Ask any questions you have in #website-redesign or #website-designers/#website-developers.

Responsibilities

Website Redesign staff are responsible for:

Updating the KQM Website Redesign ClickUp.
Actively communicating in staff channels and with their leads.
Completing tasks and projects by a specific goal date.

You are free to contribute as much as you like. While we do expect some consistency in regards to project contribution, we respect your life outside of KQM. However, if you take on a time-sensitive project, please make sure you allot enough time to finish it by the goal date. If you need help, please ask. Active communication helps everything go smoothly.

Initial Trial Period for Website Redesign Staff

All new staff undergo a trial period of at least 2 weeks where their contributions and team participation are assessed. After completing their onboarding checklist and helping with a few projects, successful Website Redesign Staff are officially a part of the team.

You can take as long as you want to finish your projects (within reason and by goal dates) and choose any kind you like. We expect that if you're willing to be a team player and pitch in, then you will complete the trial period successfully! If you have any questions or concerns about the process, please contact @irokei or your team leads.

Website Redesign Production Process

For all tasks and projects within the scope of the website redesign, follow these 7 major steps outlined below.

Identify a project that you can work on — Team leads will direct staff on projects and priorities, but if you think there is anything that needs to be done, you are welcome to bring it up and work on it.
Make a forum post — All projects need to be worked on in a forum post.
1. Check if there is a relevant forum post in #website-redesign-forum for that project.
2. Make a forum post if you need to.
3. Include the following information in the first message of the post:
  1. Describe and explain the project.
  2. Provide a goal date and general timeline.
  3. Ask for collaboration with others if you need it (projects should be open to anyone who wants to work on them, but if it is better to work individually, explain why).
  4. Say what kind of feedback you're looking for, and when you will be accepting feedback.
  5. Share any links or documents that would be relevant.
  6. Create a ClickUp task if there isn't one already.
Do the project – Work on the project with your established timeline and reach out for help when you need it. If you find that you need to make any major changes, consult with your leads and other staff for their input.
Receive feedback — Provide at least a 48-hour window for feedback, and ping the @Website Redesign role. Make sure to specify what kind of feedback you are looking for.
Revise — Address all feedback and make any changes.
Finalize — Share your revised project in the forum post. Check in with your leads and any collaborators.
Implement — Commit or ship your project, yay! If you need to make any changes after implementation, restart from step 4.

Guiding Principles

Expectations for All Website Redesign Staff:

Communication: We proactively communicate with each other and are open to feedback. Avenues for communication need to be clear, accessible, and well defined. The website redesign is a collaborative effort between designers, developers, and other staff.
Accountability: We hold each other accountable to high standards and strive to follow through on our commitments. If we anticipate being unavailable for a length of time while working on an active project, we let each other know.
Respect: We respect each other and the hard work that we put into the project. Life outside of KQM takes priority and we support this. We try to be mindful of other people’s perspectives. We may not always agree, but we can try to understand where others are coming from.
Ethics: We promote transparency in the redesign process. Projects should be inclusive, and contributors are expected to be open to feedback and reasonable suggestions. We credit people for their contributions.
Sustainability: We promote healthy, manageable, and sustainable workflows. We are here to help each other to the best of our ability. If something feels overwhelming, we let someone know. We want to avoid burnout as much as we can.

Designer Best Practices

Leads - Making Forum Posts for Sub-Projects

Check if there is a relevant forum post already for that project.
Make a forum post if you need to.
1. Name it as exactly and specifically as possible.
2. The name must match the corresponding ClickUp task.
Select at least 1 tag from each line below:
1. Designer, Front-End, Back-End, Other Staff, All Staff
2. Project, Discussion
3. Priority, (no priority tag)
4. WIP, (no wip tag)
Include the following information in the first message of the post (can copy from ClickUp):
1. Describe and explain the project.
2. Provide a goal date, project commission, and general timeline.
3. Say how many people should work on the project. Can be specific number, small range, or no limit.
4. Share any links or documents that would be relevant.
5. You must link the ClickUp task.
Pin the first message and ping anyone who needs to be included.

Staff - Working on Sub-Projects

Send a message in the forum post stating your intention to work on the project.
Assign yourself to the ClickUp task if you aren't already.
Add the tag WIP.
When you are ready for feedback, change WIP to Feedback Plz! Please note a goal date to submit feedback and describe what kind of feedback you need.
When you have finished the project and need to finalize, change Feedback Plz! to Close Me so a lead can close the sub-project.
If you need help, add the Help Me tag.
Make sure you keep track of what you contributed to the project and keep an estimate of how long you worked on it.

Developer Best Practices

Leads - Making Forum Posts for Sub-Projects

Check if there is a relevant forum post already for that project.
Make a forum post if you need to.
1. Name it as exactly and specifically as possible.
2. The name must match the corresponding ClickUp task.
Select at least 1 tag from each line below:
1. Designer, Front-End, Back-End, Other Staff, All Staff
2. Project, Discussion
3. Priority, (no priority tag)
4. WIP, (no wip tag)
Include the following information in the first message of the post (can copy from ClickUp):
1. Describe and explain the project.
2. Provide a goal date, expected work hours, and general timeline.
3. Say how many people should work on the project. Can be specific number, small range, or no limit.
4. Share any links or documents that would be relevant.
5. You must link the ClickUp task.
Pin the first message and ping anyone who needs to be included.

Staff - Working on Sub-Projects

Send a message in the forum post stating your intention to work on the project.
Assign yourself to the ClickUp task if you aren't already.
Add the tag WIP.
When you are ready for feedback, change WIP to Feedback Plz! Please note a goal date to submit feedback and describe what kind of feedback you need.
When you have finished the project and need to finalize, change Feedback Plz! to Close Me so a lead can close the sub-project.
If you need help, add the Help Me tag.
Make sure you keep track of what you contributed to the project and keep an estimate of how long you worked on it.