<?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 Antons Sapriko on Medium]]></title>
        <description><![CDATA[Stories by Antons Sapriko on Medium]]></description>
        <link>https://medium.com/@antonssapriko?source=rss-7379801061cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*j4ccP4dhs6N4e9Y1.jpg</url>
            <title>Stories by Antons Sapriko on Medium</title>
            <link>https://medium.com/@antonssapriko?source=rss-7379801061cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:40:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@antonssapriko/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[When will Publica platform be ready?]]></title>
            <link>https://medium.com/publicaio/when-will-publica-platform-be-ready-e7e6d10159b7?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7e6d10159b7</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[self-publishing]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Mon, 04 Dec 2017 11:24:33 GMT</pubDate>
            <atom:updated>2017-12-05T11:10:59.942Z</atom:updated>
            <content:encoded><![CDATA[<p>The platform is not a one-piece thing, it is not a car you are buying, but an evolutionary organism composed of many modules that give its own affordances to authors and readers.</p><p>In this article, I will advocate a piecemeal delivery approach that will allow Publica to launch earlier and in general coincide with the evolution of its community of users — authors and readers.</p><p>First, let’s recap the main affordances Publica is providing to its users</p><ul><li>authors are assisted in spreading their message about their next ebook being crowdfunded on the blockchain</li><li>authors are assisted in deploying their eCommerce on the blockchain — smart contract selling tokens instead of books</li><li>readers need Publica wallets to buy PBL tokens and pay with them for READ tokens with ease. Note, that each author will have its own contract for every single book — each book has its own token e.g. READ-BOOK1 or READ-51-SHADES-OF-GREY</li><li>further, authors need publishing module to actually submit, edit, format their literary work and deploy it to Publica storage that will be in the cloud to start with an eventual move to decentralised immutable storage, tamper and censorship free</li><li>only after this happens, reader wallets should be upgraded to have e-reader affordance to actually use their READ token from a particular book to access it from the storage</li><li>at some later point in time, the community will need a PBL-READ token exchange, decentralised, just like EtherDelta, but surely with a bit better UX!</li></ul><p>As you can see these affordances evolve over time — we do not need all of them at once. Even can say more — it will hurt having all of them released at once effectively having a platform with zero authors and books…</p><p>What is the solution then? How do we solve chicken and egg paradox proprietary to all platforms?</p><p>Publica suggestion is to release precisely the first step authors need to take on the path to a successful ICO of their book or crowdfunding on blockchain as we call it.</p><p>Specifically, it involves so simple things as author registration and personal profile set up. Such page features things traditional to an ICO e.g. project — book title, description, download of first chapters, previous works of the author, potential plan to attract professional editors or other people making a success of the title more probable (think about ICO advisors).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1FbAfQDSpKLc8j3pL9RiA.png" /></figure><p>Book funding budget, delivery time and links to all social channels, community building areas need to be prioritised. It can also contain some token economy setups like READ token price during the presale and the price to be charged when the book is ready as well as the author may grant “grace” period when the tokens to access ready book will be only purchasable from the community of early buyers.</p><p>Technically, it means that we have to work on a piece of technology not even related to blockchain or smart contracts — just simple registration and crowdfunding page builder. While technologically trivial, we have to be in constant sync with authors to calibrate and iterate till the moment, when we see that they literally RUSH TO HAVE IT and once set up, it is actually used for igiting their network of fans and supporters.</p><p>What is the next step?</p><p>It is smart contract deployment engine. Once an author will be clear with an economics of his or her upcoming book, it will be translated to a smart contracted deployed by Publica, but having an author public key set up there as an OWNER. We will deploy it to avoid author pay for gas, while we will, of course, let author export the private key associated with his profile (we will create public and private key ourselves at the moment of registration unless the author wishes to import his or her own).</p><p>And shortly after we need to let author distribute the news that in order to participate, the community has to download Publica wallet that provides seamless connection to an echnage. We think about automation of user account creation with a liit of say, USD 200/year for Publica readers.</p><p>Once this three things are done — first, author has registered the book ICO campaign and ignited community, second, author has deployed smart contract, and third — the fans have downloaded the wallets with a wish to support the author buying tokens — voila, organic demand for PBL tokens surfaces.</p><p>What is next?</p><p>Eventually, author has to finish the literary work and Publica dev team has to finish publishing module. Hope we win the race and there will be no authors waiting for us to deploy their work into Publica storage ;)</p><p>Once done, and wallet apps are enhanced with readers, authors announce to their contributors that it is time now to upgrade to actually start reading the much awaited work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7e6d10159b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/publicaio/when-will-publica-platform-be-ready-e7e6d10159b7">When will Publica platform be ready?</a> was originally published in <a href="https://medium.com/publicaio">Publica</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marketing team roles and responsibilities]]></title>
            <link>https://medium.com/publicaio/marketing-team-roles-and-responsibilities-4175e9131bd5?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4175e9131bd5</guid>
            <category><![CDATA[self-publishing]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Mon, 04 Dec 2017 11:18:50 GMT</pubDate>
            <atom:updated>2017-12-05T11:11:34.675Z</atom:updated>
            <content:encoded><![CDATA[<p>Publica is a project native to blockchain and crypto community and at the same time, it benefits by targeting a specific multi-billion industry of publishing and self-publishing in particular.</p><p>What does it mean for our team composition and direction of our efforts?</p><p>The following activity streams are recognised in general and all of them need to be mirrored in Marketing &amp; Communication.</p><p><strong>STREAM A — CRYPTO COMMUNITY (1 full time position)</strong></p><p>Goals</p><ul><li>everybody present in blockchain and crypto area should know Publica and its story of disrupting the publishing</li><li>create long media tail of interviews, publications, announcements, conference speech videos</li><li>facilitate interest and understanding of PBL token — Publica currency</li></ul><p>Areas of focus</p><ul><li>reach out to media specific to blockchain and crypto markets both worldwide and regional — schedule interviews, distribute press-releases on platform progress</li><li>set up communication and follow up with influencers — this time Publica is not asking your endorsement for an ICO, we are “post-ICO” want to showcase how blockchain disrupts publishing</li><li>find and sign up for AMA and video interviews with video bloggers having substantial reach</li><li>sign up for major blockchain events and introduce Publica founders as keynote speakers sharing experience in how blockchain can disrupt publishing, tokenisation of books and ICO/post-ICO story</li><li>exchanges — the responsibility of this person will be also reaching out to credible exchanges and facilitate Publica PBL token listing there</li></ul><p><strong>STREAM B — AUTHORS, SELF-PUBLISH AUTHORS, EXISTING PLAYERS (1 full time position joined by Josef Marc, CEO for personal outreach)</strong></p><p>Goals</p><ul><li>have a “click” with the authors, they start promoting their next book with Publica and set up their community-building efforts that eventually transform to crowdfunding via PBL and READ tokens</li><li>likewise, to token holder community we have in Telegram now, the goal is to create similar community, but of authors to hear their feedback and wishes, validate our assumptions and have them steer us in the direction most beneficial for them and their readers</li><li>total awareness building, all active self-publishing authors have to know about Publica as their next option within 6–12 months</li><li>bring from 1 to 3 bestselling authors during 2018!</li></ul><p>Areas of focus</p><ul><li>Social networks catering to readers and authors</li><li>Facebook groups for self-publishing authors</li><li>Engage with online guides on “How authors can earn with Amazon”, make them use their contacts to teach how to earn with Publica</li><li>Self-publishing influencers, let them know the new works Publica is bringing to the authors and provoke discussion</li><li>Continue with signing up to events and conferences important to authors, be keynote speaker explaining the transformation and inviting to take part immediately</li><li>Established, bestselling authors personal reach out, networking</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*ccDuAzk_2P_9lIvcxaG-xQ.png" /></figure><p><strong>STREAM C — TECHNOLOGY PR(1 full time position supervised by founder Antons Sapriko)</strong></p><p>Goals</p><ul><li>excite the community with fast progress, solutions and quality</li><li>mirror the development and design progress with a story reflecting people and the process</li></ul><p>Areas of focus</p><ul><li>team video intro</li><li>weekly summaries</li><li>participation in the blockchain/crypto conferences as part of tech track</li></ul><p><strong>STREAM D — LEGAL (founder Antons Sapriko is responsible)</strong></p><p>Goals</p><ul><li>comfortable, clear, complete terms and conditions for authors and readers</li></ul><p>Areas of focus</p><ul><li>doing anything on blockchain is not perfectly regulated, we have to find the appropriate legal framework and produce terms and conditions to let authors safely publish their work and readers own hat they have paid for</li><li>being one of the first among hundreds of ICOs addressing the issue, we should share this know-how on relevant conferences, blogs and interviews</li></ul><p><strong>STREAM E — ANNOUNCEMENTS / CHANNELS / MARTECH — SUPPORT ROLE (1 full time position, assisted by CRO department of Scandiweb)</strong></p><p>Goal</p><ul><li>make good news about Publica happened somewhere be available everywhere!</li><li>increase the conversion rate of people visiting Publica resources to sign-ups and new authors joining</li><li>re-engage visitors to come back — retargeting banners</li></ul><p>Areas of focus</p><ul><li>pool the announcements from all the streams, store them and publish on the website</li><li>reproduce, cross-post the announcements on all related social media, blogs and channels to multiply the outreach</li><li>reproduce and cross-post any media mentions, articles, conference proceedings about Publica</li><li>monitor the feedback and reactions from the community</li><li>set up GTM, heat maps, scroll maps, click-map and make an eye-tracking study</li><li>set up retargeting campaigns</li></ul><p>See more major stuff to bring into Marketing, Communication and PR? Shoot us your opinion at info@publica.io we always all ears, when it comes to suggestions of our community!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4175e9131bd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/publicaio/marketing-team-roles-and-responsibilities-4175e9131bd5">Marketing team roles and responsibilities</a> was originally published in <a href="https://medium.com/publicaio">Publica</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MageBee — how to make boring things fun?]]></title>
            <link>https://medium.com/magento-magicians/magebee-how-to-make-boring-things-fun-d8af7a24cc32?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8af7a24cc32</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[bees]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Fri, 17 Feb 2017 05:09:40 GMT</pubDate>
            <atom:updated>2020-10-05T10:35:15.283Z</atom:updated>
            <content:encoded><![CDATA[<p>What is Magebee? MageBee is a Magento eCommerce store health monitor! We really wanted our design to reflect our vision. Our goal was — logo, landing page and GUI, plus some additional things that can make this project more full and nice.</p><p>…</p><p><a href="https://scandiweb.com/blog/magebee-how-to-make-boring-things-fun/"><strong><em>Head to our blog to find out more about the design process!</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8af7a24cc32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/magento-magicians/magebee-how-to-make-boring-things-fun-d8af7a24cc32">MageBee — how to make boring things fun?</a> was originally published in <a href="https://medium.com/magento-magicians">Scandiweb Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Story of Scandiweb Guinness Record]]></title>
            <link>https://medium.com/magento-magicians/a-story-of-world-record-db7da399d79d?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/db7da399d79d</guid>
            <category><![CDATA[magento]]></category>
            <category><![CDATA[poetry]]></category>
            <category><![CDATA[record]]></category>
            <category><![CDATA[magento-development]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 21:34:00 GMT</pubDate>
            <atom:updated>2020-10-05T10:42:42.966Z</atom:updated>
            <content:encoded><![CDATA[<p>I was sitting in a city center cafe thinking about the ad copy for our next event. Last year we built a chain reaction of some 25 large segments that triggered a band to start performance and this year we wanted to open-source it and invite anybody looking to create great stuff and mix with IT crowd of Scandiweb.</p><p>I was wondering what copy would attract more people… If we throw a party with a known band afterwards, if we use some unusual objects or if we double the size of it? What if we make 50 elements or 100?</p><p>And what if … we make it the largest in the World?</p><p>…</p><p><a href="https://scandiweb.com/blog/scandiweb-makes-guinness-record/"><strong><em>Find out more about our Guinness World Record on our blog!</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db7da399d79d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/magento-magicians/a-story-of-world-record-db7da399d79d">A Story of Scandiweb Guinness Record</a> was originally published in <a href="https://medium.com/magento-magicians">Scandiweb Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scandiweb Project Managers/POs — Powerful CrossFit for the Success of Your Project]]></title>
            <link>https://medium.com/magento-magicians/scandiweb-project-managers-pos-powerful-crossfit-for-the-success-of-your-project-75e53aa3828a?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/75e53aa3828a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[web-project-management]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 01:22:47 GMT</pubDate>
            <atom:updated>2020-10-05T10:17:55.651Z</atom:updated>
            <content:encoded><![CDATA[<p>Once I was presenting Scandiweb success story to the students of my alma mater and got a question “What is special about Scandiweb that made you ahead of thousands of similar companies? What is your secret?”</p><p>I did not feel we have a secret other than persistence and years of working hard, but after few days I figured out that there is something that contributes to our success and is usually not present in other companies I know.</p><p>…</p><p><a href="https://scandiweb.com/blog/scandiweb-project-success-managers/"><strong><em>Find out what it is that makes Scandiweb special on our blog!</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75e53aa3828a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/magento-magicians/scandiweb-project-managers-pos-powerful-crossfit-for-the-success-of-your-project-75e53aa3828a">Scandiweb Project Managers/POs — Powerful CrossFit for the Success of Your Project</a> was originally published in <a href="https://medium.com/magento-magicians">Scandiweb Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the … we were doing the past month]]></title>
            <link>https://medium.com/@antonssapriko/what-the-we-were-doing-the-past-month-30acacdfb5dd?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/30acacdfb5dd</guid>
            <category><![CDATA[magento-development]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Wed, 04 May 2016 19:04:52 GMT</pubDate>
            <atom:updated>2016-05-04T19:04:52.328Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Dear Readers…</p><p>The month was tough as it was this “plateau” effect, when you do lots of things yet you do not feel you make a sizeable definite progress. You just do, do, do, do, do, do, do, do, do, and… there is nothing to write about except your feeling of frustration.</p><p>Yet we all know that we have to go through this “plateau” to arrive to our next PEAK! ;)</p><p>Here it is</p><ul><li>finally we have a team of 4 people, who actively participate in the project</li><li>in about a week readme.io documentation tree will be launched. There are some occassional docs in GitHub e.g. on events-observers, but there will be full skelton to see how it will look like in the nearest future</li><li>there are daily commits to GitHub with new code</li><li>we got positive feedback from magento developers at Magento Developer Paradise. The ones, who code the future of eCommerce highly appreciated our approach of making a relatively “rigid” framework that would advocate and OPTIMISE one way of doing such things as e.g. work with sessions, user authoirsation, etc to avoid guessing of how it can be done, what is the best way. And if it is legacy code to reverse engineer another person logic in choosing one among 10 ways how it can be done.</li><li>we started work on landing page to replcafe current e-mail subscription page at <a href="http://www.ventacommerce.com/">www.ventacommerce.com</a> — plan to deliver it wihin 2 weeks.</li><li>the next big thing in Venta — OOP approach to front end will be rleased in coming month.</li></ul><p>Ou, yes, and we got LOGO :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*7fhYCkREhBNNH7j26yKtxw.png" /><figcaption>Tell us what do you feel about it?</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30acacdfb5dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP7, GOLANG vs PHP, DOCUMENTATION HOME]]></title>
            <link>https://medium.com/@antonssapriko/php7-golang-vs-php-documentation-home-934cb0844578?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/934cb0844578</guid>
            <category><![CDATA[php7]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 07:53:17 GMT</pubDate>
            <atom:updated>2016-03-30T07:53:17.781Z</atom:updated>
            <content:encoded><![CDATA[<p>It is a weekly update time, pals!</p><p>As you may know, Venta will run under latest (at least for us, living in the March of 2016) PHP7. We hope PHP team will keep doing a great job, we trust them, so we decided to use as much as it is possible. We decided to implement scala type hinting in our code and make it best practises for other developers as well.</p><p>Since this was kinda late decision, it leads to code refactoring and reconsidering some parts of code — the good thing is we can remove some validation logic, so make code cleaner.</p><p>Some of you may call this feature a sintaxic sugar, and prefer to write tones of the similar checks. It is OK, we are not religious about that, but we hope there are plenty of developers, who would appreciate that!</p><p>The next, really important thing is: progress on code documentation. As we have learned on our own — developers hate products, when there are no documentation, or existing one is of bad quality. Documentation will be available here within a week <a href="https://ventacommerce.atlassian.net/wiki/display/VCD">https://ventacommerce.atlassian.net/wiki/display/VCD</a> and we look for your feedback to make it an enjoyable and practical for you.</p><p>From the code side, apart from refactoring existing code, we have started working on configuration package. During the progress we have met a new problem — PHP7 is quite new and we have to test it ourself a lot. In this particular case it is hard for us to be sure, what is faster now: an array or an object?</p><p>We are used to use and speak about collections — but right now we do not know, how they should be implemented. We started to research the iterators — basically by profiling some pieces of code and comparing, what is faster. As a result we get another question: what works faster in PHP7: arrays or objects? How should collection be stored: an array of arrays on the object, or array of objects?</p><p>Have something to say about it — we look forward to hear your comments or ideas.</p><p>We are sure about the answer, when we speak about PHP5, but what should we chose for Venta, when PHP7 do the job? We still need some time for the investigation.</p><p><em>Last, but not least: Should we still use PHP? Why don’t we switch to Go/JavaScript/Ruby (on Rails) / any other language you like.</em></p><p>It is quite popular to say that PHP is not good. We are not commenting this statement at all. Everything we know — it is popular. It is well known for our developers, as well as there are billions of developers, that are using PHP every day. Same do we. It is easy to decide to switch to Golang, but… do we really need to do it? We do realize complications of the whole project, so we have decided not to overcomplicate it, at least it is not a time right now, to start a discussion about technologies we are using.</p><p>There is still a place for a mistake, and maybe one day we will find perfectly suitable technic/framework/language, but we switch to that only, after we are 100% sure it is what we need and why do we need it. We prefer to use tools we understand and can fix or upgrade them on our own. We want to give you the same possibility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=934cb0844578" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FIRST LEAD, INVESTMENT OFFERS, HOW DO WE MARKET?]]></title>
            <link>https://medium.com/@antonssapriko/first-lead-investment-offers-how-do-we-market-4be9bb8254c4?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4be9bb8254c4</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Mon, 28 Mar 2016 17:35:50 GMT</pubDate>
            <atom:updated>2016-03-28T17:35:50.863Z</atom:updated>
            <content:encoded><![CDATA[<p>We have failed our tradition of weekly updates! Feels bad! Main reason is that, while coding is being done by the guys, who work on Venta 100% of their time, publishing is done by me, who is spending max 5% that is few hours per week. It is growing, so hopefully in 3–4 month it will be at least 50%!</p><p>We got first potential lead — a project we can build on core Venta platform. Special greetings to You — our dear Customer, if you read our blog! :) It is an ever exciting project initially aimed at e-commerce, but can be equally used in gaming, travel industry and more. Specifically, growth strategy behind it commands ultimate modularity and ease of interfacing with external systems. And then decision to consider core of Venta emerges and we hope we seen will get it into production!</p><p>How do market the project? So far we have been deep under radar, I was just sharing the info within personal Linkedin network, mostly with Magento developers. They provide active input to our Q &amp; A sessions and cheer us up! We are happy to see that apart from our Scandiweb team there are some 50 developers, who have starred Venta repository.</p><p>Investment offers — when people, who know, what we have achieved in Scandiweb learn about Venta project they come back with an investment offer. Feels good! Yet so far we do not need additional funds — we are just few developers — by the way, welcome Ilya Lapkovskis, who replaced Raivis and +1 member is expected to join in the end of April.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4be9bb8254c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TECH: Q & A SESSION 9TH OF MARCH]]></title>
            <link>https://medium.com/@antonssapriko/tech-q-a-session-9th-of-march-d7e77dce0ced?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7e77dce0ced</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[ecommerce-solution]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Wed, 16 Mar 2016 08:42:56 GMT</pubDate>
            <atom:updated>2016-03-16T08:42:56.004Z</atom:updated>
            <content:encoded><![CDATA[<p>TECH: Q &amp; A SESSION 9TH OF MARCH</p><p>Q: Are you aware of current symfony/http-foundation state and if it comply with PSR-7? Are you going to support PSR-7?<br>A: Yes, we have checked whether “symfony/http-foundation” package is PSR-7 compliant — itself it is not, however, there is a bridge package available to add PSR-7 support to it. And, yes, we will support PSR-7.</p><p>Q: Are you going to follow semantic versioning (<a href="http://semver.org/">http://semver.org/</a>)? <br>A: Absolutely — once we reach the point when framework core codebase is well defined.</p><p>Q: Would be great to keep a changelog — <a href="http://keepachangelog.com/">http://keepachangelog.com/</a>. Will you?<br>A: We will — once we reach the point when framework core codebase is well defined. Otherwise, we would be stuck constantly updating changelogs for every change we make at early stage of development.</p><p>Q: If you host the code on github, would it be better to use github wiki instead of atlassian.net for initial paper work? At least until the project has it’s own website.<br>A: We chose Confluence because A) the documentation on project will be quite massive and Confluence makes it easy to maintain/search/organize, B) we use it for most of our documentation for other projects — we are very familiar with it. At later stages, there will most likely to be a documentation dedicated website, however, at this moment we concentrate on documenting all relevant information rather that presenting it nicely. Our GitHub repository is split into packages and it makes more sense to have package specific documentation stored there and the rest — global type of documentation — in dedicated storage — at this moment — Confluence.</p><p>Q: Would be great to have some high level architecture diagrams to understand how components will interact with each other. Will such be available?<br>A: Yes, such diagrams will be provided.</p><p>Q: If you want some help during the research stage, it would be great to have a spreadheet or any other source with components you are planing to implement and packages/ideas/approaches which you have already reviewed/considered/dropped. So anyone could suggest the package or share some ideas about the specific components. For example when you come to translation management you may want to implement XLIFF (<a href="http://www.opentag.com/xliff.htm">http://www.opentag.com/xliff.htm</a>) support for dedicated translation tools integration. I believe you could benefit form out collective experience.<br>A: Yes, we want it to be like this — developer community being actively involved in development. So, this is not a question of IF, but rather a question of HOW — how and where to keep track of all ideas, suggestions and feedback from community. We will decide on this ASAP and let you all know.</p><p>Q: An idea from a frontend standpoint, you should make it similar to wordpress themes, a folder where it houses all frontend functionality so it’s up the developer how the frontend should look and work, seeing as it’s plug and play.<br>A: We haven’t touched framework’s front-end part yet, as we are mainly working on creating framework’s core, so this is not something we can clearly agree on or deny. However, what drawbacks we see in this approach — modularity can suffer. If there won’t be a standard of how themes should be created, 3rd party module installations will be troublesome. Theme file conflicts will be inevitable. Expect more information on front-end architecture as we go on.</p><p>Q: From an ecommerce portion, any way to make it easier to upload products or create products and categories will be beneficial. Especially mass amount of products. I know a lot of users build API extensions for Magento based on JSON feeds. Why not have an extension that is plug in play for JSON feeds?<br>A: There is absolutely no reason not to have it! Such functionality will be a matter of creating new module for framework.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7e77dce0ced" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TECH: MEET AND GREET THE VENTA COMMERCE CODE!]]></title>
            <link>https://medium.com/@antonssapriko/tech-meet-and-greet-the-venta-commerce-code-19ca571ec8f?source=rss-7379801061cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/19ca571ec8f</guid>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[magento]]></category>
            <dc:creator><![CDATA[Antons Sapriko]]></dc:creator>
            <pubDate>Wed, 09 Mar 2016 11:33:59 GMT</pubDate>
            <atom:updated>2016-03-10T02:23:14.683Z</atom:updated>
            <content:encoded><![CDATA[<p>The time has come for Venta Commerce framework to see daylight — code is now available on GitHub and you can see it here!</p><p><a href="https://github.com/ventacommerce">https://github.com/ventacommerce</a></p><p>It’s at early stage of development and only few packages are there yet, but, despite that, we want you to be able to check it. So, please, do it! Check it and let us know what you think! Your feedback is our <a href="https://www.youtube.com/watch?v=oprIEViK350">fuel</a>! :D</p><p>At the moment repository holds 7 packages.</p><p><a href="https://github.com/ventacommerce/venta"><em>Venta</em></a> package is the core of framework — that’s the one you clone and install via composer — the rest of packages will be downloaded as dependencies. You won’t see too much of output when running the framework — that has not been our priority for now. Instead we are building a core that will contain class interfaces and dependency injector, web and console application handlers, framework module loader.</p><p>A quick breakdown on what’s there.</p><p><a href="https://github.com/ventacommerce/contracts"><em>Contracts</em></a><em> package</em> holds all the interface class (contracts) definitions for the framework. The framework itself will be interface-class-heavy in order to achieve plug-and-play modularity for any functionality.</p><p><a href="https://github.com/ventacommerce/container"><em>Container</em></a><em> package</em> implements the dependency injection container functionality that will be used across the framework.</p><p><em>The </em><a href="https://github.com/ventacommerce/http"><em>http</em></a><em> package</em> (built on top of “symfony/http-foundation”) will implement most of that is needed to run framework as web application, while the <em>Console Package</em> (built on “symfony/console”) — for framework to be run via console.</p><p><a href="https://github.com/ventacommerce/extensions-loader"><em>Extensions-loader</em> </a>— as it’s name says — will be responsible for loading all the framework modules.</p><p>And finally the <a href="https://github.com/ventacommerce/application"><em>Application</em></a><em> Package</em> holds the main framework class that “glues” it all together. And a lot more will be added soon, so stay tuned!</p><p>As you will see, all packages include unit tests, and all packages themselves are 100% tests-covered at this moment. And we would like to keep it that way!</p><p>Apart from that, we work on connecting our repositories to <a href="https://scrutinizer-ci.com/">Scrutinizer</a> code analysis tool. It’s a great tool! And it’s free for open-source projects! Which makes it great+! All in all, we work hard on delivering superb quality solution and we are open to any suggestions on how we can make it even better!</p><p>So, check the code and let us know what you think!</p><p><a href="https://github.com/ventacommerce">https://github.com/ventacommerce</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19ca571ec8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>