What's happened with sensenet in Q4 last year
Last year was quite busy in Sense/Net. The main goal of the core team was to publish sensenet 7 stable release, and create as many documentation, tutorial and sample one page apps (like DMS) to improve the product by using it and to present the new view coming with sensenet 7. Also lots of improvements have been done concerning the product, for example in IR and batch actions to name a few.
We want to help you to start building your own solution with sensenet 7, so let us summarize what we achieved in 2017.
sensenet 7 stable release
One of the biggest milestones of last year was sensenet 7 stable release back in december. With the new version, the core source code has not changed much, but SN7 introduced a new, componentized era, by slicing up the product to building blocks or components. After four beta releases we introduced the stable sensenet 7 release. We are going to continuously publish patches for SN7 so you can already start working on new projects using the new version, we have your back.
As mentioned before, SN7 is no more a huge monolithic piece of software, it is built up of different components which can be added to the core Services component based on your own needs. Once this core layer, mother of all components is installed in your project, you can already start working on your solution but we have some really useful components to help you out.
Workflows are a great tool for building business processes involving content creation and response to human interactions (approving a document, completing a task or clicking on a link in a mail).
Notification is a feature for users who want to be informed about Content changes in the system. Users can subscribe to notifications on possible changes to Content items.
We think the best way to develop and improve a product is by using it. That’s why we decided to create a document management system MVP using sensenet 7 as content repository and write a one page app using React. Feel free to clone the solution, study the code or even use or improve it.
The feature set of the DMS MVP were the following:
- basic document library
- basic document management functionalities (create, copy, move)
We started working on re-architecting our Information Retrieval module that consists of two important features of an ECM solution: indexing and querying. Previously the exclusive tool used for this was Lucene.NET with a local index folder. That is a problem in a cloud environment where you cannot rely on having local indexes on the web server. So we decided to decouple Lucene-related indexing and querying operations from the main product and generalize the whole feature.
Now we are close to finalizing the first step: making the IR module replaceable. This will let us create a new search engine for cloud environments that will work as a service. Stay tuned for news on this very soon!
Batch action improvements
We have done some improvements which will make your life better when copying, moving or deleting multiple files. From now, in case of failure, the process will return with detailed information about each problematic files, giving you some hint about the cause of the issue. Use and test it, and feel free to give us feedback.
If you are interested in the development process, follow the link below to have more info about the changes and improvements. https://github.com/SenseNet/sensenet/issues/147
OAuth 2.0 is the industry-standard protocol for authorization. In sensenet we use it as an extension to our JWT authentication to let users authenticate using well-known services (such as Google or Facebook). The benefit is that users are able to sign in to a sensenet application with a single click, without manual registration. Read the blogpost to learn more.
Integrate Google authentication to your own application following our tutorial. In the first iteration we only implemented Google Sign-in, but you can add other services (like Facebook). If you do so, please consider sharing it with the community so that others can use it too!