Oliver/success
Public Access
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build

Browse Source
This commit is contained in:
Oliver
2025-06-12 19:23:09 -03:00
parent 2fad817159
commit 9b654c8dd4
95 changed files with 556 additions and 556 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
public/en/index.xml
View File

@@ -2,24 +2,24 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title></title>
<link>http://localhost:1313/en/</link>
<link>https://success.odoo4projects.com/en/</link>
<description>Recent content on </description>
<generator>Hugo</generator>
<language>en</language>
<lastBuildDate>Tue, 10 Jun 2025 12:00:00 +0000</lastBuildDate>
<atom:link href="http://localhost:1313/en/index.xml" rel="self" type="application/rss+xml" />
<atom:link href="https://success.odoo4projects.com/en/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Building a Cloud ERP Service with Odoo Community</title>
<link>http://localhost:1313/en/stories/odoo4projects/</link>
<link>https://success.odoo4projects.com/en/stories/odoo4projects/</link>
<pubDate>Tue, 10 Jun 2025 12:00:00 +0000</pubDate>
<guid>http://localhost:1313/en/stories/odoo4projects/</guid>
<guid>https://success.odoo4projects.com/en/stories/odoo4projects/</guid>
<description>&lt;p&gt;&lt;img src=&#34;https://odoo4projects.com/web/image/2890-1713a804/Header_low.png&#34; alt=&#34;ODOO4projects&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;At &lt;a href=&#34;https://ODOO4projects.com&#34;&gt;ODOO4projects&lt;/a&gt;, we specialize in helping businesses succeed with open-source ERP. But we also run our own services on the very same platform — and that’s why we chose to build our &lt;strong&gt;entire cloud ERP hosting infrastructure using Odoo Community V17&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-odoo-community&#34;&gt;Why Odoo Community?&lt;/h2&gt;&#xA;&lt;p&gt;We wanted to test how far Odoo Community could go — and it hasn’t let us down.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;100% open-source, no license fees&lt;/li&gt;&#xA;&lt;li&gt;Highly customizable for specific use cases&lt;/li&gt;&#xA;&lt;li&gt;Strong international community support&lt;/li&gt;&#xA;&lt;li&gt;Clear upgrade path and modular design&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Our objective was not just to use Odoo, but to &lt;strong&gt;push the limits of what’s possible with Community Edition&lt;/strong&gt;.&lt;/p&gt;</description>
</item>
<item>
<title>Transforming Our Cattle Farm with Odoo Community</title>
<link>http://localhost:1313/en/stories/agape/</link>
<link>https://success.odoo4projects.com/en/stories/agape/</link>
<pubDate>Tue, 10 Jun 2025 12:00:00 +0000</pubDate>
<guid>http://localhost:1313/en/stories/agape/</guid>
<guid>https://success.odoo4projects.com/en/stories/agape/</guid>
<description>&lt;p&gt;&lt;img src=&#34;https://estancia-agape.com/web/image/1078-81bed64d/agapei-1.svg&#34; alt=&#34;Estancia Agapé&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Running a cattle farm in Paraguay presents unique challenges — especially when managing operations across &lt;strong&gt;three distinct locations&lt;/strong&gt;. At &lt;a href=&#34;https://estancia-agape.com&#34;&gt;Estancia Agapé&lt;/a&gt;, our goal has always been to stay grounded in tradition while embracing innovation to grow sustainably and efficiently. This is why we turned to &lt;strong&gt;Odoo Community&lt;/strong&gt;, and the results have exceeded our expectations.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-odoo&#34;&gt;Why Odoo?&lt;/h2&gt;&#xA;&lt;p&gt;We evaluated various systems before choosing Odoo Community. The reasons were clear:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Open-source and customizable&lt;/li&gt;&#xA;&lt;li&gt;Robust set of features for inventory, accounting, and logistics&lt;/li&gt;&#xA;&lt;li&gt;Large and active global community&lt;/li&gt;&#xA;&lt;li&gt;No licensing fees&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;But what truly made the difference was the ability to &lt;strong&gt;host the service online&lt;/strong&gt;.&lt;/p&gt;</description>
</item>
</channel>