I've been developing an static website (just html, css and js files) for a client who now wants to load the site on to Kentico CMS.
I don't know anything about this CMS. Is this a practical way to import the completed code into this system?
Thanks.
I would do things the way Kentico expects.
Take your header/footer and put them into the master page (template).
Take individual template HTML and create Layouts and Templates from them.
Use Kentico Web Part where possible
For dynamic content areas, use the Editable Content Web Part.
For the menu use the CSS Menu Web Part.
Use the Portal Engine technique. Don't use ASPX pages unless you really have to.
Here is some documentation from version 8: https://docs.kentico.com/display/K8/Creating+portal+engine+master+pages.
Related
My Designing team use to generate static HTML pages (html files, css, JS, fonts etc) and use to share zip with us.
We are looking forward to add these pages in Kentico 13 Core.
I have created the custom page type having one field of type File.
Use to upload pre-generated HTML file from Pages app using above created page type.
But it use to attached as attachment and dont use to show contents. It did work with Kentico portal engine but didnt find ant option under Kentico 13 Core.
Please help!!
It's not entirely clear to me what type of behavior you are looking for, but if you are expecting to be able to customize HTML, CSS, and JavaScript in Kentico Xperience or Kentico 12 MVC the way it works in Kentico Portal Engine, that's just not possible.
Using MVC requires either:
Templates be coded ahead of time in Razor .cshtml files
Templates be designed as composable pieces that can be built up as Page Builder components (like Sections, Widgets, Page Templates)
Content Managers then will create Pages in the Content Tree and add their content to those Pages. Those Pages either have Razor Controllers/Views associated with them to render their content (and related content) or use the Page Builder to combine components that display content.
If you want to display Attachments in a Page, you can follow the instructions in the documentation.
If you want Content Managers to be able to upload HTML, CSS, and JavaScript files to be displayed/rendered on the site, you'll need to come up with a custom solution - potentially using Media Libraries and a custom coded solution.
In Kentico Xperience13, when I go in the Page Template application they said we need to use the Page Application to create a page and save it as a Page Template. But when I create a Page I don't see the place where I can save as a Page Template. So when I came back in the Page Template application the list is always empty.
To use Page Templates in Kentico Xperience 13, you either need to create default templates through code - see Developing page templates, or you can save widgets that have been added to a page as a custom page template - see Saving pages as custom page templates
As someone currently working on a site in Xperience 13, you may want to consider taking a class or two on Pluralsight to give you the basics of MVC and .net core. I am new to those but have been using Kentico for over 10 years. This change to MVC has been a bear to learn. But the Pluralsight courses have helped me get a better understanding of the structure.
Kentico does use content based routing as an option (and I think it is default in 13) you can learn more about it here https://docs.xperience.io/developing-websites/implementing-routing#Implementingrouting-Contenttree-basedrouting
when you build page types you don't have to worry about the model and the controller portion, kentico handles it, you just need to build the view.
this tutorial covers the basics https://docs.xperience.io/13tutorial/asp-net-core-development-tutorial
I am using Kentico portal to make an E-commerce site.If I wish to change the design of available sample E-commerce site.Would it be a tidious task ?
Example : If I download e-commerce design templates (i.e html and css files) and I wish to change design of each page of sample kentico site (home page,product detail page etc.)then, what is the most suitable and quick way to achieve this ?
How should I update the html/css of each page of available site with downloaded templates? OR Should I create entirely a new e-commerce site in the portal ?
The out of the box sites are meant to be used as examples and references not to build a production site off of. The markup used on the Ecommerce site will also be different, considerably different than your purchased template. I've found it much easier and faster to start from scratch with a blank site and implement all of the design that way. Make sure you take advantage of shared layouts and templates, this will help make development and re-skins in the future easier.
I've developed with WPS and WCM for several years and now I am also learning Liferay. I can't help but compare the features and I understand that in Liferay some things are done differently.
I would like to know the best practices to manage the following simple example:
A simple page with a carrousel with several images and links
Google analytics inserted in the page (Reusable in most pages)
The following is how I'd solve it in IBM WPS:
A HTML component with the Google Analytics code that is called in every page (I can't find how to do this in Liferay)
A content definition of an image and a link.
Create several contents for each image and link.
Create a menu that shows the list of content in the form of a carrousel (I can't find how to do this either in Liferay)
I am aware that Liferay has a list portlet and content that has repeatable items. I know I could use these, however its much more usable if I can have on content for each image/link and one reusable HTML snippet of code.
How should I solve this in liferay in the most efficient way?
Thanks!
You have to use Liferay Web Content portlet for creating the carousel. This is available in Control Panel. For your particular requirememnt you have to create a dynamic web content, which involves using of Velocity language and javascript to iterate over a set of images. Infact if you see Liferay's website, the home page has this kind of stuff.
For Google Analytics there are two ways. Liferay is not just meant for creating one site, it caters creation of multiple sites. Each site has a group of pages. You can create site from Control panel again. In the site settings you have this option to add google analytics id. So with each site can have different google analytics id.
If you want to do it at a global level, we add the google analytics script snippet in the Theme of liferay.
To get a better understanding of all the jargons used in Liferay, you have to atleast go through Liferay's documentation. And while going through it you have unlearn what you have previously learned. Liferay has hell lot of features than Websphere portal.
http://www.liferay.com/documentation/liferay-portal/6.1/user-guide
I need to provision a custom aspx page which does some work and then redirects to another page. Using a _layouts page, AKA an application page won't work since I only want this page accessible to one site collection.
I looked at using pattern #4 from blog post Application Development on MOSS 2007 and WSS V3. It feels pretty hacky, and it asks you to drop the DLL. Drop it into the bin of the site collection, and upload the file through SP Designer.
I'd rather have this page be a feature that gets included in my site definition or stapled to an existing site definition. I imagine I could use a feature receiver to deploy the files to the pages SP list. One of the comments on the blog post says as much:
Pardon my ignorance on this maybe I am
missing the point completely but
wouldnt it be easier to deploy your
custom pages by programmatically
adding them to the pages splist?
I basically, had a simple .aspx page
with a user control. I deployed it via
this method.
How can a custom page be provisioned without using a _layouts page?
I guess another option is to keep using a _layouts page, but make sure the referrer is correct.
Besides application pages, you also have the possibility to create site pages.
Site pages are in nature related to application pages, but they reside in a site not in _LAYOUTS.
The welcome page (default.aspx) is an example of such a page.
In the same way as with application pages, it is possible to do codebehind in these pages (check out AC's article on this subject, Using ASP.NET 2.0 Code Behind Files in SharePoint v3 Sites)
You can read this article regarding the subtle differences between application pages and site pages: SharePoint Application and Site Pages - Part 1 of 2
You deploy this custom page using a feature, where you specify the file as ghostable (look at the example in ACs article).