Re-thinking blog.impresscms.org

As you know, blog.impresscms.org is currently powered by Wordpress, which is indeed a state of the heart blogging tool. However, it is not ImpressCMS powered, and that bugs me. Altough Wordpress does achieve blogging more efficiently then ImpressCMS, we will all agree that ImpressCMS is more suited when it comes to empowering a community of people to work on a project. Then we should put our word in action, and use our product to blog about ImpressCMS.

I am confident then SmartSection would achieve the same purpose with more impact:

- articles would get more chances of being read if published on community.impresscms.org
- we would get more chance of have having other dev/designers/supporters bloging about ImpressCMS on community.impresscms if the tool was already here!

And, since the developers of SmartSection are already much invested in the ImpressCMS project, we could take this opportunity to improve SmartSection and make it a more efficient blogging tool.

Thoughts ?

I'm not against the idea... and it would remove the need to create a wordpress theme to match the others

So "smartblog" as a clone of smartsection?

For-me not problem, but is interessant sub-site blog.impresscms.org for blogs special team in impresscms.


This sector for me would be a recess of employees, where they can show their ideas and work. It has no problem in using the smartsection, but I would like to maintain this status and sub-domain if possible.


My personal opnion.

Would you suggest we simply copy/paste the original blog entries, and their comments?

Particulary... i agree with marcan... is more... i will start personal blog ... with the same system marcan propose...

Sounds great, as long as I don't lose my posts

Hi, I think "customizing" SmartSection is not bad idea, however, how about :
http://redmexico.com.mx/modules/qpages/modulo-mywords/

I think if we were to consider other alternatives that are 'Impressed' then we should ensure it's more suited to blogging.

Could we not consider the lifetype module which is a fairly new module development:

http://www.xoops.org/modules/news/article.php?storyid=4099

And as mentioned in the Impress forums.

Smartsections is excellent, but it's just not geared towards blogging, or multi-blogging, by using it people are simply submitting articles, rather than personal blogs/diaries.

WordPress was chosen because it excels at what it does - Bloggin and Smart sections also excels at what it does, but at the moment that's not blogging.

XoopsLifeType 1.0.2 RC with the newest LifeType Version 1.2.6:

http://www.impresscms.de/modules/wfdownloads/singlefile.php?cid=6&lid=27

1.- If we said: "ImpressCMS can be used for blogging", we can not use WordPress for our own blogs.
2.- We need "multiblogging" capabilities: "multieditors" is not enough. But really there are few multiblogging systems.
3.- Smartsection can be used for it, but really it would need make a new module (smartsection based). It will be a very hard work.
4.- Mywords: excelent module..but has not multiblogging; it does not run on ICMS until Eduardo will make a script for adapt his modules to ICMS. And it will need a library: rmcommon.
5.- XoopsLifeType: I like lifetype very much (more than WP MU) but it uses Frameworks (Do will we use this library when ICMS runs on its own way?) and we need think about updates (Lifetype 2.x is on the way http://lifetype.net/category/development).

I vote for Lifetype: seems the less difficult.

Quote:

This is a valid point... either the Wordpress needs to share with another site via OpenID (showing this functionality with Impress) or it should be a module.

OpenID will be implemented on MediaWiki as soon as I have arranged a schedule for installation/backups.

Quote:

Agreed

Quote:

I wonder... how much work is involved?

SmartSection can be cloned to SmartBlog - what templates need changing? What else is needed?

Quote:

This is something we need to address with Eduardo. Having compatibility with his code will increase sales of any of his commercial products.

Quote:

What code is involved to "module-ise" LifeType? Do we need Frameworks? Can we convert this to run ourselves rather than relying on another developer?

Of course - another possibility could be this:

http://wiki.lifetype.net/index.php/Plugin_openid

Oops, this option is very gooooooooooood

Quote:

nobody will be able to complain to remember some passwords and will be able to be registered tranquilamente.
If my memory serves me right it also already counts on some translations in other languages.

And the important thing Giba - we do have OpenID working in some form on Marcan's test branch, based on both Marcan's work - and the work of the xoops module developer.

This could be added to the "towards 1.1 branch" - that we use for features for the Impress Community sites...

Today I gained the day and you he is turning one I guess. I was thinking the same thing.

Giba/everyone else:

For speed: I propose one of two things...

1) LifeType (stand-alone) + openid hack

2) "SmartBlog" = Smartsection + new templates + social networking (either smartobject or Sato-sans) + some new code for "digg"ing...

Please no wiki plugin and making wiki as blog.

As module I prefer Lifetype but without the need of frameworks.
If icms is gonna make use of frameworks then there will not be a differ between icms and xoops.
Icms must not depend on xoops developing in the future. I sincerely hope icms is moving its own way in future.

If icms wants to implement somekind of 'frameworks' i prefer a central 'frameworks' for all modules which need this.
Something like smartobject. But no frameworks.
I at least don't want to depend on frameworks which is in fact a xoops neccesary for some modules to run.

my humble 2 cents,

Grtz., Shine

No plans to turn wiki into a Blog

What would be the difference with implementing lifetype versus wordpress?

Its the same boat, just a different color.

We would still be relying on an outside source for blogging. I thought the idea was to showcase that iCMS can act as a blogging system?

I believe that the original plan to clone SS and create smartblog was the best option. From there customizing for blogging would be cake. A few features added, and a little templating. Boom! Impress has native blogging capabilities.

Add to smartblog.

* Social Networking Options.
* Tag Clouds.
* SEO - If its a blog. SEO is a must. urls/should/natively/be/clean
* Ability to define how many articles per page.
* [pagebreak] - utilizing numbered pages instead of dropdowns. < 1 2 3 ... >
* Rating System - Impressions? (stars , kudos, up/down, whatever)
* On the fly comments - login and post at the same time
* Groups access per article. (Public, Private)
* Blocks - Article Calendar, Article Archive, etc.
* New Templates

Ok: SmartBlog I think it should be

* Social Networking Options. - we have either Sato-san or the ones built into SmartObject for this

* Tag Clouds. - "tag" module - until the later "tag" support is built into the Core
* SEO - If its a blog. SEO is a must. urls/should/natively/be/clean - Apparently possible with SmartSection - although I've never used this part
* Ability to define how many articles per page.
* [pagebreak] - utilizing numbered pages instead of dropdowns. < 1 2 3 ... > - Should be possible
* Rating System - Impressions? (stars , kudos, up/down, whatever) - Basic support via SmartObject - could be expanded
* On the fly comments - login and post at the same time
* Groups access per article. (Public, Private) - Good feature suggestion
* Blocks - Article Calendar, Article Archive, etc.
* New Templates - Do-able .. and we have the talent here to do this

Most of these features exist already - so I don't think this is impossible to do at all!