The Get Into Teaching service has been live for 1 year now. Our team often updates the website several times a day to ensure users get the most accurate and up to date information.
It was taking us a relatively long time to update the website and check our changes. We needed a simpler way to upload content onto the website.
In this post, I explain how my team used to upload content, and how a change in technology is helping us do this more easily.
Uploading content isn't as simple as changing some text in a box and it then appears on the website. A lot happens behind the scenes to make sure the code that contains the new content works. My team uses a platform called GitHub to do this.
Typically, these are the steps we take:
- In GitHub, we’ll type in our changes using Markdown - a type of coding language that formats our content
- Some technical stuff happens behind the scenes to create this new content
- We’ll then receive an email some time later showing us the changes
- If we’ve made a mistake, we try and change the content ourselves or ask a developer to help us fix it
- We then have to wait for the new changes to appear so we can review them again
GitHub is handy because when we want to make a change, we can create a new branch. A branch is our own snapshot of the website that only contains our changes.
We then create a pull request with our branch, which is how we propose our changes to the team. Pull requests give the team a chance to leave feedback, add suggestions and discuss the changes.
When everyone is happy, we can merge our branch with the live website.
Our old ways of working
Using GitHub on a computer where we can’t run the website means we can’t see what our changes look like straight away. We have to create a pull request and wait for the review app to build. Creating a pull request basically means requesting our changes, and the review app lets us see how these will look on the site.
This can be challenging if we’re making lots of changes throughout the day. Sometimes the review app doesn't build because we've made a mistake in the Markdown code, which means we can’t review our changes.
This means that it’s harder to check that the content we’re uploading onto the website looks right - and in the best format for the user. So we end up wasting time checking and re-doing our work.
This is where Codespaces comes in.
Codespaces - a content designer’s best friend
Codespaces is a development environment that uses GitHub. Codespaces allows us to see the changes we want to make on the website before we actually make them. It gives us an immediate preview.
This helps us see what the content will look like. That way, if we see it doesn't work, we can tweak it. And rather than waiting for the review app to build, we can see it more or less immediately.
Codespaces is very useful for non-technical team members like me. I don’t speak fluent Markdown like my developer friends, so it’s harder to spot mistakes. Codespaces makes it easier for me to do this.
Advantages of using Codespaces
Here are some more benefits of using Codespaces.
It’s easy for developers to set up. They can make sure all the right software is installed and everything’s configured. We can be up and running with a new project in minutes.
It also ensures everyone on the team has the same environment, making it easier to diagnose and solve problems.
Being a better content designer
Using technology like Codespaces means we can make better content decisions, quicker. Instead of fighting the GitHub review app, we can spend our time thinking about how we can best support tomorrow’s teachers on their journey into the classroom.