Releases: codelitdev/courselit
Code Injection & Themes
Now you can embed code in third party scripts in the <body> tag as well. This will enable various integration like chatbots and popup forms.
Additionally, we have refactored the older functionality of themes and code injection in head which could not be used with recent versions of CourseLit.
Newsletter Signup Widget
Users can now to add a newsletter signup form to their pages.
Additionally, we have introduced a separate page for blog posts so that you can add more content to your blog pages.
Faster loading
This release merges several DB models into one. Due to this change, the loading time has drastically reduced.
Optimised Images
This release brings the next/image support and other UI improvements.
Redesigned users admin area
The users area /dashboard/users have been redesigned to show a paginated list of users along with their properties. It also allows filtering by permissions i.e. Audience and Team.
Serverless
Serverless
This release contains breaking changes and is not compatible with past releases.
In this release, we have implemented the following changes.
New features
- Tags You can now add tags to your courses and blog posts.
- MediaLit All the media management related functionality have been moved to a new platform called MediaLit. You can self-host it (free) or use a cloud hosted version (paid).
Serverless architecture
Earlier we had an ExpressJS based API server and a Next.js based frontend app. Both have been merged into a single Next.js app. This brings CourseLit one step closer to the serverless architecture.
Breaking changes
- Media related functionality will not work with past releases as MediaLit is now used for media management. Hence, the featured images etc., will not resolve correctly if the content is created using a release prior to this one.
- Numeric IDs are replaced with Nanoid based IDs for courses, lessons, purchases and users.
Support
Please reach out on Twitter at @rajatsx with your queries.
Media with access control
All the uploaded media is private by default.
Media can be made public during the upload.
Using local disk for storing media is no longer supported.
Account Disabling
Fixes: Account disabling
Enhancements: Pug based email templates for back-end
UI Improvements
Password-less Authentication
The traditional username/password based authentication system has been replaced with a password-less auth system.
Other changes:
- Remove domain verification end-point used by Caddy for the multi-site configuration.
AWS S3 Compatible Storage Support
If one wants to host the user uploaded files on a storage bucket like AWS S3 or DigitalOcean Spaces instead of local disk space, she needs to set certains environment variables in the .env file of the installation and restart it.
Read more about the configuration here.