Tutorial - Developing websites with Kentico 8. .. Provides links to relevant pages in the main Kentico documentation. (based on the current. If you are new to Kentico, start with our short tutorial. Learn the basics of website development in Kentico with the Getting started tutorial. at cehalfperbfamsce.gq or in a separate installer). • Kentico CMS Tutorial - a detailed tutorial showing how to build a website step-by- .

    Language:English, Spanish, Indonesian
    Published (Last):20.09.2016
    Distribution:Free* [*Registration Required]
    Uploaded by: ELLSWORTH

    69359 downloads 101345 Views 38.56MB PDF Size Report

    Kentico Tutorial Pdf

    If you are new to Kentico, start with our short tutorial. Learn the basics of website development and content editing in Kentico with the Getting started tutorial. Kentico CMS User's Guide. 1 cehalfperbfamsce.gq In the Workflow tutorial, we assume that your website has been configured for workflow. For more. Required experience. Although Kentico CMS allows you to create dynamic websites without programming, you need to .. The rest of this tutorial explains the portal engine approach. If you want to use PDF, DOC or XLS documents.

    Local installation Check if your development server meets the recommended configuration. Install Kentico on your local computer with your own preferred settings using the Custom installation button. Remote installation Check if your development server meets the recommended configuration. Develop your website on a remote server or set up a production environment. You will find detailed procedures for this type of installation in the Deploying Kentico to a live server section.

    You can click the Upload file link and select an image from your local disk. You may also leave the field blank, which assigns the default avatar to the department. Used stylesheet - theme used for the department's section. You may use one of the three predefined stylesheets, or even edit the selected one directly using the Edit button. Used department sections - using these check-boxes, you can choose which sub-sections will be included in the department's website section.

    Department roles - roles of department members. Members of the roles selected in this field will have access to the department's website section see the Departments security topic for more details.

    Publish from - date and time from when the department will be published on the live site. If you leave the field blank, it will be published immediately after its creation.

    Publish to - date and time until when the department will be published on the live site. If you leave the field blank, it will be published until it is deleted.

    For sample values that can be entered in the fields, please see the pre-defined sample departments or refer to the Adding new departments topic. The first step in creation of a department is creation of roles that the members of the department will belong to.

    Subscribe to RSS

    This is necessary in order to control access to the department's section, as described in the Departments security topic. Role code name: SupportEngineer; name of the role used in website code. Role description: enter some text describing the role. Is domain role: disabled; indicates if the role is a domain role from Active Directory.

    Click OK. Repeat the procedure and create another role using the following details: Role display name: Customer Care Manager Role code name: CustomerCareManager Role description: enter some text describing the role. Is domain role: disabled Click OK. With the roles defined, you may proceed with creating the actual department section in the content tree. Click the New button above the tree. In the New document dialog which gets displayed, select the type.

    Intranet department document 5. On the department creation form, you need to specify the following details. For detailed descriptions of particular fields, please refer to the Departments overview topic.

    Department name: Customer Care Department description: enter some text describing the department. Department avatar: for the purpose of this example, you may leave the field blank, which assigns the default avatar to the department. Otherwise, you may click the Upload file link and select an image from your local disk. Used stylesheet: Intranet Portal - Blue Used department sections - enable all available check -boxes Department roles: add the Customer Care Manager and Support Engineers roles created in step 2.

    Publish from: leave the field blank. Publish to: leave the field blank.

    Finally, click Save to create the department with the entered details. You should see it in the content tree, under the Departments node. If you expand the Customer Care node, you should see that all pages from under the Template document were copied under it, as depicted in the screenshot below.

    The last thing you need to do is configure permissions for access to the new department. This only enables them to view the content of the department. As we want the Customer Care Manager role members to manage the content in all possible ways, let's give them the Full control permission.

    Finally, click OK to save the configuration. Let's see what we have created. If you go to the live site and browse to the title page of the Departments section, you should see the department present in the All departments list.

    Click the department's name or avatar. You will be redirected to the Home page of the department's dedicated website section. As you can see in the following screenshot, the page already contains all web parts that are present on other departments' Home pages, but they have no content yet. In a real-world scenario, the next logical step would be to assign ordinary members of the department to the Support Engineer role and the department's management to the Customer Care Manager role.

    The rest of the department's section is pre-configured and ready to be used.

    Once the department starts being used by its members, web parts on this page will get populated with content from the respective sub-section of the department automatically. These objects are necessary to provide object-based functionality of the department's section. The following text describes which objects are created and what display name and code name they are created with. In the code names, the globally unique identifier GUID of the particular department's parent document is always used.

    The forum group contains a single forum, which is also created automatically. Otherwise, content of the forum would not be indexed by the department's forum smart search index see below for more details. In addition, if you choose that the new department should contain the Forums section in step 5 of the example above , another search index gets created for the department's forums. This tag group is intended for tagging of blog posts in the department's Blogs subsection, but it is created even if you choose not to include the Blogs sub-section in the department in step 5 of the example above.

    This can be done at three levels: Page templates customization - useful to customize pages on the Design tab. Individual department customization - useful if you want to add or remove sub-sections of a single, already existing department.

    Customization of the department template - useful if you want all newly created departments to reflect certain customization. In a real-world scenario where you already have some departments created, it is expected that you will have to combine these approaches to achieve the expected result. The following examples will guide you through the process of performing these types of customization. These examples are intentionally simple, but the principles shown in them are applicable for all customizations you would possibly want to perform.

    Reordering and renaming default department sub-pages Configuration of most of the web parts and widgets used within the department sections, as well as other configuration, is dependent on alias paths of particular department sub-pages. Therefore, it is not recommended to change the default alias paths.

    Page templates customization Documents of particular department sub-sections share common page templates. For example, the Home pages of all pre-defined departments, as well as the one under the Template node, share the Intranet Portal - Department home page page template.

    This fact implies that if you customize one Home page on the Design tab e. To prevent this behavior, i. The following example demonstrates both of these approaches: 1. At first, we will try modifying one page so that all pages that share the same page template will reflect this customization as well.

    We will customize the page by adding one extra web part to the zonecentertop web part zone. Click the Add web part icon in the top right corner of the web part zone. Leave all other properties at their defaults and click OK. The web part will be added to the page template, as can be seen in the following screenshot. Finance, you will see that the web part is present there as well. The same applies to the Home page under the Template node.

    Kentico 8 Tutorial

    Let's try the other approach. Now that all Home pages contain the added web part, we can try removing it from just one of these pages, while keeping it in the rest of them. The page template will be cloned as an ad-hoc one, which will be recognizable by its name changing to Ad-hoc: Home. Now you can modify the page without affecting the other Home pages. For example, if you remove the Powered by Kentico web part added in step 3, it will only be removed from this Home page, not from all the other ones.

    This customization will then be reflected only in this particular department's website section. In the following example, you will learn how to add a sample FAQ page to the IT department's section: 1. When the New document dialog appears, select the Page menu item document type.

    In the following dialog, enter FAQ into the Page name field and choose the Create a blank page option in a real-world scenario, you may also use one of the pre-defined page templates according to your needs. Finally, click Save to save the changes.

    The new page is added as the first page under the department's main document before the Home page. The position of the page in the content tree determines the position of the page in department navigation. As you will probably want the page to be located a bit more to the right in the navigation, drag and drop the page to the desired position in the content tree. For the purposes of this example, we will only add a single Editable text web part with all its properties left at the defaults.

    Now go to the Page tab of the page's editing interface and add the actual content of the page. For the purposes of this example, you can just add some sample text as in the screenshot below. Click Save to save the changes.

    Once you are finished, go to the live site to see what you have created. Browse to the IT department's website section.

    You should see the FAQ menu item present in the main navigation, at the position where you dragged it in step 3. If you click the document, you should see the page with the content defined in the previous step.

    These pages are copied under each newly created department's parent document. By performing customization of the documents under the Template document, you ensure that each newly created department will reflect this customization too. However, this will not be the case for already existing departments. To ensure uniformity in this case, you will need to copy the new page under the existing departments manually. Go through steps 1.

    At this point, the page is created with an ad-hoc page template. To ensure uniformity with all other department sub-pages, i. Now try creating a new department, just as described in the Adding new departments topic.

    Once the new department is created, you can see that it contains the FAQ page as well. The result is a fully functional corporate website as shown below. I tested the layout and some functionality on the latest browsers IE, Firefox, Chrome and there were no issues. So Far So Good! A simple GUI, with the ability to create new content as well as manage existing content with ease and without requiring much technical knowledge, is what I would desire.

    You can even paste text from a Word document and the editor automatically detects this and formats it for you. I find this very useful as I am a frequent user of MSWord. Flexible Content model, Template Engine and Easy File Management For webmasters who do not have programming abilities, a CMS should ease the process of site creation whereas for developers, it should provide a template based model that can be customized as needed.

    The powerful template engine enables you to create Page templates and reuse them as many times you want. Since it is based on the ASP.

    NET platform, it supports master pages. It also allows you create your own document type with meta data support. The File management module lets you batch import a directory and manage site assets like the media libraries, graphic files etc.

    The inbuilt Image Editor supports all basic features like Image resize, rotate, convert, trim etc. I could not find a Multi-file uploader nor found the support for dragging and dropping files from the desktop to the uploader. I think it would be a nice-to-have feature. Workflow Management with Versioning and Process compliance A Workflow is important to enterprises and the Kentico CMS allows you to customize workflows and define your processes.

    You can notify owners when new documents arrive for approval and also let them edit documents with an exclusive lock.

    You even have the ability to compare document versions as part of the workflow process.

    Kentico 8 Tutorial | Websites | Page Layout

    This allows content approvers to review documents and see what changes were made. Security Security is one feature I am very particular about. A CMS should provide out-of-box security as well as give the owners, the flexibility to fully customize the authentication system to suit their needs.

    NET security features. Windows domain and Active Directory import facility. Authorization - Granular level of permissions possible for documents and modules, with the ability to create secured site sections and content.

    Membership — Easy to use Membership features with customizable user fields. Additional support for Double-opt-in registration, mass mails, avatars, site badges and much more. Customization — You can customize the authentication system to use any authentication service. Scalability and Availability Although I could not test the scalability of Kentico CMS, I believe it is optimized to work with 1,, users and , documents in the database, with native support for web farms.

    Since it is built using ASP.

    NET, you can use the caching techniques you are familiar with, to improve site performance. NET 3. If the application uses. You can use your favorite hosting provider or choose from our hosting partners. You should beable to create a simple application in ASP. Choose the installation location of the binaryfiles and documentation on your disk. First, you need to choose the version of.

    Click Next.


    Copyright © 2019 cehalfperbfamsce.gq. All rights reserved.