Visual

Latest blog post

This post contains 10 things (in random order) that I would advise to check before the site can go live.

1. Update your websites metadata

Often harder than it looks but should definitely not be forgotten.


Metadata settings #1

Metadata settings #2

2. Check cache settings and enable output caching

Both the performance output caching settings (enabled by default) and document settings must be enabled to use output cache.


Enable output caching

3. Enable document versioning

Either with or without workflow...


Enable workflow

4. Double check the registered users and review their permissions

Ensure that all the users have passwords specified and remove the (unwanted) users that were created based on templates. Also update the global administrators account that has been installed by default.


Double check users

5. Personalize the user interface of the CMS

Hide unnused features via UI personalization:


Apply UI Personalization

6. Update the admin and no-reply e-mail addresses

Easily update all the e-mail address settings via the following query:

-- Update all no reply emailaddresses
DECLARE @noreply nvarchar(100)
SET @noreply = 'noreply@domain.com'

UPDATE 
    [CMS_SettingsKey]
SET 
    [KeyValue] = @noreply
WHERE 
    [KeyValue] = 'no-reply@localhost.local'

-- Update all admin emailaddresses
DECLARE @admin nvarchar(100)
SET @admin = 'admin@domain.com'

UPDATE 
    [CMS_SettingsKey]
SET 
    [KeyValue] = @admin
WHERE 
    [KeyValue] = 'admin@localhost.local'

7. Review the URLs and search engine optimization (SEO) settings

  • Enable "Remember original URLs when moving documents". This setting specifies if a new document alias should be created if the document URL or alias path is updated or when the document is moved.
  • Enable "allow permenant (301) redirection". This ensures the use of 301 redirects instead of standard 302 redirection.
  • Enable "Redirect document aliases to main URL". This ensures unique content per URL throughout the website.

Note: some of these settings might need to be disabled based on your websites setup.
 

8. Create a custom 404 error page

Download, install and configure the Page Not Found Kit from the Kentico Marketplace and specify the URL in the "Page not found" settings:

Page not found settings
 

9. Disable debugging

You can easily globally disable debugging via the "Disable debugging" setting.

disable_debugging.png
 

10. Keep an eye out for errors

Check the event log from time to time and try to fix the errors.

Event log


Community

comments powered by Disqus

Search

Work

IBL-Software

Related posts

Tips and Tricks: Building Highly Scalable Websites

15 tips for optimizing your websites performance A couple of weeks ago, at the Kentico Connection 2011 in Prague, I... read more

Tips and Tricks: Debugging access denied permissions

When working with users and roles in Kentico CMS it is sometimes tricky to find the needed UI permissions. This post will... read more

Tips and Tricks: Macros in Widgets

Here is a quick tip that is useful if you work a lot with widgets in Kentico. You might know that macros are not... read more

Tips and Tricks: URLs and case letters

Did you ever look for a way to transforms all URLs to a specific case? Kentico provides it’s users this functionality... read more

Tips and Tricks: Hiding content in the content tree

Kentico CMS 6.0 brings you a great new feature that allows you to only display content to your editors if they have the... read more

Featured

Connect & Conquer