archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Windows 8.1 live tile available for mavention.com and mavention.nl - Blog - Mavention
    to your Start screen depending on the size you will choose for the tile you will see either the latest or the latest three articles published on the website Tapping the tile will take you directly to the website when you will be able to read the content in the full experience Building live tiles for your website Building Windows 8 1 live tiles for websites isn t complex and while it could be done manually it s easier to go to http www buildmypinnedsite com en and follow the wizard there In a matter of minutes you will be provided with the necessary assets and manual to integrate the live tile with your website From SharePoint perspective the easiest way to integrate the live tile with your website is to upload the generated assets file to the root of your website using SharePoint Designer Summary One of the improvements of Windows 8 1 are live tiles for websites When pinning websites to Start you can control how the tile will look like and which information should be displayed This allows you to bring the information from your website closer to your visitors With the latest update a Windows 8

    Original URL path: http://www.mavention.nl/blog/windows-8-1-live-tile-mavention-com-mavention-nl (2016-02-18)
    Open archived version from archive


  • Case Study: Mavention and Web Content Management in SharePoint 2013 - Nieuws - Mavention
    content management mogelijkheden die de nieuwe SharePoint versie biedt zoals De opbouw van navigatiestructuur op basis van taxonomie Ondersteuning voor verschillende look feel per devices Verbeterde ondersteuning meertalige websites Verbeterde ondersteuning voor search engine optimalisation SEO Content targeting en het plaatsen van recommendations om bezoekers langer te binden op de website Microsoft heeft de Mavention website als case studie opgenomen op haar internationale casestudies website Deze case studie is hier

    Original URL path: http://www.mavention.nl/nieuws/case-study-mavention-wcm-sharepoint-2013 (2016-02-18)
    Open archived version from archive

  • Nieuwe website Mavention showcase voor SharePoint 2013 - Nieuws - Mavention
    verbeteringen De zoekfunctionaliteit is doorontwikkeld en nu gebaseerd op FAST search De social features zijn uitgebreid zoals microblogging en communitysites Integratie met de cloud door bijvoorbeeld workflows via het Azure platform uit te voeren Daarnaast ondersteunt Microsoft Apps voor de zakelijke markt via een SharePoint marketplace Ook voor het ontwikkelen van websites met SharePoint is veel verbeterd Showcase Mavention ontwikkelt haar nieuwe website met SharePoint 2013 De nieuwe website wordt een wereldwijde showcase voor het ontwikkelen van websites met SharePoint 2013 Mavention toont nieuwe functionaliteit zoals Het aanbieden van content op basis van zoekresultaten De opbouw van navigatiestructuur op basis van taxonomie Ondersteuning voor verschillende look feel per devices Verbeterde ondersteuning meertalige websites Verbeterde ondersteuning voor search engine optimalisation SEO Daarnaast past Mavention responsive web design toe op de nieuwe website Dit zorgt er voor dat het formaat van de nieuwe website automatisch meeschaalt met de resolutie van het medium waarmee de site bezocht wordt Of het nu gaat om een desktop tablet of mobiele telefoon De nieuwe design gebaseerd op de metro look feel leent zich goed voor touch bediening Meer informatie over het ontwikkelen van websites met SharePoint 2013 Neem dan contact op met Joris Engels Samenwerken en

    Original URL path: http://www.mavention.nl/nieuws/nieuwe-website-mavention-showcase-sharepoint-2013 (2016-02-18)
    Open archived version from archive

  • Optimizing performance of Sitecore websites with the Mavention Bundles module - Blog - Mavention
    is already a part of your project and it is not much of a problem to extend it with bundles definition In Sitecore however the Global asax file points to a Sitecore implementation of the HttpApplication class of which you obviously don t own the code And while you could work around that Sitecore offers another approach for registering bundles Registering bundles in Sitecore Sitecore is a highly extensible platform that uses its pipelines infrastructure to customize and control how Sitecore is working Custom pipeline components can be used for many different purposes including registering bundles Following is a sample code of how you could register bundles with Sitecore public class RegisterBundles UsedImplicitly public virtual void Process PipelineArgs args RegisterBundles BundleTable Bundles private void RegisterBundles BundleCollection bundles bundles Add new ScriptBundle bundles js Include assets js jquery js assets js custom js bundles Add new StyleBundle bundles css Include assets css bootstrap css assets css custom css Registering bundles with Sitecore using a custom pipeline isn t complex but the question is whether you want to repeat this code for every single project that you will be working on and maintaining it separately What if you could separate the code from the bundles definitions and write the code once and merely reference it in all your projects Better registering bundles in Sitecore with the Mavention Bundles module Mavention Bundles is a Sitecore module that allows you to register bundles using the Sitecore patching facilities The module registers a custom pipeline component that during the initialization of your Sitecore website scans the configuration files for bundles definitions and registers them with the ASP NET MVC runtime After installing the module the only thing left for you to do is to create an include file with the bundles definition for your website Following is a sample include file based on the LaunchSitecore website configuration xmlns patch http www sitecore net xmlconfig sitecore maventionBundles enableOptimizations true enableOptimizations bundles hint list bundle hint 1 type Mavention Sitecore Bundles SiteBundle Mavention Sitecore Bundles bundlePath bundles js bundlePath bundleType Script bundleType files hint list file hint 1 assets js bootstrap min js file file hint 2 assets js custom js file files bundle bundle hint 2 type Mavention Sitecore Bundles SiteBundle Mavention Sitecore Bundles bundlePath bundles css bundlePath bundleType Style bundleType files hint list file hint 1 assets css bootstrap css file file hint 2 assets css font awesome css file file hint 3 assets css font awesome ie7 css file file hint 4 assets css custom base css file file hint 5 assets css custom nav css file file hint 6 assets css custom modules css file file hint 7 assets css custom mvc css file files bundle bundles maventionBundles sitecore configuration Then in your layouts you would simplify refer to these bundles link href bundles css rel stylesheet script src bundles js script You can define as many bundles as you need Using the enableOptimizations element you can control whether bundles should be built

    Original URL path: http://www.mavention.nl/blog/optimizing-performance-sitecore-websites-mavention-bundles-module (2016-02-18)
    Open archived version from archive

  • Inconvenient languages and formatting dates in multilingual sites in Sitecore - Blog - Mavention
    about the different ways to make things consistent here are a different options at your disposal Renaming en to en US Renaming the standard en language to en US is easily done It leads however to a broken content management experience after all all system items have been created in en rather than en US One approach to fix this would be to either hack the database and replace all references to en with en US or create en US versions for all system items As you can imagine either approach is far from desirable Creating nl rather than nl NL for custom languages When adding a new language you might consider adding it without including the country region information also refered to as a neutral culture ie nl instead of nl NL for Dutch While this gives you a consistent experience at first it has a serious consequence which you might not notice until it s too late If you use a neutral culture for your language Sitecore will not format your dates If somewhere in your rendering you would want to render a date field using the Html Sitecore Field Date new format d helper you would see the date formatted using the en US locale rather than your language It turns out that the DateRenderer class responsible for rendering values of date fields checks if the current culture is neutral or not and uses it for formatting only if it s not What to do instead It s clear that you both need to keep the standard en language as well as create all additional languages including the country region code if you care for correct formatting dates If you have only one country region code per language you could consider building a custom Link Provider and

    Original URL path: http://www.mavention.nl/blog/inconvenient-languages-formatting-dates-multilingual-sites-sitecore (2016-02-18)
    Open archived version from archive

  • Search engine optimization of multilingual URLs of bucketed items in Sitecore - Blog - Mavention
    patch http www sitecore net xmlconfig sitecore linkManager providers add name sitecore patch attribute name type Mavention Sitecore Publishing Providers BucketItemLinkProvider Mavention Sitecore Publishing patch attribute add providers linkManager sitecore configuration Although building a custom Link Provider and Item Resolver requires some custom development and knowledge of Sitecore it s not overly complex Things get slightly more complicated however when you are building URLs using Display Name on your website Building URLs using Display Name By default Sitecore builds items URLs using the item s Name By changing the settings of the Link Manager in web config you can however choose to use the item s Display Name instead One reason why you might want to do this is to support localized URLs for multilingual items Where item s Name is shared across the different languages its Display Name can be translated offering additional search engine optimization benefits in result While no additional effort is required to have Sitecore use item s Display Name for building its URL there are some additional considerations when building custom Item Resolver for bucketed items Resolving bucketed items using simplified URLs based on item s Display Name When working with multilingual websites it s very likely that not only URLs of bucketed items will be localized but URLs of item buckets as well When resolving bucketed items using their localized simplified URLs the first step is therefore to retrieve the item bucket public class BucketItemResolver HttpRequestProcessor public override void Process HttpRequestArgs args if Context Item null string requestUrl args LocalPath int pos requestUrl LastIndexOf if pos 0 string bucketPath requestUrl Substring 0 pos bool useDisplayName LinkManager GetDefaultUrlOptions UseDisplayName Item bucketItem null if useDisplayName bucketItem GetBucketItemUsingDisplayName bucketPath args else string bucketFullPath args Url ItemPath Substring 0 args Url ItemPath LastIndexOf bucketItem args GetItem bucketFullPath private static Item GetBucketItemUsingDisplayName string itemPath HttpRequestArgs args Item item null using new SecurityDisabler SiteContext site Context Site if site null Item startItem ItemManager GetItem site RootPath site StartItem Language Current SC Data Version Latest Context Database SecurityCheck Disable if startItem null ContentItemPathResolver pathResolver new ContentItemPathResolver item pathResolver ResolveItem itemPath startItem if item null return null return args ApplySecurity item First from the URL we remove the page s slug to get the URL of the item bucket Based on that URL we then retrieve the item bucket Since the HttpRequestArgs GetItem method doesn t support retrieving items using their Display Name we have to resort to a custom method which first retrieves the start item of the site and uses it to get the item bucket using its URL Once we have retrieved the item bucket the next step is to retrieve the requested bucketed item using its slug if bucketItem null BucketManager IsBucket bucketItem string slug requestUrl Substring pos 1 using IProviderSearchContext searchContext ContentSearchManager GetIndex SitecoreIndexableItem bucketItem CreateSearchContext SearchResultItem result null if useDisplayName result searchContext GetQueryable SearchResultItem Where x x displayname slug FirstOrDefault else result searchContext GetQueryable SearchResultItem Where x x Name slug FirstOrDefault if result null Context Item

    Original URL path: http://www.mavention.nl/blog/search-engine-optimization-multilingual-urls-bucketed-items-sitecore (2016-02-18)
    Open archived version from archive

  • Inconvenient XHTML validation in Sitecore 8 XP - Blog - Mavention
    you can imagine this behavior is far from desirable on the web To avoid it in most cases websites using XHTML were served as HTML documents rather than XHTML omitting the strict XML grammar rules and missing the whole point of using XHTML HTML5 The XHTML standard has been originally published in 2000 and many things have changed on the web since then As the web evolved and new demands emerged the HTML5 standard has been published HTML5 not only added new capabilities to HTML but also changed the main philosophy behind HTML Rather than using the strict XML grammar as XHTML did HTML5 allows developers to decide for themselves whether they want to have their HTML XML compliant or not Either way HTML5 documents are not served as XML and minor errors in the grammar are forgiven without the visitors even noticing them HTML5 allows for greater flexibility on the web but also to an issue in Sitecore 8 XP Inconvenient HTML5 in Sitecore 8 XP Consider the following webpage doctype html html head title Html Sitecore Field Title title head body p Hello world p body html It s a perfectly valid HTML5 document If you would however implement this HTML as a layout in Sitecore and would try to approve an item for publishing all you would see was the following error As mentioned earlier the Full Page Xhtml validator is by default a part of the publishing workflow and executes every time you approve an item for publishing As a result you have to ensure that your HTML5 website is XHTML compliant in order to use the publishing workflow or you won t be able to publish any item Disabling XHTML validation The good news is that Sitecore is a highly customizable platform and nearly everything

    Original URL path: http://www.mavention.nl/blog/inconvenient-xhtml-validation-sitecore (2016-02-18)
    Open archived version from archive

  • Optimizing Sitecore 8 XP for Internet search engines with canonical URLs - Blog - Mavention
    to take into account if you want to truly leverage Sitecore s capabilities Multilingual and canonical URLs Sitecore supports a number of different ways for building multilingual websites Depending on your requirements you might for example choose to associate different top level domains with each language or have them published as a path ie en nl Sitecore takes your configuration into account and automatically includes it in the URL If you want to control how your canonical URLs are built yourself you might want to specify it explicitly in the URL options passed to the GetItemUrl method For example by setting the UrlOptions LanguageEmbedding property to Never you would instruct Sitecore never to include the language as a part of the URL Sitecore Links UrlOptions urlOptions Sitecore Links LinkManager GetDefaultUrlOptions urlOptions AlwaysIncludeServerUrl true urlOptions LanguageEmbedding Sitecore Links LanguageEmbedding Never Sitecore Links LinkManager GetItemUrl Sitecore Context Item urlOptions URL aliases and canonical URLs One of the web content management capabilities provided with Sitecore 8 XP is the ability to specify URL aliases for items Using aliases you can have multiple URLs associated with the same item The important part here is that aliases are not redirects the whole page is accessible through the alias and the alias remains visible as the URL of the page Although it might be desirable to use this capability for some scenarios it results in making the same content available via multiple URLs and fragmenting your page s ranking in Internet search results The good news is that if you are rendering canonical URL using the code snippet above Sitecore will automatically revert to the original URL of the item rather than the alias used to view it With that there is no additional effort to properly deal with aliases from the SEO point of view Inconvenient item clones and canonical URLs Another web content management capability available with Sitecore 8 XP is the ability to clone items Cloning items is similar to duplicating with the slight difference that there is a one way relationship between the source and its clones Changing the content of the source item can easily be pushed to its clones making it very easy for you to reuse content in your website Comparing to aliases clones are different as cloning creates a new item in the content hierarchy Ideally assuming that the majority of the content of the cloned item is the same as its source s you would want to render the canonical URL pointing to the URL of the source item when viewing cloned pages Before publishing an item and its clones it s easy to determine whether an item is a clone or not If an item is a clone the item from which it has been cloned can be retrieved through the Sitecore Context Item Source property Unfortunately when retrieving this property for the published item its value is empty One workaround around this limitation would be to create a new field in your Data template and

    Original URL path: http://www.mavention.nl/blog/optimizing-sitecore-internet-search-engines-canonical-urls (2016-02-18)
    Open archived version from archive



  •