Issues:006

Go to Issue Log page

Headline "Free form" normal text input before search elements Status Accepted Issue ID 006 Issue Type Enhancement Priority Normal Description I'd like to build up pages where some "semantic information" comes first, then I'll have space for free text input, and then the rest of "semantic information". Taking the user page, like Josef Noll. I'd like to have name, contact info, picture, and tag cloud first The the free input, e.g. About, references... Then information like project leadership, participation in meeting, Currenlty the page is define through Template:User, where a lot of semantic queries are added. All of these queries are shown prior to the information "About the user". Page Link Josef Noll Screenshot Created By Josef.Noll Date Added 2015/09/10

Response If we switch to using forms and templates for content pages, then this is entirely possible. The dev sites I gave you access to show how you can add sophisticated layouts to pages if templates are used across the site. Page Link Responded by Neill Response Added 2015/10/06

Response Hi Josef. Would you like me to come up with a new user page design using a form and template? We could also have it so they are auto created when a new user is added. Page Link Responded by Neill Response Added 2015/10/15

Response Hei Neill, 1) yes, please go ahead with a new user page design. I am currently using "Template:User" and "Form:User" for these pages, thus I suggest you rename them to "User_2014" and start from scratch. The user pages are already autocreated, see "All" or "All participants". 2) Could you do a quick fix with the Form:IoTSec_AI and Template:IoTSec_AI, used in creating ActionItems from the IoTSec.no page? 3) while doing so, can you check why cols=1 (or cols=10) does not work for the User field in the action items? Every new action item has a long field for Action Items Page Link http://cwi.unik.no/wiki/IoTAdmin:AI-001 Screenshot Responded by Josef.Noll Response Added 2015/10/18

Response Hi Josef. Unfortunately Free Text is always shown after the template content. I never use SF's Free Text because you have absolutely no control over it's styling. It would be better to use a form/template field to capture and display this text (it doesn't have to be stored in a property). We can probably use a cunning replace text regex to take the existing free text content and convert it into a field. Page Link Responded by Neill Response Added 2015/10/19