="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel

.tag-delete').each(this.ajaxTagDelete); // [semtag] concept list for each tag $$('.doc-tags .tag-list-activator').each(this.ajaxTagConcepts); // [semtag] end concept list for each tag

profile : * Java proficiency * Familiar with unit testing concepts and best practices * Familiar with functional testing concepts and best practices ** Experience with Selenium and the [[Page Objects>>url:https://code.google.com/p/selenium/wiki/PageObjects]] pattern is preferred * Familiar with web technologies: HTML/CSS

. Editing Pages XWiki Syntax Understanding XWiki Basic Concepts Document Lifecycle URL resolution

XWiki = * [[Basic Concepts >> http://enterprise.xwiki.org/xwiki/bin/view/GettingStarted

volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english

translation application. The concept seems to work by application version. We need to verity

concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation

on launchpad.net there is a quite extensively developed translation application. The concept seems to work

. * Skin extensions sounds like an afterthought. I wonder if we cannot somehow merge the concepts together

-USI-1.2.ppt} which explained the concept of Wiki 2.0 (a.k.a Structured Wikis or Application Wikis

summary : Proof of concept for XML based api

adopted the "nested pages" paradigm. It means that you will no longer find the "space" concept in the UI

good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and

once you understand its concepts and how it works! You may be proud, XWiki team! 12 February 2012

/#!/yannickloth/status/172641714576687104]]:((( > #XWiki is a great tool once you understand its concepts and how