Somehow you've posted the same message about four times. I've only got one answer for it, though...%P It happens that it is not only possible but unnecessary to create a template; blog entries are made through a template already, and you need only modify that template. Of course, all XWiki pages are Velocity templates, but you have two big fat clues that you're editing through a template that's stored as an XWiki document: first, the form isn't the same as the generic document editing template, and has application data fields instead of only Document fields (title, parent, tags, etc); second, the URL is different, as explained below. To find out where that template is, you need to edit the page's source rather than its form data. I don't remember how that's done with the GUI on 1.0, but the URI for editing a page named Web.Page is /xwiki/bin/edit/Web/Page. What you will find is that normally when editing a blog entry you are not using the "edit" action (the portion of the URL after /xwiki/bin/) but the "inline" action, so that the URL ends with /xwiki/bin/inline/Web/Page. This will show you an #include directive, probably #includeTemplate, with the name of the form as its argument. The GUI will also notify you of the existence of any included document[s]. For example, with the skin that I'm using, a right-side toolbar field below the Parent field announces "1 included document:" and lists its name with an "Edit" link next to it. Of course, that will only let you edit the text of the document itself; if (as I infer from your statement that you wish to make entries "more structured") you intend to add fields to the object, you will have to use the class editor on that class, which is another topic. brain[sic]