Couldn't you limit the size of the images either through wiki syntax ( [[image:foo.png||width="200px"]] ) or through CSS ( max-width: 200px )?

I don't know anything about this, so nothing changes on this part I guess. Nothing changed here. You can use either the Color Themes (for non-technical people) or you can customize the skin of the Blog space but you need to know a bit of CSS (and maybe some HTML/Velocity).

If you're using XWiki only for the blog application then I think there are better alternatives (blog platforms) that were made specifically for this. XWiki's main goal is IMO to help you and your peers organize your information in a collaborative way. The new things that 5.1 brings compared to 4.3M1 are: new search engine based on Solr, virtual mode is on by default, new security module, new localization module, improved Distribution Wizard and Extension Manager in general. Hope this helps, Marius

To handle pictures better, I use following macro: #macro(picture $img, $width) <a href="/xwiki/bin/download/$doc.space/$doc.name/$img">{image:$img| width=$width}</a>#end Width parameter is optional, fixed width or percents can be used. And user is able to click on picture to see bigger picture. See http://platform.xwiki.org/xwiki/bin/view/DevGuide/WikiMacroTutorial for more info about macros.

It is as simple as specifying the width when you insert an image in a blog post using the WYSIWYG editor and you know that the image won't fit the screen size. Each blog post is unique so the author must know what images he's going to insert (unless you are generating the blog posts automatically from some external source you don't control). Plus, I doubt you have tons of images to insert (in that case I recommend you to use the gallery macro). Moreover, the editor allows you to create a link to view the original image, when the user clicks on the resized image. So I don't see the problem here, sorry.

On Tue, Aug 20, 2013 at 3:16 AM, crocket &lt;crockabiscuit(a)gmail.com&gt; wrote: It is as simple as specifying the width when you insert an image in a blog post using the WYSIWYG editor and you know that the image won't fit the screen size. Each blog post is unique so the author must know what images he's going to insert (unless you are generating the blog posts automatically from some external source you don't control). Plus, I doubt you have tons of images to insert (in that case I recommend you to use the gallery macro). Moreover, the editor allows you to create a link to view the original image, when the user clicks on the resized image. So I don't see the problem here, sorry.

> Otherwise, I'd end up coding a blog on top of XWiki. > > >> >>> 2) There don't seem to be pingback or other XXXbacks used to communicate >>> with other blog articles. >> >> I don't know anything about this, so nothing changes on this part I guess. >> >>> 3) For non-web devs or non-technical people, it is not easy to change >>> themes or customize UI to make it look like a blog. >> >> Nothing changed here. You can use either the Color Themes (for >> non-technical people) or you can customize the skin of the Blog space >> but you need to know a bit of CSS (and maybe some HTML/Velocity). >> > > Probably. > > >> >>> >>> The latest stable release is 5.1 now. >>> Has it become useable for me? >> >> If you're using XWiki only for the blog application then I think there >> are better alternatives (blog platforms) that were made specifically >> for this. XWiki's main goal is IMO to help you and your peers organize >> your information in a collaborative way. The new things that 5.1 >> brings compared to 4.3M1 are: new search engine based on Solr, virtual >> mode is on by default, new security module, new localization module, >> improved Distribution Wizard and Extension Manager in general. >> >> Hope this helps, >> Marius >> > > I guess wordpress is a perfect fit for a blog starter. > I'm sad that I need XWiki for a wiki and wordpress for a blog.