Hi,
I would like to gather your ideas about how we could simplify the Homepage
of XWiki Enterprise.
- Maybe is something that doesn't make sense to have on it?
- Maybe is something that is missing?
Thanks,
Caty
Interaction Designer on behalf of XWiki Development Team
On Wed, May 18, 2016 at 1:20 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
>
>
> Marius Dumitru Florea wrote:
> > Maybe http://extensions.xwiki.org/xwiki/bin/view/Extension/HTML+Macro
> can
> > help.
> Say Marius,
>
> When I read this, it feels like this is something that users need to
> install.
> But this is pre-installed by default or?
>
> I tend to believe that we do not display this properly.
> Agree?
>
There's an information pane on the right saying:
"Bundled With: XWiki Enterprise, XWiki Enterprise Manager"
And if you try to search for it using Administration > Add Extensions
you'll see that it's already installed.
What improvement do you have in mind?
Thanks,
Marius
I'd raise it on the mailing-list.
>
> Paul
>
Hi devs,
Since we’ve removed default support for xwiki/1.0 syntax in XWiki, we should also probably remove it from xwiki.cfg and just document it somewhere on xwiki.org (where we document that syntax and how to enable it). I’m referring to:
#---------------------------------------
# XWiki Syntax 1.0 Rendering Engine
#
#-# Disable particular renderers.
#-# Macro mapping
# xwiki.render.macromapping=1
#-# Velocity interpreter
# xwiki.render.velocity=1
#-# Groovy interpreter
# xwiki.render.groovy=1
#-# Plugin rendering
# xwiki.render.plugin=1
#-# Radeox wiki renderer
# xwiki.render.wiki=1
#-# Simple wiki syntax rendering
# xwiki.render.wikiwiki=0
#-# [Since 2.4M1]
#-# Rendering order: content will be rendered by the first renderer on the list, output rendered by the second, etc.
#xwiki.render.renderingorder=macromapping, groovy, velocity, plugin, wiki, wikiwiki
#-# Maximum number of documents to keep in the rendered cache
# xwiki.render.cache.capacity=100
#-# Default target for external links. Use _blank to open external links in a new tab/window.
# xwiki.render.externallinks.defaulttarget=
WDYT?
Thanks
-Vincent
Ex. I have a page with title 'MyPage' in space 'MySpace'. The title displayed
in browser tab for this page is "MyPage (MySpace.MyPage.WebHome)-XWiki"). I
want to display it like- "MyPage- MyOrganizationName".
How could I do that for every single page on my wiki?
--
View this message in context: http://xwiki.475771.n2.nabble.com/Changing-title-of-the-browser-tabs-for-al…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
1] I need to change "Created by xxx on 2009/09/09 00:00" displayed at every
page bottom (where xxx is any creator of page). By default, on every new
page, creator should display name "MyOrganizationName" irrespective of the
creator.
2] Need to remove user details from "Last modified by SuperUser on
2016/05/12 13:06". It should display only "Last modified on 2016/05/12
13:06".
3] Need to remove whole "Last modified by SuperUser on 2016/05/12 13:06"
line from a specific page (Home page in my case).
--
View this message in context: http://xwiki.475771.n2.nabble.com/change-default-page-data-like-page-create…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
I use such a macro
{{spaceindex space="test"/}}
or
{{spaceindex count="0"/}}
or just
{{spaceindex/}}
There are only pages which were created via REST API. If I press "Create a
new page" link in this space it will not show it (while it exists). I use
xwiki 7.4.2. What can be a source of this problem?
--
View this message in context: http://xwiki.475771.n2.nabble.com/spaceIndex-macro-shows-only-pages-created…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello XWiki users and devs,
The current xwiki.org blog [1] contains mostly release notes announcements,
Bug Fixing Days results and some occasional events that XWiki has taken
part of.
We would like to pump some life into it by encouraging community members to
post articles and news related to the XWiki ecosystem so that everybody can
have a better view of what`s going on.
It can be anything XWiki-related:
* a tutorial / how-to,
* a feature presentation,
* an event where XWiki was presented,
* an extension that you have worked on and published on extensions.xwiki.org
,
* tips and tricks on how to boost productivity with XWIki,
* a real-life problem that was fixed with XWiki,
* news about some public/government agency or even high-profile private
company adopting XWiki,
* etc.
Also, you don`t necessarily have to be a technical person to show your love
for XWiki :)
Anyone interested would have to do it as an individual, member of the
community, using their xwiki.org account. We do not care what company you
are from, as long as your article has content that is interesting/valuable
for the XWiki community.
You should obviously avoid writing SPAM articles, promoting irrelevant
products and generally off-topic stuff.
Here is how to do it in a few easy steps:
1. Log in with your xwiki.org account and go to the Blog Drafts [2] section
2. Create a new sub-page there (use the + button) and write your article.
Don`t forget to save!
3. Contact an XWiki committer either by mail (users or devs list) or by IRC
[3], give them the link to your draft and ask them for a review it.
4. If the review is successful, the article gets moved to the main Blog [1]
and published.
You could view it as a sort of "Pull Request", but for blog articles :)
Note: We also accept cross-posting! You can also share an article on XWiki
that you have written on some other blogging platform. You can post it
entirely or just do a quick summary about it and link to its original
location.
We hope to see some interesting articles and to increase visibility on what
people are achieving with XWiki!
Thanks,
Eduard
----------
[1] http://www.xwiki.org/xwiki/bin/view/Blog/
[2] http://www.xwiki.org/xwiki/bin/view/Blog/Drafts
[2] http://dev.xwiki.org/xwiki/bin/view/Community/IRC
Hi Bryn,
Thanks for your feedback, lots of good points. See below for a point by point comment.
> On 14 May 2016, at 00:47, Bryn Jeffries <bryn.jeffries(a)sydney.edu.au> wrote:
>
> Useful comparisons, but I wasn't sure who the expected reader would be.
I’ve just sent another email explaining more the context and the reason for this initiative.
> The XWiki vs Confluence comparison feels rather biased so wouldn't be very helpful to someone trying to make a rational decision.
The goal is of course to be as unbiased as possible although it’s never fully possible to do so. At least we need to find out the parts that are not correct and remove them or word them better. The goal is to highlight the strengths of XWiki vs Confluence and MediaWiki.
> The table makes them seem identical (perhaps it would be useful to highlight the actual differences) aside from license.
I agree that I’m not sure we need to list the stuff that are similar and maybe it would be better to only mention the differences. Now that said, I think the idea is also for neophytes to wikis to be able to understand this page. We need to decide which we wish to have.
> Both are listed as having a ticketing plugin, but last time I checked (admittedly over a year ago) I couldn't find a robust plugin anywhere close to Confluence's offerings.
You seem to be knowing Confluence which is great, since it’s been more than 10 years that I haven’t used it myself.
Indeed, I don’t know why there’s this "Ticket plugin” mentioned. I’ll check with Caty. XWiki certainly doesn’t have a full ticket extension right now AFAIK. The
closest I can think of is the Task Application: http://extensions.xwiki.org/xwiki/bin/view/Extension/Task+Manager+Applicati…
> The extensions in XWiki really vary in quality, whereas Confluence has a lot of very polished plugins. That's at least been my experience, and I think there's a need to distinguish between high-quality maintained extensions vs. the more hacky ones.
Definitely. I’ve also discussed this with others and it’s time that we start curating extensions and introduce some “Editor Picks” or “Recommended” extensions. I’ll start this in another thread real soon.
> The lack of a markup editor in Confluence is a big difference. Might be worth illustrating further.
Agreed. Maybe the polyglotism too (ability to use various markup syntaxes).
> I think the page hierarchy model is rather difference. Confluence makes chaining of child pages very easy, and access restrictions to child pages is simple to manage. XWiki was a bit clunky by comparison, but that was for 7.1 and maybe the addition of sub-spaces in more recent versions makes this easier to manage.
Could you explain why it’s simpler with Confluence by comparison with, say, XWiki 7.4.3? I think this now at least as easy if not more now. Same for access restrictions to children pages.
See http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization
> The other big difference, to me, is in documentation. XWiki has changed a lot over the years, particularly in the API,
This is not fully correct. A lot of new APIs have been introduced, showing the dynamism of the XWiki community indeed. However, we take very seriously backward-compatibility (so seriously that breaking it fails our build automatically ;)). So all that worked are still supposed to work. Do you have an example that you’ve noticed where it’s not true (it can happen from time to time when we conscientiously decide to break a recent API that we think nobody uses) .
> and a lot of the material discoverable on the web is out of date.
Any example? That would help to fix them.
> My perception is that Confluence's API has been more stable over successive releases and more effort has been invested in keeping documentation up to date.
It’s certainly true that we need to improve on dev documentation (the user doc is probably ok but the dev one can be improved).
> Much of this difference is just a natural outcome of the proprietary vs. open source backgrounds of each system.
Well our goal is to be open source and still be good on all fronts! :)
Re Confluence, they have lots of people working on the doc vs XWiki where it’s the developers doing it, so it’s more a question of manpower than of proprietary vs open source IMO.
What’s interesting though XWiki is a smaller team, we’re still progressing and innovative at least as fast (if not more) as Confluence IMO. Lots of people have commented that they prefer XWiki over Confluence. Some quotes are on https://www.xwiki.org/xwiki/bin/view/References/Testimonials
Anyway, let’s focus on editing this comparison page to make it as accurate as possible. Keep the comments coming and feel free to edit the doc too if you wish.
Thanks
-Vincent
> -----Original Message-----
>> From: Ecaterina Moraru (Valica) [mailto:valicac@gmail.com]
>> Sent: Saturday, 14 May 2016 1:05 AM
>> To: XWiki Mailinglist; XWiki Mailinglist
>> Subject: [xwiki-users] [Proposal] Comparing XWiki to MediaWiki and
>> Confluence on xwiki.org
>>
>> Hi,
>>
>> Since we had users asking on the IRC what are the differences between
>> XWiki and other solutions, it would be a good idea to provide such pages on
>> the
>> website:
>>
>> - XWiki and MediaWiki
>> http://dev.xwiki.org/xwiki/bin/view/Drafts/XWiki-vs-MediaWiki
>>
>> - XWiki and Confluence
>> http://dev.xwiki.org/xwiki/bin/view/Drafts/XWiki-vs-Confluence
>>
>> It would be great to know if you agree with the listed content and if you find
>> other similarities or distinctions between the above solutions.
>>
>> Additionally, what other solutions would you be interested in seeing
>> comparison with?
>>
>> Thanks,
>> Caty