Feydra Q&A

Feydra Questions and Answers


Q: What problem does Feydra solve?

A: It solves two problems:

  1. It allows Front End Developers to work independent of Back End Developers. That is, FEDs do not need to coordinate with BEDs every time they want to change front end code. They can work independently and check everything into source control to bring it all together. This also allows the front and back ends to work in parallel reducing the overall development timeline.
  2. It allows FEDs to work using their chosen design tool. That is, by separating the design process from the underlying CMS, Feydra lets FEDs design in any tool that can output the final result in CSS/JS/CSHTML (HTML).

Q: How is working with Feydra different than what I do today?

A: Normally FEDs create the front end assets and Sitecore developers chop them up into components. With Feydra, SC devs can create the components as generically styled placeholders that express the data without any styling (essentially as divs). FEDs can update those on their own schedule, breaking dependencies between FEDs and BEDs and allowing for them to work in parallel.

Feydra allows Back End Devs to stub in placeholders for the front end, so the back end can architect and build the actual components based on those the IA has already designed using wireframes (or really simple ones used on every implementation). FEDs can be more efficient because they are working closer to the components, leading to less iteration. FEDs can work on the stubbed components and see how it looks in real time, without waiting for a BED to go and integrate their changes.

Q: How do I install Feydra?

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

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: How long does it take to get a Feydra environment set up?

A: 10 minutes, at most.

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: How does Feydra overlap with SXA?

A: It doesn’t, really. If you use SXA, you won’t use Feydra, since all files go into the media library where FEDs can’t access them easily. Feydra solves one of the problems SXA does (the problem of serial processes by FEDs and BEDs) in a completely different way that retains the existing development tools and processes most teams are familiar with.

Q: Doesn’t Feydra mean the BEDs have to do a lot of work up front?

A: Typically, the IA team would do wireframes, then design would get involved to do the layout and component designs. Then the front end would cut them up into CSS/JS/HTML, and then the back end would start building the Sitecore componentry, leading to iteration between FE/BE as the designs and components were dialed in.

Now back end can figure out the components, data and taxonomy from the wireframes and build unstyled versions (which are vastly easier to build) from the wireframes.  FEDs can then start encoding the designs using the unstyled components that BE built.

 

 

 

Q: Why do I need to buy this?

A: It saves time, saves effort, shortens project timelines, improves agility, and speeds iteration. In essence, we’ve broken a dependency that drives most implementation headaches.

Q: Can I just create a reusable set of unstyled components and do the same thing as SXA? That is, avoid paying for SXA?

A: No, for two reasons.

  1. There are typically two kinds of components to set up: simple ones that take 5 minutes, and complex ones that are unique to the project. So a reusable set only buys you an hour or so on the first type and is not applicable to the second type.
  2. You lose the entire drag and drop page construction that frees your marketing team to pump out pages without back end help.  SXA pays for itself on that alone in about 2 months.

Q: When should I use SXA instead of Feydra?

A: Feydra is good for classic Sitecore development where you are doing a full implementation – a “from scratch” implementation with lots of customization or complex design.

SXA is a great fit when there is not a ton of complexity or when there is a lot of content managed components (or both). Feydra is probably a better choice when either budget is constrained or if the componentry will be complicated.

Q: Is there a "quick" way to get started?

A: Of Course!   After Feydra is installed on the server and configured properly follow the steps below!

 

  1. Open the control panel in your browser “/Feydra”.
  2. Select: Activate as “USER” (your user).
  3. Open the file you want to edit (CSS, JS, CSHTML) in your favorite editor.
  4. Save the file to “/FeydraRoot/USER/…” on the server (be sure to match the path).
  5. Refresh the page in the browser and see your changes.

 

*Note about #4 – saving the file on the server depends on your project configuration (Unc path, remote access, FTP, etc.). It’s possible that this step could be automated, depending on the editor you use.