Blog

Back to blog
How Feydra can keep you in your comfort zone

November 15, 2018 | Kliment Klimentov

Setting up a Sitecore instance for local testing can be not only difficult, but also time-consuming. Dealing with extremely large databases or RAM requirements, setting up additional modules and servers, and taking in mind Sitecore license terms can be only part of the difficulties each one of your front-end developers might have to face when starting a new project. Not only that, because of Sitecore's OS requirements, Front-End Developers (FEDs) might be forced to use an Operating System like Linux or MacOS and/or tools that take them outside of their comfort zone. 

  

Feydra reduces the time and effort of adding a new FED to the project to just installing a NuGet package and providing a network share. Feydra eliminates the need to install а test Sitecore instance for each of the front-end developers and provides a safe working environment, where FEDs can test their front-end assets without interfering with the work of Back-End Developers (BEDs) and possibly overloading their PC.  

  

Often FEDs must wait for a build or trigger one, then wait for app pool recycle so they can see their changes applied to the Sitecore instance (a QA instance for example). What if the changes break the website? With Feydra, FEDs can see their changes straight away without passing over their assets to BEDs.  

  

Bottom Line: Feydra provides the flexibility to use all the tools a FED would use in their normal work on a local static site but see the changes on a Sitecore site.  

  

Take Feydra for a test drive for 30 days and see what we mean.  

Feydra Front end back end

Share
Tags

4.0 acquisition avtor azure back end best of tds 2015 best practices builds bulgaria charlie turano code generation code connection content editor content management continuous integration datasources development delta deploy deployment feature features feydra front end front-end guest post habitat hedgehog helix how to live chat jenkins jenkins build kliment klimentov launch sitecore miscellaneous mvc mvc rendering nuget package placeholders post deploy step press release preview rainbow razl schackathon razl 4 razl 4.0 sean holmesby security sitecore development seo sitecore sitecore rocks sitecore roles sitecore 9.2 tds classic 5.8 sitecore user group tds classic best practices tds validators sugcon technology sugcon anz sugcon eu tfs sxa tom kamin sync tds tds 5.0 una verhoeven tds 5.6 tds 5.8 tds classic tds classic 5.6 tds classic 5.7 wellness vibert trahan wffm visual studio visual studio online yaml webinar

Related Blog Posts
Edit Front-End Assets with Feydra
Feydra is the answer to a common question: How can front-end developers start working quickly on Sitecore assets like CSS and JS files without having to install and run the entire Sitecore project?<br> <div>&nbsp;</div>
How Feydra Improves Front-End Development for Sitecore
Feydra offers a more efficient modern approach to front-end development workflow for Sitecore.
Feydra and the Virtual Sandbox
Feydra virtualizes all front end assets (css, js &amp; cshtml) of a Sitecore instance. With Feydra, front-end developers can commit their changes to Source Control without requiring the intervention of a back-end developer. We call it a virtual sandbox.&nbsp;
Feydra Frequently Asked Questions
Answering a number of excellent questions we've gotten from the community regarding Feydra, including how long it takes to set up a Feydra environment and how to install the product.&nbsp;
Feydra: A Front-End Assessment
Feydra allowed me to start building the front-end in a very short time with no Sitecore experience, and it let me use tools that I was comfortable and familiar with.
Feydra: A Quick Start Guide
A step-by-step guide for installing, configuring and, most importantly, using Feydra from the front-end.
Feydra from the Front-End
Feydra eliminates common roadblocks for designers and front-end developers working on Sitecore projects by getting them up and running more quickly and allowing them to use the development environment and workflow tools they prefer.&nbsp;