Today, I’ll be talking on how to go about integrating the Weceem CMS into a grails-app. It is\u00a0extremely simple and with a couple of steps you would have a CMS that can render traditional as well as custom content merged into your grails application.<\/p>\n
\n
Weceem (as in ‘We seem’ to like it :D) is a Content Management System developed by Marc Palmer for JCatalog that is built on Grails. It is open source and easy to use. \u00a0Apart from being customizable, the other thing that I liked about it was the ability to create custom content, and that too using grails conventions!!.<\/em><\/p>\n <\/em><\/p>\n While it supports traditional content like Blogs, Wiki articles etc, one had the flexibility and support of creating a custom content that might be more in line with the hosting grails app.<\/em> Add to that the ease of a grails plugin that makes it’s integration with an existing grails app a breeze.<\/p>\n \n \n To install weceem simply type<\/p>\n [shell]grails install-plugin weceem[\/shell]<\/p>\n While installing, it will pull a whole lotta stuff as it’s dependencies (searchable, blueprint , ckeditor etc).<\/p>\n Next to see the plugin’s CMS page, one needs to configure a couple of properties.<\/p>\n 1) \u00a0 In your Config.groovy change the follwing line to false \u2026.<\/p>\n [groovy]grails.mime.file.extensions = false \/\/set to true by default[\/groovy]<\/p>\n 2) \u00a0Next if you need content to be served from the root URI (‘\/’) of your application, simply remove the default grails URL mapping for ‘\/’ URLMappings.groovy.i.e doing this will cause the app home page to change to the CMS home page.<\/p>\n Thats all you need to have Weceem up and running.<\/p>\n \n \n Simply hit ‘grails run-app’ and depending on your implementation of Step 2 above either hit ‘\/’ or ‘wcmContent\/show’ and VOILA!!!<\/strong>, you end up on the landing page of the CMS. Click on the ‘edit content repository’ link to go to the Content Repository that looks something like the image below…<\/em><\/p>\n \n \n Weceem CMS landing page<\/p><\/div>\n \n You have a grails powered CMS integrated into your app in matter of minutes. Click on the new content link button, and you are presented with a range of content options \u2026 from HTML to Blogs to Wiki pages and so on.<\/p>\n \n First select existing Blog folder in the CMS dashboard \u00a0and then click on \u00a0the ‘New Content’ -> Blog Entry ..<\/p>\n Add some content …<\/p>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Thats it … All you gotta do now is hit save.<\/em><\/p>\n Now to view our content … Go to the blogs page of your app (URI for page is defined in ‘Alias uri’ section of Blogs folder-edit page.. Default is ‘blog’) or “http:\/\/<serverURL>\/blog”<\/strong><\/p>\n Tip : <\/strong>To serve all content through a specific URI prefix .. just add<\/em>[groovy]weceem.content.prefix = ‘content’ \/\/ replace ‘content’ with anything you prefer … [\/groovy] \n \n \n<\/p>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n In the next blog, I’ll talk how to go about creating your own custom content .. <\/em><\/strong><\/p>\n Till then … peace out .. \ud83d\ude42<\/p>\n \n \n Today, I’ll be talking on how to go about integrating the Weceem CMS into a grails-app. It is\u00a0extremely simple and with a couple of steps you would have a CMS that can render traditional as well as custom content merged into your grails application. Ok … First things first … What is Weceem ? Weceem […]<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":4},"categories":[7],"tags":[800,258,799,4840,802,798],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/5101"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=5101"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/5101\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=5101"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=5101"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=5101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Getting back to Installation …..<\/strong><\/h5>\n
Great … Lets create some content …<\/strong><\/h5>\n
\nto make your blogs page and all other repository content be served from <\/em>\u00a0http:\/\/<serverURL>\/content\/<blog_or_anything_else><\/strong><\/p>\n