How Feydra Improves Front-End Development for Sitecore

July 16, 2018 | Andrew Karaptis

Without Feydra, it is tricky for a front-end developer to work on a Sitecore project. The main roadblock is this - each developer, ideally, wants to install and run a copy of the project so they can integrate and test their work. Under ordinary circumstances, a few factors make this difficult:

1. Some front-end developers have no experience with Sitecore. Sitecore takes the path of heavy install and heavy configuration in return for delivering a robust feature set. This makes its installation and maintenance a process that requires specialized dev knowledge and experience.

2. Sitecore runs on a Microsoft tech stack including .Net framework, IIS and MSSQL. Most front-end developers don’t run these prerequisites on their local development computers, which are sometimes Linux or OSX machines.

3. Many Sitecore projects manage their vital item configuration through separate tools like TDS Classic (Team Development for Sitecore), which adds an extra prerequisite and chunk of workflow knowledge just to keep the project synced with the latest server-side development progress.

The main benefit of using Feydra is that the front-end developer no longer has to install or run the Sitecore project locally. Instead the front-end developer can write their front-end code on their own computer; Feydra allows them to upload it continuously to an integration server (set up by the Sitecore developers) where they can see their changes in action. This allows front-end development to spin up quickly and with much lighter overhead on Sitecore projects. The workflow is as follows:

1. Sitecore developers set up a Feydra integration server and create Feydra accounts on it for each front-end dev.

2. Front-end developers view and test work right on that integration website, so they never have to run the entire project themselves.

3. Front-end developers pull code from the main source control repo, make changes in front-end assets there, upload those assets to a special Feydra override folder on the integration server, and can see their work in action.

4. Front-end developers commit their completed code with confidence that it’s been fully tested in a real Sitecore instance alongside the latest dynamic content, configuration, and server-side development progress.

There are a few other ways to handle this same problem, such as downloading static copies of staging or production Sitecore HTML, working on it locally, hoping you’re still working on the latest relevant HTML output, and pushing those code changes to a source control repo without ever having tested them inside a live working Sitecore site with real dynamic content. This technique comes with many risky pitfalls and more revision churn in our experience. SXA toolkit for Sitecore comes with its own unique front-end workflow where static assets and HTML are exported/imported back and forth between Sitecore and the front-end developers. This seeks to solve the same problem as Feydra, but in a different way. So Feydra is currently for non-SXA Sitecore projects.

Feydra offers a more efficient modern approach to front-end development workflow for Sitecore. Contact us now for more information about how Feydra can help your front-end team.

Feydra Sitecore

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>
Guide to Sitecore Packaging
Development of features and components requires a set of Sitecore items to be packaged - things like renderings and templates. With TDS Classic, Sitecore developers can automate the packaging process.&nbsp;
TDS Classic: Content File Sync
Content File Sync is a fantastic time saver for any Sitecore developer.
Azure Sitecore Deployment: Deploying to a Slot
Setting up Azure staging slots, so the next release of our project can be placed there, allows us to deploy the new code to a private website (the slot), and test it before pushing it live. We are going to script this process to make it easier for the devops team to automate.
TDS Classic Best Practices: NuGet Build Components and TDS Classic .user configs
There are certain systems and processes that you can put in place to make a TDS Classic project run more smoothly. We're highlighting the best practices that our team recommends for getting the most out of TDS Classic.
Azure Sitecore Deployment: Adding Project's Code and Items to the Azure Deployment
Modify the scripts so that the compiled LaunchSitecore site is also provisioned into the new XP environment.
TDS Classic Best Practices: Bundle Packages, Delta Builds and Delta Packages
Following TDS Classic best practices, like using Delta Builds and Delta Packages, can make the entire development experience run much more smoothly.
Azure Sitecore Deployment: Adding Custom Modules
Modify the previous install so that the initial install contains the Sitecore Package Deployer module. It is an excellent way to enable continuous integration to the website.
Azure Sitecore Deployment: Preparing the Default Scripts and Packages
Preparing the default packages for a Sitecore Azure deployment and extending to add a custom module to the install.<br> <br> <br> <br> <br>
Azure Sitecore Deployment: Setting Up the Solution and VSO Build
<p>The first in our series on setting up a Sitecore instance on Azure, with an initial deployment that includes custom built modules as add-ons to the setup.</p>
Troubleshoot and Prevent Failed TDS Classic Project Builds
When building an .update package with TDS Classic, the build might fail with no additional information. From increasing log verbosity to using validators, there are ways to minimize or prevent this type of error.
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.
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;
TDS How To: Install the TDS Connector for Rocks 2.0
Manually install the TDS connector for Sitecore Rocks 2.0
Using NuGet Packages in TDS
New to TDS 5.5 is the ability to create and consume NuGet packages in your TDS project, allowing developers to capture their Sitecore items and easily distribute them across multiple teams.
Occasional Issue Seen with TDS Installer
When upgrading to TDS 5.5.0.x from an older version and trying to load a solution with a TDS project inside, the following error might occur:
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
TDS for SC Hackathon 2016
For all those participating in the Sitecore Hackathon, check out our Habitat for TDS and some other cool surprises.
Config Transforms for Config Files
If you don't want to use a third party development tool for your config transforms, I have good news. Config transforms are supported natively within TDS!
Package Installer from the Command Line
The TDS package installer allows you to install packages through the command line. Learn how...<br>
New Build for TDS 5.0!
A couple bugs were reported over the last few months. We've been able to fix the bugs and now have a stable CTP version for use.
It's finally here!
Team Development for Sitecore has finally been released go download it now!
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.