More in this section

Forums / Developing with Sitefinity / Best Practices of sitefinity.

Best Practices of sitefinity.

2 posts, 0 answered
  1. Zeeshan fawad
    Zeeshan fawad avatar
    4 posts
    Registered:
    05 Jun 2009
    13 Oct 2009
    Link to this post
    Hi, We have some queries about development in sitefinity.

    1. How can we have production version and test version of a project. Currently we are managing it in dotnet and first apply the addition/changes in test version then copy the additions/changes online.

    2.Can we have a workflow of users working on a project. eg first admin add a page and place content on it, then release it for designer , then designer after designing the page release it for developer etc.

    3.Are there any best practices for designing and development in sitefinity.

    Regards

    Zeeshan Fawad.
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    14 Oct 2009
    Link to this post
    Hi Zeeshan fawad,

    1. How can we have production version and test version of a project. Currently we are managing it in dotnet and first apply the addition/changes in test version then copy the additions/changes online.


    You can use some replication tool and CVS to track the changes between you staging/test and production server.

    2.Can we have a workflow of users working on a project. eg first admin add a page and place content on it, then release it for designer , then designer after designing the page release it for developer etc.

    Standard edition of Sitefinity supports workflow. It is based on roles and it works for Generic Content based modules and pages. You can enable it from your web.config file. Below is sample that illustrates enabling workflow for pages and Blogs module

    <cms defaultProvider="Sitefinity" pageExtension=".aspx" disabled="false" redirectToHomePage="true"
       pageEditorUIMode="Overlay">
       <providers>
        <clear />
        <add connectionStringName="DefaultConnection" allowPageHistory="true"
         allowPageWorkflow="True" cachingProviderName="ASPNET" name="Sitefinity"
         type="Telerik.Cms.Data.DefaultProvider, Telerik.Cms.Data" />
       </providers>
     
     
    .....
     
     
    <add name="Blogs"  allowWorkflow="True" urlRewriteFormat="[Publication_Date]/[Title].aspx" urlDateTimeFormat="yy-MM-dd" urlWhitespaceChar="_" visible="False" defaultMetaField="Title" applicationName="/Blogs" allowVersioning="True" allowComments="true" commentsModeration="false" allowLocalization="True" localizationProviderName="" securityProviderName="" versioningProviderName="" connectionStringName="GenericContentConnection" type="Telerik.Blogs.Data.DefaultBlogProvider, Telerik.Blogs.Data"/>
     
    ....

    3.Are there any best practices for designing and development in sitefinity.

    Sitefinity follows the structure of a standard ASP.NET web application. It is better to develop only generic content based modules and add the loging only in user and custom controls.

    Greetings,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
2 posts, 0 answered