{"id":1463,"date":"2020-05-13T10:20:45","date_gmt":"2020-05-13T10:20:45","guid":{"rendered":"https:\/\/gpsites.co\/dev\/?page_id=1463"},"modified":"2024-08-19T17:58:30","modified_gmt":"2024-08-19T17:58:30","slug":"about","status":"publish","type":"page","link":"https:\/\/demo.vashk.com\/about\/","title":{"rendered":"About Sonat: Who We Are and How We Got Here"},"content":{"rendered":"
\n
\n
\n
\n
\n\n

<\/path><\/svg><\/span>About Sonat<\/span><\/h2>\n\n\n\n

We established Sonat to create a powerful tool to simplify content creation, including drafting, editing, translating, publishing, and fixing the broken feedback loop<\/strong> directly on the content.
<\/p>\n\n\n\n

We used similar concepts and techniques that software engineers use to work together in different phases (writing code, verifying and validating the software, and finally releasing and deploying), simplified it, and applied it to the Rich Text and Structured Content<\/strong> creation and publication.<\/p>\n\n<\/div><\/div>\n<\/div><\/div><\/div>\n\n

\n\n
\"about<\/figure>\n\n<\/div><\/div><\/div>\n<\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n
\n
\n
\n\n

<\/path><\/svg><\/span>Hear from Dan, our founder:<\/span><\/h2>\n\n\n\n

As a software engineer and a product owner, I saw how people from different departments (technical writing, development, marketing, legal, etc.) struggle to create and update content for their products. It was hard enough to collaborate and agree on the content in the first place.<\/mark> But the struggle would persist during the whole process, including the publishing management, keeping track of the changes, correlating the content with the correct product version, and making it accessible to the end-users.<\/mark><\/p>\n\n\n\n


Despite all efforts, still, product manuals didn\u2019t always come out very successful, especially when users kept calling customer service asking for the same information the team meant to address in the manuals. Also, the absence of an effective feedback loop to engage users in creating and updating content was totally felt.<\/mark><\/p>\n\n\n\n

As lifetime users of different products, we all know how difficult it is to find helpful information about a product at the right time. Even after piling up user manuals in our closets for a day, we may still find it difficult to access what we need.<\/p>\n\n\n\n

It would be nice if user manuals could be easily found online, accessible everywhere, and continuously updated and improved based on real users’ experiences, questions, and feedback. And then, maybe, we would even refuse to produce, receive, and collect paper manuals to take better care of our environment.<\/mark><\/p>\n\n\n\n

Inspired by the tools that software engineers used to collaborate and participate in the single source code, I wondered if we could make the same mechanism work for the content creators. <\/p>\n\n\n\n

These tools have enormously evolved and now empower hundreds and even thousands of software engineers to work on the same source code, build, test, and finally deploy software with minimum conflicts and overhead.<\/p>\n\n\n\n

So, I started developing Sonat, a user and eco-friendly tool to provide an excellent experience for all stakeholders of the content writing process; the creators and their end-users.<\/mark> Our online manual creator<\/a> is an easy-to-use tool that allows you to create user guides on an all-in-one platform.<\/p>\n\n\n\n

A better writing experience and happier users<\/h2>\n\n\n\n

Better writing, collaborating, and publishing experience for the producers results in a better end-user experience.<\/p>\n\n\n\n

On the other hand, we create a continuous improvement process with lots of features<\/a> by involving end-users and getting their direct feedback and suggestions.<\/p>\n\n\n\n

The result is:<\/p>\n\n\n\n