[GeoNode-users] Geonode and Django Content Management System

[Jesús]

Hi all,

I have succesfully integrated django-cms and geonode for a project
currently available at darwinfoundation.org/geoportal or
geoportal.darwinfoundation.org . Hope we can start uploading data and blog
posts soon. We have an internal geonode with layers, maps, and posts as
part of the workflow.

There's plenty of space for further development but i needed to stop at
some point to cover other tasks.

Current version of django-cms use django 1.6 and has been installed
manually. I have integrated djangocms-blog for multilingual post and a wiki
system also.

I didn't touch the models nor views so we can benefit from geonode project
development . I have not developed geonode django-cms plugins but should be
easy enough to integrated them on geonode.

For already published maps i use iframes to embed them on posts. The
workflow is quite simple. Users publish maps and editors can use those maps
among other resources to publish stories.

I found no problem related with the auth system so far. Admins can use the
group app to give permissions to advance users.

The code needs cleaning and would benefit from refactoring but you can take
a look at https://github.com/jesusjl/cdfgeonode/tree/2.4.x-geonode-1.0.0.

It's just a geonode template with customizations.


Some challenges i found on the path...

Internationalization: I had problems with the way geonode and django-cms
manage internationalization. As far as i know django-cms use parler... So
with some hacks i was able to use both ways to handle this topic. I had a
lot of problems by the way geonode handle layers and maps urls, mostly 404
errors.

Javascript: i had some javascript error difficult to debug when allowing
geonode pages be controlled by django-cms, but i was able to use
placeholders at the homepage. Care should be taken anyway.

Url: I was expecting to use django i18n patterns to handle geonode urls as
part of django-cms but it became really cumbersome. So i just import
geonode url and include django-cms urls at the end. See internalization for
the purpose on it.

Probably someone with more django experience could surpass all this
difficulties. Im sure that integrating django-cms on geonode would leverage
the project to a new level and probably it is worth the investment.

Hope i can help within my means and would love to hear more on this topic.

Jesus

2016-06-23 1:53 GMT-06:00 David Kennewell <david.kennewell at hydrata.com>:

> Hi there Geonode users,
>
> I wanted to share a few developments we've made with Geonode and
> DjangoCMS, and learn if there are others in the community headed in this
> direction.
>
> For those not familiar with django-cms <http://django-cms.org> it's a
> tool that allows users to edit and publish content directly to a website
> through their browser. No coding or web developer required. A typical
> usecase would be a reporting publishing an article to her newspaper
> website.
>
> I've been working with an NGO in Chennai,India to improve the
> accessibility of their work around flood management, and have found the CMS
> a really useful tool to merge reports and Geonode spatial data together in
> a way that readers can engage with. Here's an example:
> http://chennaifloodmanagement.org/en/projects/cag-flood-inundation-mapping/
>
> To achieve this outcome, there's basically two steps. I'd be interested in
> collaborating with anyone who would like to get involved in either of
> these.
>
> *1. Integrating Geonode with DjangoCMS*
> Current status:
> I've bolted these two together with sticky tape and paper glue to
> demonstrate what might be possible on the Chennai project :) Currently I'm
> running two separate servers & databases, with hardcoded links in each
> project to make it look like it's all talking to each other. Apart from the
> dev headache, major drawback here is that users need two django accounts,
> one for editing reports in CMS and another for geonode. Yuk.
>
> Desired status:
> Integrate DjangoCMS as an app under geonode. Now that geonode is running
> on Django 1.8 this is should be possible. If I do go down this path (we
> still need some decent traction here to justify it) I'd really appreciate
> some guidance on how to do this in a manner that allows both easy
> integration for other projects, but acknowledges that this isn't the core
> use-case for geonode, so should be an optional extra (in my opinion).
>
> *2. Authoring geonode maps within DjangoCMS content editor. *
> Once you're geonode/CMS webapp is up and running, your users still need to
> be able to publish geonode maps from the CMS editor. I've written a plugin
> to enable this. Once again, it's bare-bones, but it works and we find it
> useful. I've pushed the code to github here:
> https://github.com/Hydrata/geonode_cms_map
> I'd be happy to write an install doc for this, but that's probably not
> useful until I resolve the above integration issues. Until then it's a
> manual deploy - feel free to reach out if you would like guidance and we
> can work through together - I'm sure I'd learn something from this too.
>
> That's it from me for now, I'd love to hear any similar stories or
> use-cases that might help guide this development in a way that's useful for
> all.
>
> thanks
>
> David Kennewell
> Water Resources Engineer
> Hydrata.com
> +971 55 409 7378
> david.kennewell at hydrata.com
> https://ae.linkedin.com/in/davekennewell
>
>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geonode-users
>
>


-- 
Jesús
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20160626/d0ced5b6/attachment.html>