<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Custom development — Articles | WebPro Company OÜ</title>
    <link>https://webpro.company/blog/tag/custom-development/</link>
    <atom:link href="https://webpro.company/blog/tag/custom-development/rss.xml" rel="self" type="application/rss+xml" />
    <description>Custom Drupal solutions — tailored features, integrations and components that go beyond what ready-made modules offer.</description>
    <language>en-US</language>
    <lastBuildDate>Thu, 28 May 2026 06:00:00 GMT</lastBuildDate>
    <item>
      <title>How WebPro built its website — custom build, AI-assisted, honest review</title>
      <link>https://webpro.company/blog/how-webpro-website-was-built</link>
      <guid isPermaLink="true">https://webpro.company/blog/how-webpro-website-was-built</guid>
      <pubDate>Thu, 28 May 2026 06:00:00 GMT</pubDate>
      <category>Development</category>
      <category>Custom development</category>
      <category>AI</category>
      <description>The WebPro website is not Drupal and not a ready-made framework. It is a Node.js static generator written from scratch, with most of the code written by AI. This is an honest account of how that happened and what it actually meant. Why not Drupal Drupal is what WebPro works with every day. But Drupal makes sense where there is complex content management logic, multiple user roles, integrations or a need for non-technical people to manage content. The WebPro website has none of those needs. There are about a dozen pages, no content editors, and content changes infrequently. Drupal would have brought all its obligations along — security updates, modules, a database, a deployment process — with nothing to gain. It would have been the wrong tool. Why not a ready-made framework The next…</description>
    </item>
    <item>
      <title>Drupal custom module development — when it makes sense and what it costs</title>
      <link>https://webpro.company/blog/drupal-custom-module-development-cost</link>
      <guid isPermaLink="true">https://webpro.company/blog/drupal-custom-module-development-cost</guid>
      <pubDate>Wed, 14 Aug 2024 06:00:00 GMT</pubDate>
      <category>Development</category>
      <category>Drupal</category>
      <category>Custom development</category>
      <description>Drupal has thousands of contributed modules — but sometimes none of them cover the exact need. Here is when a custom module is the right choice and what it means. When a custom module is the right choice Drupal.org has over 50,000 modules. Before commissioning custom development it is always worth checking: Is there an existing module that does this? Can an existing module be configured to cover the need? Can the module&apos;s behaviour be extended through hooks or plugins? If the answer to all three is &quot;no&quot; — a custom module is the right choice. Typical reasons to build a custom module: Integration with a specific external system (ERP, CRM, payment gateway) Business logic unique to the organisation Performance-critical functionality that a general module does not optimise enough You need…</description>
    </item>
  </channel>
</rss>
