<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tanel Tähepõld on Medium]]></title>
        <description><![CDATA[Stories by Tanel Tähepõld on Medium]]></description>
        <link>https://medium.com/@tanel.tahepold?source=rss-716e337100d1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*6Zua71rbplyJYOsAlEY6kA.jpeg</url>
            <title>Stories by Tanel Tähepõld on Medium</title>
            <link>https://medium.com/@tanel.tahepold?source=rss-716e337100d1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:16:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanel.tahepold/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building vs buying a document generation solution]]></title>
            <link>https://medium.com/pdf-generator-api/building-vs-buying-a-document-generation-solution-b5e461738b82?source=rss-716e337100d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5e461738b82</guid>
            <category><![CDATA[document-generation]]></category>
            <category><![CDATA[build-vs-buy]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Tanel Tähepõld]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 12:36:10 GMT</pubDate>
            <atom:updated>2021-08-24T15:51:25.425Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>You have two options when it comes to choosing a document automation system. You can either build the tools you need in-house or buy a specialized, industry-specific solution. The most forward-thinking firms and teams intelligently devote their technical resources to projects that create a unique competitive difference. Internal tool development is frequently a source of distraction.</p><p>Is document generation a core part of your product? It can be a core part but is it the unique part (IP) of your product? If not, then maybe it makes sense to buy. Following the best practices, it can be the same if we are talking about document generation. Doc generation can look easy, but you can end up with a massive project inside your product. This is associated with other additional costs, which we will describe in more detail in the next part of the article.</p><blockquote>The fastest-moving companies and teams wisely allocate their engineering resources to projects that move the needle in terms of unique competitive differentiation. Building internal tools is often a distraction. The Facebooks of tomorrow would be foolish to build much of the tooling they need to operate their organizations and infrastructure from scratch.</blockquote><blockquote><a href="https://www.bvp.com/atlas/developer-laws-2019#7-Developer-platforms-enable-companies-to-focus-on-product-differentiation-and-unique-competitive-advantage"><strong>Bessemer Venture Partners: Developer law nr 7</strong></a></blockquote><h3>Do I need documents generation?</h3><p>Document Generation can be useful when multiple documents need to be generated and each document contains a mixture of:</p><ul><li>Static content — the parts that remain the same in each document.</li><li>Dynamic content — content that is customised for the audience or recipient of the generated document.</li></ul><p>Document generation is the process of creating business-critical documents such as invoices, contracts, sales proposals, and work orders. You can automatically create digital documents using your unique templates and branding, as well as gather data from several CRM systems using pre-defined rules, with the correct document generation tools.</p><h3>What to consider before making the decision?</h3><p>There are some crucial elements to consider before making an informed choice. Total cost, project complexity, potential dangers, and competitive advantages are some of these considerations. Let´s take a look at some of the considerations below.</p><h4>Total cost</h4><p>Understand the true costs of building versus buying software, including license models, implementation, and maintenance costs. Companies often find the initial cost of an outsourced document software system is less expensive than developing a similar system in-house. Small and medium-sized businesses, on the other hand, must take into account the cost of implementation as well as continuing maintenance. When these expenses are outsourced, however, they can be more easily controlled since solution providers can recognize problems and reduce risks.</p><h4>Risk</h4><p>Control, performance, and completion — all of which might fail throughout the building process — are all risks that are eliminated when organizations choose to acquire a software package. There are still vendor-related concerns, such as support and dependability.</p><h4>Scalability</h4><p>Purchasing an enormous document software program can be costly to maintain and run, whereas custom solutions can be developed to fit the unique demands of small and medium-sized businesses.</p><h4>Time to develop</h4><p>Developing an internal product requires planning, resource allocation, and preparing for the unknown. Because document generation projects are relatively new, it can be difficult to define the scope. This can lead to significant timeline risk. Building a document software system takes longer and costs more money than purchasing an existing service.</p><h3>The scope of work might be larger than expected</h3><p>The goal of most document generation systems is to deliver a minimal viable product (MVP) as fast as possible. While it is true that with a skilled engineering team, attaining high accuracy on big customers in a timely manner is possible, the last 20% of document variety tends to consume 80% of the time.</p><figure><img alt="Document generation process handled by developers" src="https://cdn-images-1.medium.com/max/1024/1*KtAlkWPxEJyh6_KlCs_ghQ.png" /><figcaption>Document generation process handled by developers</figcaption></figure><blockquote>Developer productivity is the fuel of business, the speed of iteration is a key main factor of success. The Build vs Buy decisions are obsolete, they are replaced by Buy and Build: developers select a set of platforms that are easy to use and can be extended. Twilio is a great example of such a platform.</blockquote><blockquote><a href="https://alven.co/portfolio/#algolia"><strong>Algolia</strong></a><strong> co-founder Julien Lemoine at </strong><a href="https://alven.co/the-debrief-go-to-market-in-dev-tools-part-1/"><strong>Alven.co</strong></a></blockquote><h3>What is PDF Generator API?</h3><p>If you have not heard about the <a href="https://pdfgeneratorapi.com/">PDF Generator API</a>, we would like to shortly introduce our main value proposition. PDF Generator API allows you to easily generate transactional PDF documents and reduce the development and support costs by enabling your users to create and manage their document templates using a browser-based drag-and-drop document editor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tMyveJ6TrfJTSnCXi8zjcg.png" /><figcaption>Document generation process handled by integration</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5e461738b82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdf-generator-api/building-vs-buying-a-document-generation-solution-b5e461738b82">Building vs buying a document generation solution</a> was originally published in <a href="https://medium.com/pdf-generator-api">PDF Generator API</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a low-code platform and why should you care?]]></title>
            <link>https://medium.com/pdf-generator-api/what-is-a-low-code-platform-and-why-should-you-care-3f154c520e42?source=rss-716e337100d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f154c520e42</guid>
            <category><![CDATA[low-code-platform]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[low-code-app-development]]></category>
            <category><![CDATA[integration]]></category>
            <dc:creator><![CDATA[Tanel Tähepõld]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 07:04:18 GMT</pubDate>
            <atom:updated>2020-07-16T07:04:18.687Z</atom:updated>
            <content:encoded><![CDATA[<p>A low-code platform is an application that provides a graphical user interface for building software products with the goal of making the software development process easier and faster for the IT department.</p><p>Although the term “low-code platform” <a href="https://www.forrester.com/report/New+Development+Platforms+Emerge+For+CustomerFacing+Applications/-/E-RES113411">emerged around 2014</a>, the concept isn’t a new one. There has always been “power users” among business users who see an opportunity to optimize a process and take it upon themselves to create their own application. To do so, they often dabble in technologies such as Visual Basic for Applications (VBA) programming in Microsoft Excel. The low-code platform expands that philosophy from only the most tech-savvy of workers to any average employee who sees a business problem or process that a simple app could optimize and solve, and sets out to build it themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayAwIHN9V1b_SZ0GvloQ_g.png" /></figure><p>As low-code platforms are visual environments then it requires less development knowledge and even business professionals can plan and manage workflow applications. With the simplified, component-based library of low-coding solutions, each user can drag-and-drop the chosen pre-developed element into the required place, while connecting the elements, as defined by the logic of the workflow.</p><h3>What are the best low-code platforms?</h3><p>Let’s take a look at some of the best low-code platforms. We used articles from <a href="https://www.softwaretestinghelp.com/low-code-development-platforms/">Software Testing Help</a> and <a href="https://www.pcmag.com/picks/the-best-low-code-development-platforms">PC Mag</a> to compile the short overview. I suggest reading their in-depth analysis of each platform.</p><h4>Appian</h4><p><strong>Tagline: </strong>Automate more codeless. Deliver powerful business applications, faster.<br><strong>Website:</strong> <a href="https://www.appian.com/">https://www.appian.com/</a></p><p>Both sites listed <a href="https://www.appian.com/">Appian</a> in their top ten of low-code tools, Software Testing Help ranked it as 1st and PC Mag as 2nd. Appian features an easy to use drag and drop user interface to build smart applications that will improve the business, customer engagement, and worker efficiency. It is more expensive than some other platforms, but it will speed up the complex application development with it’s native AI and machine learning services.</p><h4>Mendix</h4><p><strong>Tagline:</strong> Low-code Application Development platform.<br><strong>Website:</strong> <a href="https://www.mendix.com/">https://www.mendix.com/</a></p><p><a href="https://www.mendix.com/">Mendix</a> is ranked 4th on both lists and it can take care of the entire software development lifecycle as it also includes tools for project management and software testing. Mendix also features an App Store, prebuilt templates, and integrations which help you to speed up the development process.</p><h4>Zoho Creator</h4><p><strong>Tagline: </strong>Build business applications faster with a low-code development platform<br><strong>Website:</strong> <a href="https://www.zoho.com/creator/low-code-platform">https://www.zoho.com/creator/low-code-platform</a></p><p><a href="https://www.zoho.com/creator/low-code-platform">Zoho Creator</a> is ranked 1st on the PC Mag and 5th in Software Testing Help. One of the main benefits of Zoho Creator is out-of-the-box integrations with other Zoho products. If you are already using any of their products then it is a no-brainer to use Zoho Creator to automate your workflows between different tools.</p><h3>Conclusion</h3><p>With the use of a low-code platform, you can <strong>focus on your company’s digital transformation</strong> and back-office development instead of struggling with the limitation of resources. Low-code applications can seamlessly integrate into legacy systems, so you can easily extend their functionality to the whole company. All tools mentioned above let you convert business logic into functional workflows in minutes. All of them feature a full drag-and-drop user interface and also allow you to write code to complete more complex tasks. Low-code platforms allow collaborate across teams and role-based access controls keep your business secure and your work streamlined.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f154c520e42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdf-generator-api/what-is-a-low-code-platform-and-why-should-you-care-3f154c520e42">What is a low-code platform and why should you care?</a> was originally published in <a href="https://medium.com/pdf-generator-api">PDF Generator API</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we use Open API v3 specification to auto-generate API documentation, code-snippets and clients]]></title>
            <link>https://medium.com/pdf-generator-api/how-we-use-open-api-v3-specification-to-auto-generate-api-documentation-code-snippets-and-clients-d127a3cea784?source=rss-716e337100d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/d127a3cea784</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[open-api]]></category>
            <category><![CDATA[api-documentation]]></category>
            <dc:creator><![CDATA[Tanel Tähepõld]]></dc:creator>
            <pubDate>Mon, 27 Apr 2020 09:22:22 GMT</pubDate>
            <atom:updated>2020-04-27T09:22:22.551Z</atom:updated>
            <content:encoded><![CDATA[<p>Poor or non-existent documentation is one of the five<a href="https://nordicapis.com/5-reasons-why-developers-are-not-using-your-api/"> reasons why developers never use your API</a>. So we wanted to make sure that our API documentation is clear, complies with standards and what is most important — is automatically updated whenever we update our API specification.</p><p>We already had our API defined in Swagger 2.0, but it was a static definition and never used to generate the API documentation, not to mention automatic code generation.</p><h4>The benefits of OpenAPI specification</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxv3XJkvHnY9NLHuj1b5bQ.png" /><figcaption><a href="https://swagger.io/blog/api-strategy/benefits-of-openapi-api-development/">https://swagger.io/blog/api-strategy/benefits-of-openapi-api-development/</a></figcaption></figure><p>I expect that most of you are familiar with OpenAPI, but to whom it is new, here is a quick introduction from <a href="https://swagger.io/docs/specification/about/">Swagger About</a> page who started the movement. The OpenAPI specification is an API description format for RESTful APIs. The specification allows defining the entire API structure from available endpoints to parameters and authentication methods. The API specification can be written in YAML or JSON. The complete OpenAPI Specification can be found on GitHub: OpenAPI 3.0 Specification.</p><p>The main benefits of definition driven API development are better developer experience, faster go to market and increased team independence. You can read more about the benefits of definition driven API development <a href="https://swagger.io/blog/api-strategy/benefits-of-openapi-api-development/">here</a> and I also suggest reading the post about <a href="https://hackernoon.com/is-api-first-development-approach-right-for-your-business-0lr2b58">API driven development</a>.</p><h4>Validating your API specifications</h4><p>Many organisations maintain their API style guides. These documents detail the decisions already made in terms of resource naming, capitalisation, versioning, and other elements on how the API needs to look and feel.</p><p>Although if these style guides are not enforced, we will end up with inconsistent API specifications. While manual reviews are essential, you can also turn to automation to help implement your style guide.</p><p>While searching for a way to automatically validate our Open API specification we found <a href="https://github.com/stoplightio/spectral">Spectral</a> (created by <a href="https://stoplight.io/">Stoplight</a>) an awesome JSON/YAML linter for creating automated style guides. Spectral allows you to describe your API style guide as a set of rules, so you can automatically validate your Open API specification against your API guidelines and make sure that everyone is following them.</p><h4>Generating API documentation</h4><p>There are a lot of different tools and services which allow you to display live API documentation from the OpenAPI specification. You can either self-host the API documentation using tools like <a href="https://github.com/Redocly/redoc">ReDoc</a> or <a href="https://swagger.io/tools/swaggerhub/">Swagger UI</a> or go with a SaaS which provides hosted documentation. Usually, these services offer not only the API documentation capabilities but cover the full API lifecycle. In that category, we have <a href="https://www.postman.com/">Postman</a>, <a href="https://stoplight.io/">Stoplight</a>, <a href="https://swagger.io/tools/swaggerhub/">Swagger Hub</a>, <a href="https://www.apimatic.io/">ApiMatic</a>, to name a few.</p><p>After trying out different services, we finally chose to self-host the <a href="https://github.com/Redocly/redoc">ReDoc</a> as we liked their three-column design and how they present the endpoint parameters, with example payloads and responses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b2QZHasVrIGv1Zhvw5IK1w.png" /><figcaption>API reference documentation with ReDoc</figcaption></figure><p>We also loved how easy it was to deploy the documentation with ReDoc. You can just use their bundled JavaScript and specify URL to your Open API specifications. The code snippet below is everything you need.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/583b819b8d0abf2c4e626ef34a90d227/href">https://medium.com/media/583b819b8d0abf2c4e626ef34a90d227/href</a></iframe><h4>Generating code-snippets</h4><p>Developers must be able to try your API as easily as possible. Therefore you should provide code samples in different programming languages. Creating and maintaining code samples in different languages can be complicated if you don’t have the know-how in the team.</p><p>After doing some research on the Internet, we found this <a href="https://github.com/cdwv/oas3-api-snippet-enricher">small node module</a> which uses the <a href="https://github.com/ErikWittern/openapi-snippet">openapi-snippet </a>generator to create code samples and enrich your Open API specification. You can just run the following command, and you will have code samples for each of your API endpoints.</p><pre>./node_modules/.bin/snippet-enricher-cli --input=openapi.yaml &gt; openapi-with-examples.json</pre><p>And the result is nice looking code samples in your documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*apVGTY3t8i6Fh5ZjOgDkGg.png" /><figcaption>Code samples generated with openapi-snippet</figcaption></figure><h4>Generating HTTP API clients</h4><p>If managing code-snippets is time-consuming, then keeping your API clients up to date is a nightmare, especially if you have a small team. So, besides generating code-snippets for each API endpoint, we also wanted to auto-generate HTTP clients for our API.</p><p>This task turned out to be more complicated than we initially thought, but we ended up with the <a href="https://openapi-generator.tech/">OpenAPI Generator</a>, which is a fork from <a href="https://swagger.io/tools/swagger-codegen/">Swagger Code Generator</a>. The main advantages of the OpenAPI Generator were better documentation and the easy to use node module. What we found important was specifying a configuration file for each programming language. You can find a set of available configuration options for each language <a href="https://openapi-generator.tech/docs/generators">here</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb76625cefb8baf418fc6afdbab7abd1/href">https://medium.com/media/eb76625cefb8baf418fc6afdbab7abd1/href</a></iframe><p>We also created a small bash script to help us automate the code generation and fix some issues in the generated README file. We have another script that automatically pushes client updates to GitHub. This means that by running a single bash script, we create HTTP clients for five target languages (Python, Java, JavaScript, PHP and Ruby) and publish updates to GitHub.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e0579ff13999777156a793e63271bbf5/href">https://medium.com/media/e0579ff13999777156a793e63271bbf5/href</a></iframe><p>If you wish to know more about Open API Generator then I suggest reading the <a href="https://nordicapis.com/introduction-to-openapi-generator/">Introduction to OpenAPI Generator</a> by Kristopher Sandoval on <a href="https://nordicapis.com/">Nordic APIs</a>.</p><h4>Summary</h4><p>The chosen tools were only the best for us, and I suggest that before you start documenting your APIs, you would also do your research with some trials on different tools. You might find some other combination that suits you much better. Selecting the right tooling will save you a lot of time. The good part is that once you have the specification is done, it’s easy to try out different tools and hosting options as well.</p><p>Also, this short piece didn’t cover an essential part of the API development process — the testing. Many of the tools named above — like <a href="https://www.postman.com/automated-testing">Postman</a> and <a href="https://swagger.io/tools/swagger-inspector/">Swagger</a> provide means to automate your API testing and make it part of your API development process. Hopefully, this is something I will cover in the next blog post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d127a3cea784" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdf-generator-api/how-we-use-open-api-v3-specification-to-auto-generate-api-documentation-code-snippets-and-clients-d127a3cea784">How we use Open API v3 specification to auto-generate API documentation, code-snippets and clients</a> was originally published in <a href="https://medium.com/pdf-generator-api">PDF Generator API</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>