Comments on XWiki.org Main
Navigation
$xwiki.getDocument('Help.SupportPanel.Content').translatedDocument.title
Failed to execute the [include] macro. Cause: [Current user [incubator:XWiki.evalica] doesn't have view rights on document [xwiki:Help.SupportPanel.Content]]. Click on this message for details.
org.xwiki.rendering.macro.MacroExecutionException: Current user [incubator:XWiki.evalica] doesn't have view rights on document [xwiki:Help.SupportPanel.Content]
at org.xwiki.rendering.internal.macro.include.IncludeMacro.execute(IncludeMacro.java:119)
at org.xwiki.rendering.internal.macro.include.IncludeMacro.execute(IncludeMacro.java:59)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:311)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:88)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.transform(AbstractBlockAsyncRenderer.java:74)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRenderer.tranform(DefaultBlockAsyncRenderer.java:154)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRenderer.execute(DefaultBlockAsyncRenderer.java:137)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:157)
at org.xwiki.panels.internal.PanelWikiUIExtension.render(PanelWikiUIExtension.java:132)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor$DecoratorWrapper.render(DefaultBlockAsyncRendererExecutor.java:67)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor$DecoratorWrapper.render(DefaultBlockAsyncRendererExecutor.java:49)
at org.xwiki.rendering.async.internal.AsyncRendererJob.runInternal(AsyncRendererJob.java:101)
at org.xwiki.job.AbstractJob.runInContext(AbstractJob.java:246)
at org.xwiki.job.AbstractJob.run(AbstractJob.java:223)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
show how many steps the carousel has
This looks good overall, but unfortunately it won't fit nicely in 1024px (actually, a 3 column XWiki hardly ever does).
Is there an elegant way to make the top menu look good on small resolutions?
Personally, I find the number of entries (9) a bit large for a horizontal menu, but it's a big site with lots of information, and every entry seems pretty important.
If all 9 entries are kept, it will be hard to make the menu fit. The problem is that if it starts from the left above the side column it will be inconsistent with the other pages, and if it expands above the right side column it will look unbalanced on the home page.
On the other hand, I think it's OK for the footer to take the whole window width.
can't we serve different skins for different resolutions? We need this also if we even want to make an iPhone/mobile version. If the resolution is smaller than X, we could serve other version (with only one column). We could have a layout selector like the one on w3.org
Stylesheet toogle example: http://www.kelvinluck.com/assets/jquery/styleswitch/toggle.html
Merge Community and Get Involved
+1
Do we really need a Support tab? or are we happy with just "advertisement" on homepage, download page and project page.
All the rest of the items in the menu link to subwikis, while Support will be just a simple page.
+1
Nice work Caty. You know I like it. I already said that to you
Some observations..
Actually we have the carousel and then immediately the footer? It is quite unusual this structure. I thought about another section with content between carousel and the footer.. The footer seems to be half of the homepage. IMO it should stay on the very bottom. The user must 'search' somehow for it to obtain information. We should not give them the footer as the first choice for information in the homepage.
Another question is : what other information will be stored in the carousel steps? We should consider the fact that some people may not be tempted to 'scroll' it. So the 'important' information should be kept either on the first carousel slide or somewhere on the page.
Hope that it will not have an autoplay option (changing slides at a given interval). If yes we should make sure that the page always loads with the first step. (Anyway personally I don`t agree that much the idea of this carousel in this context).
Also it may not be a good idea the presence of 3 big colored glossy buttons in the left. For Play and Get Support we can try to find some other ways to differentiate them. Or to move the download button in the middle section somewhere..