-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The carpentries.org content redesign #27
Comments
On May 3 2021, we kicked-off work with a designer with the following objectives: The new Carpentries website should:
Note that the revision of the lesson program websites is out-of-scope for this project. We expect that design work will take 10 - 12 weeks, and hope to work with a frontend developer to actualise the approved designs for 9 weeks after the design work is complete. We hope to launch a new website in late 2021 or early 2022. |
Is this currently out of the hands of the CDT until the web designer has finished her work? |
The web designer will deliver the final product of the work next week. After that, we will work with a web developer to create a template that we can use for our main website, and that will be a starting point to harmonize our visual identity across all our sites. |
The Carpentries is keen to improve accessibility across our interactions and resources. We approached this in three ways. Firstly, we engaged the community in a conversation about equitable access to and availability of platforms and tools used for collaboration in online communities. We collated feedback and populated accessibility related issues on our Help Wanted page. A few examples of issues and PRs submitted include:
Additionally, the Core Team participated in an ‘Acc-athon’ to add alt text across Carpentries curricula. Secondly, we contracted UX/UI designer Oliva DuVal to do a brand refresh comprising the redesign of our organizational and lesson program websites, and our community handbook with the following objectives in mind:
Olivia produced a website schema meeting each of these objectives. In doing so, we realized much of the content on our website should be organized into separate handbooks according to various community roles, and that work is being managed by the Community Development Team. Lastly, we contracted bytes.co, a web design, digital marketing and development agency specializing in web accessibility. Bytes.co worked in collaboration with their sister company, Accessible Web, to convert the carpentries.org website template schema developed by Olivia DuVal (UX/UI contractor) into static html/css/js web pages. These web pages are currently being converted into full static sites and conform to WCAG 2.1 AA web accessibility standards. |
Content for the website and handbooks has been developed by each of the teams. The Core Team members assigned to this work are now moving the content into the appropriate GitHub templates. |
The content developed by teams has been transferred to the appropriate GitHub templates. There is a final round of functionality updates needed before moving into community review and launch. Tagging @Talishask in case she would like to add more |
The Website working group has decided not to continue the project with bytes.co and so this will need further discussion and decision making. A full request for quote (RFQ) will be provided by the team to set out our requirements before going to tender. In the interim we will focus on improving the existing website content. |
The website working group met this week and will begin meeting every two weeks. @OscarSiba, our new Communications Manager, has joined the working group. First task is to finalise the drafted RFQ and share broadly to identify a website developer to complete this project |
The website working group is interviewing potential contractors next week |
A contractor has been identified and will start work in the new year. @OscarSiba and @Talishask have pulled 99% of the website page drafts into a Google document. I will be sharing links to all relevant documentation and provide status update for the working group to continue its work in 2024 |
Since the last update was at the end of 2023, I am including a summary of all 2024 activity here. Note also that while the title of this issue applies just to carpentries.org, this update refers to that site as well as the three lesson program sites and the handbook. We hired The New Dynamic to work with us at the end of 2023. After hiring The New Dynamic to build a Hugo theme for us, we spent the first half of 2024 working with them on this process. The intent was to have one theme used for all four websites (The Carpentries and its three lesson programs) so all four websites would have the same look and feel and user experience. This process began by sharing our designs with them, testing the theme they provided, sharing feedback with them, and continuing this process until all deliverables were met. As we developed the theme, we would populate it with real content as provided by Core Team members. As of this status update (2024-11-14), we have been able to implement the theme and content and will be completing deployment by 2024-11-18. At the same time, we have been working on revamping our Handbook to update content, remove outdated content, and update the general theme and organization to make resources easier to access. The development of the new handbook followed a similar pattern of testing and user feedback. The new handbook will be deployed 2024-12-09. Both of these launches are intended to be "soft launches." We have many outstanding issues in the relevant GH repos tagged "later" that we will come back to in 2025. Edit to add note - @OscarSiba please feel free to add any other comments you would like to include. |
Carpentries Team dedicates time to read, research and learn about web accessibility as a necessary prerequisite to signing up for a design thinking workshop as a team in Phase 2 and the start of website redesign work in phase 3.
The three phases are:
this section was updated to reflect a necessary shift in the focus of each of the three phases of this project
The text was updated successfully, but these errors were encountered: