<?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 Patryk Porabik on Medium]]></title>
        <description><![CDATA[Stories by Patryk Porabik on Medium]]></description>
        <link>https://medium.com/@patrykporabik?source=rss-1e00239aaf72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*WLyB5BuMy8yvZLQ1.</url>
            <title>Stories by Patryk Porabik on Medium</title>
            <link>https://medium.com/@patrykporabik?source=rss-1e00239aaf72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:43:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@patrykporabik/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[How to create basic plugins in GrandNode]]></title>
            <link>https://medium.com/@patrykporabik/how-to-create-basic-plugins-in-grandnode-a96cd7cbcd22?source=rss-1e00239aaf72------2</link>
            <guid isPermaLink="false">https://medium.com/p/a96cd7cbcd22</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[grandnode]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Patryk Porabik]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 10:11:05 GMT</pubDate>
            <atom:updated>2019-10-29T05:20:45.359Z</atom:updated>
            <content:encoded><![CDATA[<h4>One of the most important features of GrandNode is a fact that it’s pluginable solution. It’s functionality can be easily extended with plugins or widgets. Mentioned architecture allows you to dynamically load new assets in your GrandNode based stores. Whole process is very simple, if you just have general programming knowledge, you will be able to create plugins.</h4><figure><img alt="Beginners guide to GrandNode plugin development" src="https://cdn-images-1.medium.com/max/600/1*HDYpMKHlCbL1DI0qHgk3ug.jpeg" /></figure><h3>First step</h3><p>If you don’t have GrandNode downloaded, visit:</p><p><a href="https://github.com/grandnode/grandnode">grandnode/grandnode</a></p><p>Or</p><p><a href="https://grandnode.com/">More than just an e-commerce platform. GrandNode is the most advanced e-commerce platform at the market</a></p><p><strong>What are plugins in GrandNode</strong>?</p><p>Let’s start with the most simple question. What are plugins in GrandNode? Basically, it’s a little package with compiled files, they are used to extend GrandNode’s functionality and make it more flexible for you. GrandNode has few different types of plugin. We can discint few groups of them. First group, the most popular are payment methods. In e-commerce industry, payment methods are one of the most important plugins, because without them you won’t be able to collect payments from your customers. GrandNode offers for example integration with PayPal, BrainTree, Stripe. Next group, also very important, shipping methods. GrandNode can be integrated with shipping providers like ShipStation, Fedex, UPS.</p><p>Before we start the real coding, you should know that there is an ideal pattern for GrandNode plugin’s name. Ideally, it should be named in the following way<strong> Grand.Plugin.<em>{Group}</em>.<em>{PluginName}</em></strong>, where <em>{Group}</em> is our group of plugin, like Shipping, Payment, Widgets, Misc, <em>{PluginName}</em> is a name of our plugin, i.e GoogleAnalytics, FacebookPixel, PayPal. It’s just recommendation, “MyGrandNodePlugin” will work, but it’s better to keep it consistent.</p><h3>GrandNode plugin basics — structure, required files</h3><p>Plugins in GrandNode are stored in the Plugins folder, in the main directory of solution. Please don’t place source code of plugins into Grand.Web/Plugins folder, because this folder is reserved for compiled, deployed plugins.</p><p>First of all, we need to create a new class in the Grand.Plugins project. We will name it <em>Grand.Plugin.Misc.ExamplePlugin</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/0*ZfCnrVwW2-PfOwt8.png" /></figure><p>In the next step, we have to add necessary dependencies, to perform that, please click the class name in the directories tree, click the right button and select Edit the project file. Then add following code to it.</p><pre>&lt;ItemGroup&gt;<br> &lt;ProjectReference Include=”..\..\Grand.Core\Grand.Core.csproj”&gt;<br> &lt;Private&gt;false&lt;/Private&gt;<br> &lt;/ProjectReference&gt;<br> &lt;ProjectReference Include=”..\..\Grand.Data\Grand.Data.csproj”&gt;<br> &lt;Private&gt;false&lt;/Private&gt;<br> &lt;/ProjectReference&gt;<br> &lt;ProjectReference Include=”..\..\Grand.Framework\Grand.Framework.csproj”&gt;<br> &lt;Private&gt;false&lt;/Private&gt;<br> &lt;/ProjectReference&gt;<br> &lt;ProjectReference Include=”..\..\Grand.Services\Grand.Services.csproj”&gt;<br> &lt;Private&gt;false&lt;/Private&gt;<br> &lt;/ProjectReference&gt;<br>&lt;/ItemGroup&gt;</pre><p>And this, but please note that in below entered code, you have to edit the project name manually:</p><pre><em>&lt;PropertyGroup Condition=”’$(Configuration)|$(Platform)’==’Release|AnyCPU’”&gt;<br> &lt;OutputPath&gt;..\..\Grand.Web\Plugins\</em><strong>Misc.ExamplePlugin</strong><em>\&lt;/OutputPath&gt;<br> &lt;OutDir&gt;$(OutputPath)&lt;/OutDir&gt;<br>&lt;/PropertyGroup&gt;</em></pre><pre><em>&lt;PropertyGroup Condition=”’$(Configuration)|$(Platform)’==’Debug|AnyCPU’”&gt;<br> &lt;OutputPath&gt;..\..\Grand.Web\Plugins\</em><strong>Misc.ExamplePlugin</strong><em>\&lt;/OutputPath&gt;<br> &lt;OutDir&gt;$(OutputPath)&lt;/OutDir&gt;<br>&lt;/PropertyGroup&gt;</em></pre><p>It’s time for tip — please remember that every plugin in GrandNode inherits from BasePlugin. So make this class public and inherit from BasePlugin.</p><p>Each plugin in GrandNode must have the Description.txt file, which is a descriptor of the whole plugin. Inside it you will find information about authors, plugin version or supported version of GrandNode.</p><pre><em>Group: Misc Plugins<br>FriendlyName: Example Plugin<br>SystemName: Misc.ExamplePlugin<br>Version: 1.0<br>SupportedVersions: 4.50<br>Author: grandnode team<br>DisplayOrder: 1<br>FileName: Grand.Plugin.Misc.ExamplePlugin.dll</em></pre><p>This file should be placed in the main directory of plugin. In the same directory, you should also add the logo.jpg file.</p><p>Next ideal moment for tip which is worth to remember — Right click on logo and description files, then select properties and <strong>Copy To Output Directory</strong> set to <em>Copy if newer</em>. It applies to every static file.</p><p>It’s time to add methods coming from <strong>BasePlugin</strong>. Your file now should look like the following one:</p><pre>public class ExamplePlugin : BasePlugin, IMiscPlugin<br>{<br>    #region Methods<br>    public override async Task Install()<br>    {<br>        await base.Install();<br>    }</pre><pre>    public override async Task UnInstall()<br>    {<br>        await base.Uninstall();<br>    }<br>    #endregion<br>}</pre><p>In your main directory of plugin, please create the DependencyRegistrar.cs file. We will register plugin to container.</p><pre>namespace Grand.Plugin.Misc.ExamplePlugin<br>{<br>    public class DependencyRegistrar : IDependencyRegistrar<br>    {<br>        public void Register(ContainerBuilder builder, ITypeFinder typeFinder, GrandConfig config)<br>        {<br>            builder.RegisterType&lt;ExamplePlugin&gt;().InstancePerLifetimeScope();<br>        }</pre><pre>        public int Order {<br>            get { return 1; }<br>        }<br>    }<br>}</pre><p>Congratulations! It’s your first, the most basic plugin in your GrandNode development history! Now, press the right button on your plugin, rebuild it and open GrandNode admin panel. You will be able to install it. It won’t make anything special, but you will be able to install it, so it’s great beginning. If it’s not enough for you, let’s roll deeper, we will add some settings and menu link.</p><h3>How to add settings to your plugin</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/0*pBWPLJtX9jfAk2Ng.png" /></figure><p>It’s time to create class file for our settings, place it in the main directory of plugin.</p><pre>namespace Grand.Plugin.Misc.ExamplePlugin<br>{<br>    public class ExamplePluginSettings : ISettings<br>    {<br>        public string Login { get; set; }<br>        public string Password { get; set; }<br>        public bool IsMale { get; set; }<br>    }<br>}</pre><p>Next file to create is a ConfigurationModel.cs file, it should be placed in Models folder in the main directory.</p><pre>namespace Grand.Plugin.Misc.ExamplePlugin.Models<br>{<br>    public class ConfigurationModel<br>    {<br>        public string Login { get; set; }<br>        public string Password { get; set; }<br>        public bool IsMale { get; set; }<br>    }<br>}</pre><p>Please note that settings are automatically loaded into container, so you don’t have to register them. In the next step we will focus on controller creation, make class public and inherit from BasePluginController.</p><pre>namespace Grand.Plugin.Misc.ExamplePlugin.Controllers<br>{<br>    [Area(&quot;Admin&quot;)]<br>    [AuthorizeAdmin]<br>    public class ExamplePluginController : BasePluginController<br>    {<br>        #region fields<br>        private readonly ExamplePluginSettings _settings;<br>        #endregion<br>        <br>        #region ctor<br>        public ExamplePluginController(ExamplePluginSettings settings)<br>        {<br>            this._settings = settings;<br>        }<br>        #endregion</pre><pre>        public IActionResult Configure()<br>        {<br>            var model = new ConfigurationModel();<br>            model.isMale = _settings.isMale;<br>            model.login = _settings.login;<br>            model.password = _settings.password;<br>            <br>            return View(&quot;~/Plugins/Misc.ExamplePlugin/Views/Configure.cshtml&quot;, model);<br>        }<br>    }<br>}</pre><p>We’ve used the role based authorization to prevent accessing to class by direct link. Now we need to create second action, with the same name, but with parameter which is our ConfigurationModel. This method is used to save our settings. We will need to add two interfaces to our class; ISettingsService to save settings and ILocalizationService to display success message after operation. After that your file should look like this:</p><pre>namespace Grand.Plugin.Misc.ExamplePlugin.Controllers<br>{<br>    [Area(&quot;Admin&quot;)]<br>    [AuthorizeAdmin]<br>    public class ExamplePluginController : BasePluginController<br>    {<br>        #region fields<br>        private readonly ExamplePluginSettings _settings;<br>        private readonly ISettingService _settingService;<br>        private readonly ILocalizationService _localizationService;<br>        #endregion<br>        <br>        #region ctor<br>        public ExamplePluginController(ExamplePluginSettings settings, ISettingService settingsService, ILocalizationService localizationService)<br>        {<br>            this._settings = settings;<br>            this._settingService = settingService;<br>            this._localizationService = localizationService;<br>        }<br>        #endregion<br>        <br>        #region methods<br>        public IActionResult Configure()<br>        {<br>            var model = new ConfigurationModel();<br>            model.isMale = _settings.isMale;<br>            model.login = _settings.login;<br>            model.password = _settings.password;</pre><pre>            return View(&quot;~/Plugins/Misc.ExamplePlugin/Views/Configure.cshtml&quot;, model);<br>        }</pre><pre>        [HttpPost]<br>        public IActionResult Configure(ConfigurationModel model)<br>        {<br>            model.isMale = _settings.isMale;<br>            model.login = _settings.login;<br>            model.password = _settings.password;<br>           <br>            _settingService.SaveSetting(_settings); //save our settings<br>            _settingService.ClearCache();<br>            SuccessNotification(_localizationService.GetResource(&quot;Admin.Plugins.Saved&quot;));</pre><pre>            return Configure();<br>        }<br>        #endregion<br>    }<br>}</pre><p>In next step we need to manage the Views file. In the Views folder create the _ViewImports.cshtml file and paste following code to it. According to .NET Core Docs — The <strong>ViewImports file</strong> is a place where we can write code and place common directives to pull in namespaces that our views need. And that’s why we have to create our file.</p><pre>@inherits Grand.Framework.Mvc.Razor.GrandRazorPage&lt;TModel&gt;<br>@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers<br>@addTagHelper *, Grand.Framework</pre><pre>@using Microsoft.AspNetCore.Mvc.ViewFeatures<br>@using Grand.Framework.UI<br>@using Grand.Framework.Extensions</pre><p>In this step we will create our Configuration view file. In the “Views” folder, create the following file — Configuration.cshtml. At the beginning of the file declare which model you will use on this page. Then, declare which layout you will use. Create simple form as it’s in the example and place the name of the controller (without Controller at the end). You will have to use also antiforgery token, <a href="https://www.devcurry.com/2013/01/what-is-antiforgerytoken-and-why-do-i.html">read about them</a> if it’s something new for you.</p><pre>@model Grand.Plugin.Misc.ExamplePlugin.Models.ConfigurationModel<br>@{<br>    Layout = &quot;_ConfigurePlugin&quot;;<br>}</pre><pre>&lt;form asp-controller=&quot;ExamplePlugin&quot; asp-action=&quot;Configure&quot; method=&quot;post&quot;&gt;<br>&lt;antiforgery-token /&gt;<br>&lt;div class=&quot;form-horizontal&quot;&gt;<br>    &lt;div class=&quot;form-body&quot;&gt;<br>        &lt;div class=&quot;form-group&quot;&gt;<br>        &lt;admin-label asp-for=&quot;login&quot; /&gt;<br>            &lt;div class=&quot;col-md-9 col-sm-9&quot;&gt;<br>                &lt;admin-input asp-for=&quot;login&quot; /&gt;<br>            &lt;/div&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;form-group&quot;&gt;<br>        &lt;admin-label asp-for=&quot;password&quot; /&gt;<br>            &lt;div class=&quot;col-md-9 col-sm-9&quot;&gt;<br>                &lt;admin-input asp-for=&quot;password&quot; /&gt;<br>            &lt;/div&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;form-group&quot;&gt;<br>            &lt;div class=&quot;col-md-3 col-sm-3&quot;&gt;<br>                &lt;admin-label asp-for=&quot;isMale&quot; class=&quot;control-label&quot; /&gt;<br>            &lt;/div&gt;<br>            &lt;div class=&quot;col-md-9 col-sm-9&quot;&gt;<br>                &lt;admin-input asp-for=&quot;isMale&quot; /&gt;<br>                &lt;span asp-validation-for=&quot;isMale&quot;&gt;&lt;/span&gt;<br>            &lt;/div&gt;<br>        &lt;/div&gt;<br>    &lt;/div&gt;<br>    &lt;div class=&quot;form-action&quot;&gt;<br>        &lt;div class=&quot;col-md-offset-3 col-sm-offset-3 col-md-9 col-sm-9&quot;&gt;<br>            &lt;input type=&quot;submit&quot; name=&quot;save&quot; class=&quot;btn-green&quot; value=&quot;@T(&quot;Admin.Common.Save&quot;)&quot; /&gt;<br>        &lt;/div&gt;<br>    &lt;/div&gt;<br>&lt;/div&gt;<br>&lt;/form&gt;</pre><p>Rebuild the plugin and whoa! New feature in your plugin should appear in admin panel!</p><p>How to add plugin to main menu of admin panel</p><p>Everything is fine, but you’re probably wondering how to add plugin to the main menu of admin panel. It’s very simple process. I will create an example with you and in the further projects, you will be able to manage it easily.</p><p>If you want to have your plugin listed here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/0*Pg_QzV-UCX2nqOQv.png" /></figure><p>You should inherit from IAdminMenuPlugin and implement method from inherited interface.</p><pre>public class ExamplePlugin : BasePlugin, IMiscPlugin, IAdminMenuPlugin<br>{<br>    //Previous code added in the first steps<br>    public void ManageSiteMap(SiteMapNode rootNode)<br>    {<br>        var pluginNode = rootNode.ChildNodes.FirstOrDefault(x =&gt; x.SystemName == &quot;GrandNode Team&quot;);<br>        if (pluginNode == null)<br>        {<br>            rootNode.ChildNodes.Add(new SiteMapNode() {<br>            SystemName = &quot;GrandNode Team&quot;,<br>            Title = &quot;GrandNode Team&quot;,<br>            Visible = true,<br>            IconClass = &quot;icon-puzzle&quot;,<br>        });<br>         <br>        pluginNode = rootNode.ChildNodes.FirstOrDefault(x =&gt; x.SystemName == &quot;GrandNode Team&quot;);<br>    }<br>    var Menu = new SiteMapNode();<br>    Menu.Title = &quot;Example Plugin&quot;;<br>    Menu.Visible = true;<br>    Menu.SystemName = &quot;ExamplePlugin&quot;;  <br>    <br>    Menu.ChildNodes.Add(ew SiteMapNode() {<br>    Title = &quot;Settings&quot;,<br>    Visible = true,<br>    SystemName = &quot;ExamplePlugin.Settings&quot;,<br>    ControllerName = &quot;ExamplePlugin&quot;,<br>    ActionName = &quot;Configure&quot;,<br>    RouteValues = new RouteValueDictionary() { { &quot;area&quot;, &quot;Admin&quot; }         },<br>    });</pre><pre>    Menu.ChildNodes.Add(new SiteMapNode() {<br>        Title = &quot;Support&quot;,<br>        Visible = true,<br>        SystemName = &quot;ExamplePlugin.Support&quot;,<br>        Url = &quot;https://grandnode.com/boards&quot;,<br>        RouteValues = new RouteValueDictionary() { { &quot;area&quot;, &quot;Admin&quot;    } },<br>    });<br>    if (pluginNode != null)<br>        pluginNode.ChildNodes.Add(Menu);<br>    else<br>        rootNode.ChildNodes.Add(Menu);<br>    }<br>}</pre><p>Please remember that SystemName has to be unique.</p><p>It’s the end of the first, beginner’s guide to GrandNode plugin development. In next tutorials, we will cover the topic how to create an examples from each plugins group — widgets, payments, etc.</p><p>If you don’t know anything about GrandNode, you are able to check it in the following places:</p><p>Official website — <a href="https://grandnode.com/">https://grandnode.com</a></p><p>GitHub repository, because it’s open source — <a href="https://github.com/grandnode/grandnode">https://github.com/grandnode/grandnode</a></p><p>or if you got stucked, ask question on community forum — <a href="https://grandnode.com/boards">https://grandnode.com/boards</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a96cd7cbcd22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GrandNode: A closer look at the open source e-commerce platform]]></title>
            <link>https://medium.com/@patrykporabik/grandnode-a-closer-look-at-the-open-source-e-commerce-platform-d4978ff95bdd?source=rss-1e00239aaf72------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4978ff95bdd</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[net-core]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[online-shopping]]></category>
            <dc:creator><![CDATA[Patryk Porabik]]></dc:creator>
            <pubDate>Wed, 09 Oct 2019 11:51:44 GMT</pubDate>
            <atom:updated>2020-05-20T11:01:01.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*l8ThPKwRwo__YAdEAFEP0g.png" /><figcaption>Header of GrandNode article</figcaption></figure><p>GrandNode is something more than an average open source e-commerce platform. With the wide range of features, GrandNode is the most advanced e-commerce platform on the market.</p><h3>Overview</h3><p>In a nutshell, GrandNode is based on ASP.NET Core (few weeks ago it was moved from 2.2 to 3.0) and MongoDB. It’s based on the most popular open source tools like: .NET Core, MongoDB, Bootstrap, jQuery, Docker, Amazon S3 or Azure. Thanks to open source and tested, mature solutions, GrandNode is one of the most safiest solutions in the e-commerce industry.</p><p>GrandNode can be called as a perfect solution for C# developers. Its modern code base can be a great material to personal improvements. GrandNode source code has been rewritten and whole application use only asynchronous methods.</p><h3>GrandNode e-commerce features</h3><p>The variety of features, does not allow me to show them all, because it would take a lot of time, but I will point out only the most important for developers and store owners. Because this two groups can get the most from GrandNode.</p><h3>Different types of produts</h3><p>E-commerce platforms developers got us used to use two common types of product — simple and grouped. GrandNode made some improvements on this field. Out of the box, you are able to create few products. Instead of standard and common simple, grouped or downloadable products, you will be able to create auctions with time counter, bookings, product kits and in the newest version, fully working membership portal with paid access to additional material (so it’s free to create portal similar to Coursera or udemy).</p><h3>Cheap &amp; Easy to Host</h3><p>GrandNode is a .NET Core application, so it can be installed on Linux, Windows and Mac OS systems. It also supports Docker. Currently it’s very easy to host it on many, different portals. For example, GrandNode can be installed as a predefined DigitalOcean app, from its installer. You can do it on 5$/mo droplet. So in the comparison to the majority of solutions, it’s a pretty nice score. Still it’s subjective, but I won’t provide any links, because it would be a selfish promo, so if somebody is interested in, just Google it.</p><h3>Extendable with plugins</h3><p>GrandNode is the most advanced e-commerce platform, but still it can be extended with plugins made by GrandNode developers or community. Almost each part of store can be improved by widget or plugin. If you want to get some free or paid plugins, it’s time to <a href="https://grandnode.com/extensions">visit GrandNode marketplace</a>.</p><h3>Multi store, multi vendor and multi tenant</h3><p>It’s probably one of the best features of GrandNode. Out of the box it is a multi store, multi vendor and multi tenant solutions. With multi store feature, you can create as many stores as you want. Each of store can be independent or somehow connected with another one. What’s important, each store is managed from single admin panel.</p><p>When I write Vendor, I meant about Sellers. You can easily create a marketplace portal with products coming from different sellers. Further more, you are able to allow them to apply for a seller account, so they will be able to register and sell in your store.</p><p>And the last, but not least — multi tenancy. It has been added to GrandNode in 4.50 version. With functionality called as “Staff” you are able to create independent store managers and allow them to manage only particular stores. There is a <a href="https://grandnode.com/multi-tenancy-in-grandnode">blog post about multi tenancy in GrandNode</a>.</p><h3>Why it’s the best for developers?</h3><p>As it’s mentioned at the beginning of the article. GrandNode is based on open source solutions, so developers don’t have to do anything extra to start developing. Just download source code and code!</p><h3>Implemented Web API</h3><p>It’s one of the most important features for developers. With implemented OData REST API developers are able to easily integrate GrandNode with customers ecosystem — ERP, CRMs and sales channels. Documentation perfectly<a href="http://docs.grandnode.com/web-api"> describes its work</a>.</p><h3>Simple templating</h3><p>GrandNode default template is based on Bootstrap 4. C# allows to create store from independented, shared components, so you can create themes like puzzles. Take it out from one place and put it in totally different place. Trust me, each developer loves the templating which is simple and easy to learn.</p><h3>The best skeleton for your app</h3><p>With the variety of features, GrandNode can be a great skeleton for your customers app. You can remove or hide particular parts of it and create dedicated solutions for customers.</p><p>The whole source code is published on GitHub — everyone can check it, so here is the link: <a href="https://github.com/grandnode/grandnode">https://github.com/grandnode/grandnode</a></p><p>The official site of the project: <a href="https://grandnode.com/">https://grandnode.com</a></p><p>Polish site of the project: <a href="https://grandnode.pl/">https://grandnode.pl</a></p><p>and developer documentation —<a href="http://docs.grandnode.com/"> http://docs.grandnode.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4978ff95bdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>