This is the screenshot, how to write such in confluence ?
What macro to use pls ?
Confluence pages can be set up in hierarchies, with parent pages and multiple children pages, much like folders and sub-folder hierarchies. Files can be attached to these pages.
Go into any space where you have edit rights. Create a new page, lets call it "top", save it. Remaining in the view of "top", click create page again, create one called "middle 1", save it, and remaining in it, create a third one called "bottom". Go back to "top", create another page called "middle 2"
Now look at the page tree. You will see a tree structure
top
middle 1
bottom
middle 2
Related
I am new to Umbraco, and am trying to get to grips with its concepts, in particular how to create lists. For example, you might want a news listing that appears on a page as a list of headlines with mouseover extra content, but you don't want to be able to click on an item and open a full page, it's just there as a list.
You could create a repeating grid of content on the page itself, but that could become unwieldy.
It looks like (correct me if I am wrong) the Umbraco way is to create a parent page, and each news item to be a child page, which can be edited individually, and use a partial view to list them on the required page.
Is this the recommended approach?
If so, two questions :
How do I exclude these news 'phantom' pages from the main navigation - I understand I could set a true/false property on the page with alias umbracoNaviHide and tick this (which excludes it from 'visible' in the queries)
If so, how do I prevent direct access to the news page by its url (the umbracoNaviHide does not prevent the page opening)
Presumably these news pages would show in the back end main view as they would be descendants of the home page?
Any advice welcome!
You can use a Content Repository to hold content objects that won't be pages in your application.
Use following steps:
Step 1: Create the root content repository document type
Go to your backend to the Settings section. Under Document Types create a new type and give it the name Content Elements. After creating this make sure to check the checkbox of Allow at root in order to add this element to your root in the Content section.
Step 2: Add your newly created document type to the root of the content
Go to the Content section and choose to add a new item directly under content ( select the three dots next to Content ).
Select your Content Elements item, give it a name and click save.
Step 3: Remove the checkbox allow at root
You only want to add one Content Reposity item to your root where you will place all items like news, jobs, locations,...
Go to the settings of the Content Elements document type and remove the checkbox of Allow at root.
Step 4: Create a child repository for each type
Using your example I will now create a News document type which will be a child item of the Content Elements repository.
Go to the Document Types under Setting in your backend and choose to add a new document type. Give it a name News and choose save.
In the settings of the Content Elements check the checkbox of the newly created News item to allow as a child.
Step 5: Add the news list in your content
In the content section choose to add a new item under the Content Elements using the three dots.
Select the News item, give it a name and choose save.
Step 6: Create a new document for the news item
One more item is a NewsItem which will hold the properties/information of the item.
Using the same steps of 4 you can easly add this. Be aware that now you have to go to the News item where you will add a check to the NewsItem checkbox to allow as a child.
Also now define some properties of the newsitem.
Step 7: Add newsitems in the content
Using the same steps from 5 you can now add items in the news list.
Step 8: How to place a content element on to your page
If you have created a page you can add a property with a ContentPicker datatype which can be used to select a item from the Content Elements repository. Or using partial views you can create a list from the News to get all items.
Hope this helps!
I have a splitapp application with two cols.
On the left I have a tree that i can navigate level by level.
I want indicate to user the current position in the menu tree by a path.. now I use this trick: insert a button to show the current path
but i don't like this solution. Any suggestions?
P.S. The path could also be very long and I can't see it in the detail page because the content of the detail page could not always sync with the master page.
This really sounds like a breadcrumb. If the path becomes too long you could limit it to show the two latest dives within the object hierachy which would be like ... > Product A > Info D. The individual links can be used for back navigation. From technical perspective the path can be obtained from the binding context.
And this is how it could look like as shown in the SAPUI5 Explored:
The solution is probably not unique to Concrete5 CMS, but I need to build a page with a list of items. Each item would link to a detail page of that item showing a full text description.
Each item on the initial summary page would have the first few lines of the detail page description and a "more" link.
Does anyone know how I could go about doing this in C5?
This is a very common thing to do with Concrete5, and there is a built-in block to handle it -- it's called "Page List".
Note that out-of-the-box, this block doesn't show the first few lines of each page's content, but rather shows the "description" field as entered when creating the page (or editing the page's properties). But I have a free addon available in the marketplace called "Page List Teasers" -- http://www.concrete5.org/marketplace/addons/page-list-teasers -- which adds this functionality to the built-in Page List block.
You can also check out the blog views of the page list - they show how to display an area from another page with all the content blocks they contain, and how to display attributes. You could make a rich text attribute called description then display that as you loop through the list of pages.
I have a dojo layout that creates a sidebar on the left with a list of pages and a center area which is a tab container.
When a user double clicks a page in the sidebar, it creates a new closable tab in the center with a form to edit that page (the form is loaded via the href attribute on the ContentPanes, it's a standard Zend Framework request). However, if I open two or more pages, it creates all the elements and form controls with the same dijit IDs which creates conflicts. (This is expected I guess)
Aside from manually appending the current page ID to every element/dijit on the tab contents, does anyone know of a cleaner way for me to do this? Will this be an issue with the form element name attributes still being the same?
I guess the other approach is to not put id's on any of your widgets.
I want to ask about the objective C on iPhone. I am writing a application, it contains 2 pages. The first page requires the user enter some information. The second page displays the tab page (3 tab).
And I create the first page and the second page in different project. I use the 'Window-based Application' to create the first one and use the 'Tab Bar Application' to create the second one.
However, I don't know how to combine it. Or should I build the second page in the first page project? If so, what should I do and link the tab bar? As I don't know how to create a tab bar content in the first project.
Thank you very much.
The link below might help get you started, but you'll have some difficulty with the Tab Bar Controller part. I usually create all those pieces programmatically...
http://pushplay.net/blog_detail.php?id=27
Does the "info page" collect some information and then not appear again under normal usage (e.g. a login screen)? If so, I would recommend making the "tab page" your main view, and present the "info page" modally (with presentModalViewController:animated:). It shouldn't be too hard to copy the view controller files and xib, if necessary, into the project with the "tab page".