I need to create a content presenter template and integrate it into webcenter. But I am new in this technology. Can anyone give any reference from where I can learn these stuff, any step-by-step tutorial. Any information will be very helpful.
In addition to the resources Peter provided, this will help you as well:
Creating and Using Page Templates in Oracle WebCenter Portal Applications - In a WebCenter Portal application, page templates provide a means for creating the application’s pages with a common look. Each page of an application is stamped out from a page template, which provides common elements for the page. The individual pages can add their specific content, extending the page template. In this training module, you learn how to create and use page templates in both WebCenter Portal applications and in WebCenter Portal: Spaces.
Recorded Presentation 50 minutes, 49.3 MB
Presentation slides (PDF) -- you'll have to visit the page above to find
Related Documents -- you'll have to visit the page above to find as I cannot post more than 2 links.
Here are a couple of links to the documentation. The best ones are the Users Guide and the Developers Guide.
Publishing Content Using Content Presenter
Creating Content Presenter Display Templates
Related
I have a question to Magnolia CMS (integrated with Spring) users.
I have to write e-shop integrated with CMS where we can divide all pages into two categories:
Edited and added by admin
static pages like user account settings, shopping cart etc.
First ones, must be totally customizable by admin - I mean, admin must be able to create his own template, add text areas or graphics/video whenever he wants. He also must be able ( this is very important) to create new products which must be also stored in db to be accessible for the application code ( to fill the products list by myself in the code or to set the prices on the static admin pages).
So user can add as many products as he would like, create separate template for some of them and I have to be able to search for this products in db ( for example when user try to use search criteria). The search panel must be created by me - but where admin will place it is up to him.
The second type of pages are static pages done in JSP and I do not expect to change it using CMS.
As the second type of pages is of course not a problem, I do not know what CMS solution I should use for first type of pages.
I thought about Magnolia CMS, but as I can see all templates must be created by programmer in the code.
Also I'm not sure if it's possible to implement mechanism to maintain products ( inside the e-shop) - from one hand admin must be able to add templates for them in CMS, but I must be able to access them from the code ( to maintain them at shopping cart, make invoice etc). The product prices are set from admin panel ( static pages) as well- not from CMS of course. Maybe I can add any single product at the static pages ( insert it into the db) and somehow connect CMS page with it ?
I also need to add that main page template must be designed by HTML designer, so perhaps it would be plain HTML and this main template would be updated due to the admin needs in CMS.
Cloud anybody please advice me the best CMS solution where I can achieve all this ?
Best Regards
I've seen fair number of shops implemented that way with Magnolia where you use spring & web flow to manage a shopping cart and checkout process, while letting editors to create & customise products & categories & promos available in the shop.
You can also get similar (w/o spring) integration just by installing shop module of Magnolia. It's product and product category management might come in handy even if you were to replace checkout by your own.
To answer the other questions and stipulations
you can write your templates in ftl and models in groovy and have those hosted inside of the repository, thus giving access to them to editor and allowing her to change whatever needs to be changed. However there is also danger in that since templates are responsible for generating html, editor might be able to break html layout by making changes directly to the templates. While you want editor to create new products and modify existing ones, Magnolia lets you separate template of products from the content of products so you can let editor to edit just all the fields that you deem editable for given product without having her to ever access html or ftl directly.
as you mention, html will come from designer, so what you pbly want is to take that html, break it into functional blocks that repeat in multiple pages, save it as ftl templates and replace sample text in there with FM tags to retrieve such data from Magnolia. Actually, even better, download the STK static prototype and hand it over to your graphic designer. Tell her to create design by changing css/js/images only, but not to change structure of the html itself in the prototype, then you can truly just drop in css/js/img provided back to you by the designer.
regarding static pages - you can always serve them from Magnolia even if you don't expect anyone to ever edit them (since it usually happens sooner or later that someone wants to edit them) or you can simply configure bypass for the url for such pages and have Magnolia ignore them so they can be served by underlying application server container
to bring in Spring based application, you might consider looking in more details at and using Magnolia's Blossom module which will in turn let you annotate your spring controllers to be treated as Magnolia templates to make integration even more simple.
HTH, Jan
I have been using EZ Publish for a while but I am still a bit confused about the difference between the Article, Article (Subpage) and Article (Mainpage) content classes.
Just wondering what contexts these are meant to be used in.
Content classes in eZ Publish are a dime a dozen. eZ Publish ships with a bunch of 'default' content classes but you are not expected to use all of them. In sites I work on for instance I generally get rid fo the subpage and mainpage versions of the article and then modify the article class to better fit my needs. That is one of the strongest attributes of eZ Publish, the ability to create custom classes in the admin area and then just writing a custom template to serve up the content. Full documentation on what exactly an eZ Publish Class is can be found here. Remember to hit up the eZ Publish Share site, a place for eZ Publish developers to share questions and answers.
The if you are using one of the built in designs (ezwebin for instance), the Article would typically be used for single page articles and the Article (Mainpage) and Article (Subpage) would be used to construct multi-page articles.
Use the Mainpage as the container and fill it will subpages (one for each page of your article) and the templates should add an Article Index with links to each page of the article.
If you want articles to be presented as just a single page use the plain Article class.
I have just migrated a lot of content from an old webpage to a 2.5 Joomla website. Almost every imported page contains a contact detail of one person from a 3-10 people pool.
I would like to define these contacts as Joomla contacts and just simply link to these profiles from every page.
How do I find or create a permalink to these user profiles?
I don't know of a native Joomla way of doing this, but due to the frequent ugliness of Joomla urls, we use YOURLS as an all-around link shortener on all of our sites. It comes with a front end that users are able to create their own links, etc., but we just use the mechanism, and some of the other features on the admin site of things - the mechanism itself is quite straightforward and easy to use once you create one to see what needs to be in the database for it to do it's magic.
I'm just starting to play around with Orchard CMS. I like what I see so far, but I need to be able to create pages that display record details for data stored in another system. Does any one know if that is possible?
I have a SQL Server database that hold real estate property record information. This information gets displayed on the web. On that same website are informational content pages (FAQs, Contact Us, Home, etc...) What I would like to to is leverage the CMS portion of Orchard for the content pages. Then I would like to write a module using the Orchard that would get the real estate info, allow users to search parcels, and display detail pages for each parcel.
If you view the site http://www.sc-pa.com/search you can search by last name "smith" and select one record. That may help illustrate what I need Orchard to do.
Yes, that is possible, but your scenario is way too vague to get into any specifics. Can you elaborate on exactly what you are trying to do: what does the external data look like, where is it stored, how do you want to integrate it into Orchard, do you need any integration with content types and parts, or with search, etc.
One alternative is to expose ur data as web service or odata endpoint and then use jquery to do asynch call to get json data. Then ur home free.
Create a page and put the javascript in that or include a ref to js file.
I come from a background of coding my client website projects from scratch with MySQL and PHP. They are typically public facing sites with a mixture of static content, dynamic content plus a little functionality here and there (i.e. account, searching etc). Nothing too heavy.
So I generally code up a little CMS site to let them update what they need to, put it in a protected folder and that's that.
Now I'd like to use CodeIgniter and more of a MVC approach for my next site. Should I be doing anything to separate the CMS out from the rest of the site or is it simply another area (with its own controllers/models etc) and extra authentication?
There are several good methods to create an admin interface in CodeIgniter described at:
http://philsturgeon.co.uk/news/2009/07/Create-an-Admin-panel-with-CodeIgniter
You probably will want to look mostly at "#2" on his list; it's lightweight and not much additional work.
The CMS is part of the site, if by CMS you mean administration panel / backend of your application, you can use the above link provided by coreylink as it details different ways to create an admin panel.
My personal preference is to create a folder called 'admin' in my controllers directory and create semantically meaningful names so my urls are webapp.com/admin/users and so on.