Hi there,

I am Alexander Gazibara, the Technical Writer behind the Data Springs User Guides for all of the modules. I've been in the field of Technical Writing for the last 9 years and have been mostly involved with writing the user guides for different types of users and applications (both web and standalone).

I have been writing the guides for Data Springs DNN modules for the last three years, the first one being the Dynamic Image Rotator back in 2006.

This first project proved to be a bit more complex than I originally anticipated because of the fact that it was my first contact with the DNN platform. So, not only was I supposed to get familiar with the module which wasn't that complicated, but with the platform it was built for as well.

Once I got passed that first obstacle, It was a lot easier for me to understand and describe all other Data Springs modules and related tasks. It is still interesting to see how many different functionalities can be developed as DNN modules.

In my experience, even though it may seem a daunting task, it is always useful to read the User Guide as you may find out about all the little functionalities you otherwise wouldn't notice, which can prove to be very useful on the long run.

Usually, with well thought out applications such as Data Springs modules, the main tasks are easy to understand and you can get off the ground even without the manual. Still, there are always these tips and tricks which make you a power user with just a bit of additional effort of reading the guide.

I try to put a lot of effort into creating the Data Springs guides (screenshots, structured information, task oriented information, etc.) because I would like the Data Springs users to be able to easily find the information they need and be able to quickly apply it to complete the desired tasks.

Because the guides are written for you, the users, and since there is no other way of knowing if they are communicating the functionalities properly, I would like to ask you for some feedback and ideas for potential improvements in the future. Thank you and I am looking forward to hearing from you.