Re: Web page - I am sure we had the website JSP in source control… though right now I’m having a hard time finding it. Perhaps my SVN credentials no longer give me access?
Re: Community Spam filter: I’ve put out an internal Jive message to clarify this queston.
Re: Community integration/performance By default… a JiveX installation for ignite realtime would have a URL like https://(ignite.jiveon.com … If we used this default URL, we’d get better performance as we could take advantage of Akamai global CDN for caching in geo specific edge nodes. If we require the community.igniterealtime.org URL, we will lose CDN acceleration. It’s not cheap nor fun to manage, so I’d not expect Jive to pony up for a custom Akamai account. For this reason, I’d suggest we we use ignite.jiveon.com or ignitrealtime.jiveon.com …
Regarding theming, it will look different than the website and different from the current look and feel. That said, we could modifiy the website to look a bit more like the future community theme by simplifying things a bit. We can definitely do color customization and use Ignite logos, etc.
Also about performance… I have some limited ability to tweak a JiveX cloud installation, given that my day job has me directly involved with our hosting and cloud operations. With both Akamai acceleration and a bit of extra memory, we should have a reasonable experience. I’d really epxect it to surpass what we have now.