<p>Hi,</p>
<p>I'm looking into developing a CMS like application and I need some pointers on how this would be best achieved.</p>
<p>What I want to do is a "core" like app. So it will provide the "administration" part out of the box but you will need to extend on top of that to build your user facing website. In the admin part (the core that's already provided) you will be able to create content but to display it you would need to extend this core and setup your routes, how to render the content, templates, etc. And any custom thing you might want to do that's not available in the core already.</p>
<p>Ideally the core should be implemented in a way that would allow future updates without breaking what the users built on top.</p>
<p>Any ideas/tips how thins king of app could be architected/designed in GO?</p>
<hr/>**评论：**<br/><br/>niosop: <pre><p>Sounds somewhat like <a href="https://github.com/ponzu-cms/ponzu" rel="nofollow">https://github.com/ponzu-cms/ponzu</a></p></pre>snowpunk_: <pre><p>Hi,
What you described looks like needs to be more similar (in terms of architecture) to a framework rather than a CMS.
I'd go for an MVC pattern, where users will be able to extend the three fundamental parts of your web content application, the data model, the routing model and the frontend/rendering module (facultative, I'd rather implement only REST ep's and create some template layering on top of it that can be optional and some users may opt to implement their frontend solution)</p></pre>joviwap: <pre><p>If you are looking for a Mobile Application you can check <a href="http://docs.kingofapp.com" rel="nofollow">http://docs.kingofapp.com</a></p></pre>
