Blogg
Insikter, nyheter och best practices från teamet på Geta Digital.
How to use your landingpage
A Landing page can be described as a page that the visitors arrive on. There are different types of landing pages but I decided to focus on “Click through” landing page. This is a landing page where the focus is mainly on e-commerce, click through pages , which “warms up” the cus…
Content Area - under the Hood, part II
In the first part we looked closer on how templates get discovered and registered in Template Model Repository.
Category selection for multiple sites in EPiServer enterprise solutions
In this example I'm matching the entry category name for each site with the site definition name in EPiServer. Here are the site definitions for this example. Notice the name of the sites:
Content area - under the hood part I
This is a multi-part blog post series about what happens under ContentArea property in EPiServer.
New version of Geta oEmbed
oEmbed is a format for allowing an embedded representation of a URL on third party sites. Basically it allows editors to easily embed content from sites like YouTube, Vimeo, Flickr, Amazon and 300 other providers , by just copy/pasting the URL into their content. The module takes…
Hvorfor sover du så godt om natta?
For noen år siden kjørte jeg et forprosjekt for en kunde. Vi skulle bygge en strategi for dem, analysere konkurransebildet, og gi noen tydelige føringer for hvor de skulle bevege seg videre med internett som - for dem - en ny kanal.
New version of Geta Tags
Look for Geta.Tags version 2 and above (should be available on nuget.episerver.com soon).
Moving from EPiServer CMS to EPiServer Commerce as a Developer
EPiServer CMS has been around since 2001 and now powers 30 000+ web sites worldwide with a development community of 25 000+ developers. EPiServer Commerce was launched in 2010 and has far fewer installations and experienced developers, but that is changing rapidly! Chances are th…
Simple URL keeper for EPiServer
So what we want to do is attach our selves to the MovingContent event, get a hold of the old URL and the content GUID, store that data, and in our custom 404 controller check for it so that we might perform a redirect (otherwise we display our normal 404 page).