Skip to main content

2 posts tagged with "cleanup"

View All Tags

· 2 min read

Since the last blog post, we've been continuously working on improving the Edlib "plant", and in reference to the previous blog post, we've concluded that we need to replant it. This means we are now rewriting and consolidating most of the code to make further development more straightforward and secure. The need for a better overview and control has been growing simultaneously as the code base has grown. Part of the problem has been the use of many separate services, and now the decision has been made to move towards a monolithic Edlib. Besides being a big job, it will also provide us with an excellent opportunity to document and sort out flukes we've been unable to touch earlier. This enables us to reconsider the essence of Edlib - what to keep and what to throw away.

For instance, this means assessing and swapping out problematic or heavy services, such as Open Search, with the more lightweight Meilisearch. We'll also be looking into what systems for operations are sufficient and beneficial for Edlib. It is no secret that K8s is a resource-demanding system and is most likely overkill for the current needs. We are swapping K8s out with the serverless Lambda with Laravel Vapor on top of it.
As the roadmap indicates, this work will occur in the first half of 2023.

Sadly, Edstep - one of the platforms using Edlib, had to be discontinued since the last blog post, but all the learning content used within Edstep lives on in Edlib and can be accessed through Gamilab. Perhaps Edstep will rise like a phoenix from the ashes one day.

If you have any questions, feel free to contact us!

All the best

The Edlib team

· 2 min read

Keeping an open-source project alive is like gardening your plants - you'll need to give the project water and space to grow, but you must also make sure to provide the soil with some needed nutrients now and then. Furthermore plant must be kept healthy by removing obstacles like dead leaves or rearranging the position of some parts. Finally, it needs the proper exposure to the sun.

In Edlib, all this takes place over time. Over the last months, we've been working continuously with gardening by removing dead or overcomplicated code. Such gardening makes room for adding new code in a healthier and more tidy environment. You can follow this work in detail, by visiting our release overview page.

We are delighted to see a new leaf grow out of Edlib as we have received language attributions in terms of translations for Content Author - which now supports Korean (ko) language! 어서 오십시오!

We hope that many more will follow and submit translations in their langauge. Read more about translating Edlib and submit you translations today! Contact us if you have any questions.

We have also worked with improving documentation and examples on the "Edlib Docs" and you can now read all about how NDLA use Edlib.

If you have any questions, don't be afraid to contact us!

All the best

-The Edlib Team