About PSOURCE English

<div class="markdown-heading" dir="auto"> <h1 class="heading-element" dir="auto" tabindex="-1">PSOURCE</h1> </div> <p dir="auto"><strong>Open Source software for ClassicPress and WordPress.</strong></p> <p dir="auto">PSOURCE (Power-Source) develops, modernizes and maintains free Open Source software for <strong>ClassicPress and WordPress</strong>.</p> <p dir="auto">Our focus is on practical solutions for websites, communities, Multisite networks, e-commerce and small businesses — with a strong emphasis on <strong>control, privacy, clean code and long-term maintainability</strong>.</p> <p dir="auto">PSOURCE has grown out of real-world projects and real-world requirements over many years. What started as the continuation of abandoned or outdated projects has gradually evolved into a growing ecosystem of interconnected tools.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🧩 What is PSOURCE?</h2> &nbsp; </div> <p dir="auto">PSOURCE is not a single product, nor is it simply a collection of unrelated plugins.</p> <p dir="auto">Many projects can be used independently, while others complement each other and extend each other's functionality. This allows individual tools to become part of more comprehensive solutions for complex projects.</p> <p dir="auto">Some projects originated as older WordPress plugins that were no longer maintained by their original developers. Others have been extensively rebuilt or developed from the ground up over time.</p> <p dir="auto"><strong>Good Open Source software does not have to disappear just because its original developer moves on.</strong></p> <p dir="auto">PSOURCE aims to preserve, modernize and meaningfully evolve such projects — allowing new software to grow from the ideas and work that came before.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🌱 A Growing Ecosystem</h2> &nbsp; </div> <p dir="auto">PSOURCE has grown organically over many years.</p> <p dir="auto">Some of the software was created out of the practical need to keep existing projects and long-established client installations running for the long term. Especially with complex WordPress Multisite environments, replacing working systems with completely different solutions is often simply not a realistic option.</p> <p dir="auto">So the work began: learning, fixing, modernizing, extending and maintaining.</p> <p dir="auto">Over time, individual projects became entire tool suites. Some were consolidated into smaller suites, others were fundamentally rebuilt. At the same time, more and more original development was added.</p> <p dir="auto">The result is an ecosystem where different PSOURCE projects can complement and extend one another.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🚀 Our Projects</h2> &nbsp; </div> <p dir="auto">The PSOURCE organization contains projects covering a wide range of areas.</p> <div class="markdown-heading" dir="auto"> <h3 class="heading-element" dir="auto" tabindex="-1">💼 Business &amp; Administration</h3> &nbsp; </div> <ul dir="auto"> <li><strong>PS Smart Business</strong> – CRM and business management</li> <li><strong>PS Power-Sidebars</strong> – management of custom sidebars</li> <li><strong>Powerform</strong> – form management and form builder</li> </ul> <div class="markdown-heading" dir="auto"> <h3 class="heading-element" dir="auto" tabindex="-1">👥 Community &amp; Communication</h3> &nbsp; </div> <ul dir="auto"> <li><strong>PS Community</strong> – community functionality</li> <li><strong>PS Chat</strong> – chat and communication features</li> <li><strong>Private Messaging</strong> – internal messaging</li> </ul> <div class="markdown-heading" dir="auto"> <h3 class="heading-element" dir="auto" tabindex="-1">🛒 E-Commerce &amp; Multisite</h3> &nbsp; </div> <ul dir="auto"> <li><strong>MarketPress</strong> – powerful e-commerce solution with a particular focus on Multisite and network shop environments</li> <li><strong>PS Bloghosting</strong> – blog and site hosting for WordPress Multisite</li> <li><strong>PS Postindexer</strong> – network-wide content indexing</li> </ul> <div class="markdown-heading" dir="auto"> <h3 class="heading-element" dir="auto" tabindex="-1">🎨 Design &amp; Content</h3> &nbsp; </div> <ul dir="auto"> <li><strong>PS Padma ContentBuilder</strong> – theme and template builder</li> <li><strong>UpFront Framework</strong> – flexible drag-and-drop theme framework</li> <li><strong>PS Wiki</strong> – wiki and knowledge management</li> <li><strong>PS Link Checker</strong> – link checking</li> </ul> <div class="markdown-heading" dir="auto"> <h3 class="heading-element" dir="auto" tabindex="-1">🔐 Security &amp; Administration</h3> &nbsp; </div> <ul dir="auto"> <li><strong>PS Update Manager</strong> – plugin and theme update management</li> <li><strong>PS Live Debug</strong> – development and debugging tools</li> <li><strong>PS Security</strong> – development of a comprehensive, locally operated security solution</li> <li>various libraries and shared components</li> </ul> <blockquote> <p dir="auto">This list is not complete. Individual repositories contain the latest information about each project.</p> </blockquote> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🛠️ ClassicPress &amp; WordPress</h2> &nbsp; </div> <p dir="auto">PSOURCE supports <strong>ClassicPress and WordPress</strong>.</p> <p dir="auto">ClassicPress has a special place in the project: many PSOURCE projects are developed with the goal of expanding what ClassicPress can do and helping build a strong ecosystem of plugins, themes and developer tools around it.</p> <p dir="auto">At the same time, support for WordPress is deliberately maintained.</p> <p dir="auto"><strong>This is not about WordPress versus ClassicPress.</strong></p> <p dir="auto">It is about choosing the right tool for a particular project.</p> <p dir="auto">That is why PSOURCE projects can be useful for both ClassicPress and WordPress — and in many cases can be used on both platforms.</p> <p dir="auto">For older projects, modernization often means:</p> <ul dir="auto"> <li>replacing deprecated APIs</li> <li>improving PHP compatibility</li> <li>modernizing JavaScript</li> <li>reducing obsolete jQuery dependencies</li> <li>fixing security issues</li> <li>improving WordPress and ClassicPress compatibility</li> <li>preserving and extending existing functionality</li> <li>bringing older projects back to life for modern environments</li> </ul> <p dir="auto">The principle is simple:</p> <p dir="auto"><strong>Modernize without unnecessarily breaking working projects.</strong></p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🔒 Control, Privacy &amp; Independence</h2> &nbsp; </div> <p dir="auto">PSOURCE believes that people should remain in control of their own software and their own data.</p> <p dir="auto">For this reason, PSOURCE projects aim to avoid unnecessary dependencies on external services.</p> <p dir="auto">This means, wherever practical:</p> <ul dir="auto"> <li>no unnecessary cloud dependencies</li> <li>no mandatory SaaS services</li> <li>local processing whenever possible</li> <li>transparent Open Source code</li> <li>no artificial limitations where they are technically unnecessary</li> <li>GPL-based software</li> </ul> <p dir="auto">Of course, individual projects may integrate with or require external services for specific functionality. The relevant requirements and privacy information are always documented in the repository of the respective project.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">📦 Open Source</h2> &nbsp; </div> <p dir="auto">PSOURCE is Open Source.</p> <p dir="auto">Most projects are licensed under:</p> <p dir="auto"><strong>GPL v2 or later</strong></p> <p dir="auto">The specific license of each project can be found in its respective repository.</p> <p dir="auto">You are free to inspect, modify, extend and use the code in your own projects, provided that the applicable license is respected.</p> <p dir="auto">And that is exactly what we want.</p> <p dir="auto">A project does not have to remain exactly as it was when it was first released.</p> <p dir="auto"><strong>Fork it. Improve it. Translate it. Extend it. Build something new.</strong></p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🧑‍💻 For Developers</h2> &nbsp; </div> <p dir="auto">PSOURCE is not intended to be a closed product.</p> <p dir="auto">The projects are meant to provide a foundation that other developers can build upon.</p> <p dir="auto">Bug fixes, improvements, translations, new features and independent extensions are welcome.</p> <p dir="auto">Some projects are forks or continuations of older Open Source projects. Others have evolved far beyond their original codebase, while some are entirely original developments.</p> <p dir="auto">As a result, repositories may contain different development stages and historical structures.</p> <p dir="auto">That is part of their history.</p> <p dir="auto">The goal is not to hide that history, but to use it as a foundation for <strong>maintainable and future-proof software</strong>.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🤝 Get Involved</h2> &nbsp; </div> <p dir="auto">PSOURCE is built around Open Source and collaboration.</p> <p dir="auto">Found a bug?</p> <p dir="auto">Have an idea for an improvement?</p> <p dir="auto">Want to translate, extend or modernize a project?</p> <p dir="auto">Create an <strong>Issue</strong> or submit a <strong>Pull Request</strong> in the respective repository.</p> <p dir="auto">Feedback is always welcome as well.</p> <p dir="auto">If you find a project in the PSOURCE organization that you would like to internationalize, extend or further develop for ClassicPress, <strong>get in touch</strong>.</p> <p dir="auto">You do not have to wait for a project to be perfect.</p> <p dir="auto">Maybe your contribution is the next step.</p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🌍 Growing Internationally</h2> &nbsp; </div> <p dir="auto">PSOURCE has its roots in Germany, and many projects were originally developed with German requirements in mind — including areas such as privacy, taxation, e-commerce and legal requirements.</p> <p dir="auto">The project therefore continues to have a strong focus on <strong>German and European requirements</strong>.</p> <p dir="auto">At the same time, PSOURCE is now beginning to grow internationally.</p> <p dir="auto">English translations, documentation and contributions from other countries are very welcome.</p> <p dir="auto">PSOURCE does not aim to cover every region by itself.</p> <p dir="auto"><strong>If someone wants to adapt a project to their own language, country or requirements, that is exactly what Open Source is for.</strong></p> <hr> <div class="markdown-heading" dir="auto"> <h2 class="heading-element" dir="auto" tabindex="-1">🌐 PSOURCE</h2> &nbsp; </div> <p dir="auto"><strong>Power-Source – Open Source from Germany.</strong></p> <p dir="auto">WordPress · ClassicPress · Open Source · GPL</p> <p dir="auto">A project can start small.</p> <p dir="auto">A developer can build something because they need it themselves.</p> <p dir="auto">Someone else can improve it.</p> <p dir="auto">Someone translates it.</p> <p dir="auto">Someone else builds on top of it.</p> <p dir="auto">And eventually, it becomes something larger than the original project.</p> <p dir="auto"><strong>That's the ecosystem we want to build.</strong></p> <hr> <p dir="auto" align="center"><strong>PSOURCE</strong> Open Source for WordPress &amp; ClassicPress</p>