Incremental improvements to the about page, first admin buttons, accessibility improvements, introducing Portainer, Google Search Console verification and getting started on the Jest Snapshot testing for our front-end are among my list of highlights for the past week.
Last week we’ve made a steady progress towards our UI 2.0 milestone. It has been very nice to see About page getting more and more polished by the efforts of Chris. It was a tough one, but we finally have a properly styled and responsive About page!
In this article, I will cover four steps that will help improve your website SEO.
When it comes to building any modern website, you will most definitely have to work on the Search Engine Optimization for it, because you want other people to be able to find your website and utilize it. Let’s take a closer look at what it is and how to make it work.
Search Engine Optimization is a term used to describe the process of making your website better for search engines. …
In this blog post, I will provide you with some updates on what happened in Telescope in the last couple of weeks.
Throughout the last 14 days or so we have continued the work on the microservices and UI 2.0, which was quite exciting to see. Besides, I have finally managed to find a good-looking and properly working changelog generator for our releases. Tested in our latest 1.8 release, it categorizes merged pull requests based on the labels specified in the configuration file. The produced result looks quite appealing:
With the imminence of midterms madness, this week was fairly quiet for most of the students on Telescope. Nevertheless, there has been important work going on in expanding our footsteps in the world of micro-services. We rolled out an impetuous switch the UI 2.0 and cleaned up after porting from Gatsby.
As for myself, I have primarily focused on investigating the changelog generation issue. Since our old changelog generator has not produced any results during the
1.7.0 release, and was well-hated by David for making us follow specific commit message formatting, its fate was clear. Even though I couldn’t fight…
On this week’s Telescope podcast is how to tame the monster and how to make one go away.
“git outta here” — Chris Pinkney
Last week has been pretty busy. Telescope team has shipped
1.7.0, in which we finished porting to Next.js, scrapped Gastby front-end for good, fully updated all of our dependencies, made a good progress with micro services, and finally configured Dependabot appropriately. Good job, team!
After the initial fiasco with launching Dependabot, we have been very serious in dealing with this beast. …
In this article I will talk about setting up automatic dependencies updates, its pros and cons…and how to break your CI with it.
Dependabot is an automation bot that would check dependencies in your project for you and create PRs to update outdated ones for you. What is even more exciting is that ever since it’s been acquired by GitHub, it is completely free to use for both your personal accounts and open-source projects. Being an integral part of the GitHub Security features, it will take extra care of patching security vulnerabilities in your repository as well.
In this blog post, I will provide you with some updates on what happened in Telescope last week.
One of the major things that I achieved last week was incorporating the new release process into our repository and successfully testing it to create release
1.6.0 of our project. Some additions that were made since the last article was posted include the
npm-version command line tool. Now we can do the release not with two commands, but just with one:
npm version minor -m "Release 1.6.0"
I also have to mention that during our test release we have encountered one problem…
In the last couple of weeks, we’ve focused on cleaning up the PRs section at Telescope and continued porting to Next.js, along with some improvements to developer experience, theme, and CI/CD.
“There should be two tasks for a human being to perform to deploy software into a development, test, or production environment: to pick the version and environment and to press the “deploy” button.”
― David Farley, Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
In this article, we will review the typical software release process and how it can be automated with GitHub Actions.
GitHub Actions is a great tool for continuous integration (CI) and continuous deployment (CD). It allows us to set up automated workflows directly in our GitHub repository. Moreover, Marketplace would give you access…
This week Telescope team has been able to release yet another iteration of the Telescope project. Some of the milestones that we achieved are a considerable progress in porting our front-end from Gatsby.js to Next.js, updating the global theme, global state management logic, cleaning up Eslint warnings. We made a deep dive into the ‘Pull Requests’ section under our repository, resolving over 20 items. But most importantly, we worked and collaborated together as a team.
It has been very insightful to learn about current team composition and project management approach. We are truly scrum. Our goals are not always known…
Enthusiastic Junior Software Developer striving for discoveries & curious about technology