Blog

Feydra Frequently Asked Questions

April 13, 2017 | Angel Uzunov

With Feydra, front-end developers can work the way they want, using the tools they prefer and are used to instead of being worried about Sitecore requirements. Feydra also allows them to commit their changes without the help of a back-end developer. Since the product release we've gotten a number of excellent questions from the community, such as:

Q: How do I install it?

A: Feydra is supplied as NuGet packages which contain the 2 DLLs and a configuration file that need to be deployed to the QA or design server (typically QA).

Q: Approximately how long does it take to set up a Feydra environment?

A: About 10 minutes.

Q: How is Feydra different than a headless CMS implementation?

A: Headless CMS strips the front-end away from the content storage and production task. Content is delivered via API instead of as components or fully formed pages. Designers typically use a JavaScript framework for building pages.

Feydra separates the activity of front-end development from back-end, but does not change the standard functionality of Sitecore. It leverages a deep understanding of .NET development to decouple the process, but not the actual application.

Q: What does my team have to do to get a Feydra environment set up?

A: Push 2 DLLs and a configuration file to their chosen environment (usually a QA server) and create a standard file share on the server for the FED to push changes to. Virtually every team already has this environment in place already.

Q: Do I need to set up dedicated CM and CD Sitecore instances for Feydra?

A: Feydra is planned for use on the environment where the actual front-end assets will be used - in a split environment case, this would be the CD instance.

Q: Should the initial setup/deployment of Feydra be done on CM and CD Sitecore instance?

A: The initial setup, in a split-environment case, should be done on the CD instance. If your internal Feydra box (or QA, or whatever internal machine they're using) has both CM and CD, in which case you’d probably want it on both so that your front-end developers could see their changes on both. Generally, Feydra is only needed on lower tier environments like Dev Integration and QA. Feydra should not be installed on Production instances.

Q: Is web-app supported by Feydra?

A: Azure Web Apps are supported by Feydra with a small exception - for now Feydra doesn't have enough access to create the initial user folders under the FeydraRoot folder inside the website root, so these initial folders need to be created in advance (for example by having a build step create them).

We've answered more Feydra questions on our Feydra Q&A or skip right to the best part and download Feydra to start virtualizing!

Feydra development

Related Blog Posts

TDS Classic How-To: Disable Automatic Code Generation
Code Generation is automatically triggered after every change in the TDS Project tree. If a project contains many items, users can disable this feature for their convenience.
TDS Classic Sitecore Deploy Folder
Sitecore Deploy Folder is a setting, located in the build tab of the TDS Classic Project's Properties page, and used to tell TDS Classic where the webroot is located.<br>
TDS Classic Builds on Jenkins Build Server with NuGet Packages
Our simple scenario includes 2 developers using TDS Classic and checking-in changes to source control. The Jenkins build server takes the changes and performs the build, and then deploys the created package to two Sitecore environments.
Features to Improve Sitecore Development: TDS Classic Strikes Back
Each and every feature in TDS Classic is aimed at helping developers. Whether the feature is out front or running quietly in the background the goal is always the same: make the development experience better. &nbsp;&nbsp;
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;
TDS Classic Features to Improve Sitecore Development
Each version of TDS Classic comes with the same goal: to make Sitecore development and, by extension, developers, lives easier. Every feature in our products is aimed at making the process better - some of these features aren't quite as well-known as others, but they all help smooth and improve the development experience.
Deployment Properties and the Deployment Property Manager
When working with TDS Classic, you will eventually need to deploy your items to a Sitecore instance and you might not want the default behavior of every item in your TDS project deploying every time. This is where the TDS Sitecore Deployment Property Manager comes in!
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.
TDS Classic 5.6 Feature Spotlight - Prevent Deployment of Incorrect Assemblies
This feature, new to TDS Classic 5.6, will prevent a solution from deploying unless all assemblies (except the excluded assemblies we allow you to specify) match what exists in your webroot.&nbsp;
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;
TDS: The Evolution of Auto-Sync
Auto-Sync has been described as a new feature, but in reality has existed in TDS since 2010 and has taken a new form in TDS 5.5, due to be released March 22, 2016
Team Development for Sitecore Webinar
Our Sitecore MVPs Charlie and Sean recently did a demo of TDS to all Sitecore partners. We recorded the demo to share with the world.