• State Not Answered
  • Replies 4 replies
  • Subscribers 18 subscribers
  • Views 765 views
  • Users 0 members are here
Options
Related

Front end development workflow

gavinthomas

I'm new to the verint platform. I'm a front end developer needing to set up a local development environment so I can build the theme and UI widgets.

What we tend to do with platforms like this is set up a flat build environment that allows the front end developer to create dummy pages, layouts with css which then goes to a Back end developer to integrate (for example using sitecore or umbraco sites)

With that i've set up a development environment using parcel and storybook so i can isolate widgets and demonstrate widgets.

We're not looking to use the theme functions to change properties in the less files:  LESS Functions 

i've pulled down all the less files and hoping to build them locally (but now running into issues as it's trying to pull those less functions and i've guessing they are defined on the server although i can't find any reference to them)

I was wondering if anyone has done anything similar  or had a different set up? I want to know how other have managed to branch and build widgets



Add info about less functions
[edited by: gavinthomas at 11:12 AM (GMT 0) on Fri, Feb 19 2021]
Parents
  • 0
    gavinthomas said:
    i've pulled down all the less files and hoping to build them locally (but now running into issues as it's trying to pull those less functions and i've guessing they are defined on the server although i can't find any reference to them)

    That is correct. The platform-specific LESS functions are used by the default theme and widgets and are not functional outside of the platform.

    gavinthomas said:
    I was wondering if anyone has done anything similar  or had a different set up?

    We make use of

    1. A vendor-specific factory default provider
    2. The built-in IDE for widgets/themes w/ developer mode enabled (though we sometimes use text editors across the files if performing bulk replacements)
    3. Source control integration via the file system (using Git/GitHub)

    When prototyping markup, either a Raw HTML widget (when just testing markup) or a static HTML widget w/ its own LESS file, is sufficient for us.

      already shared the link to developer mode. There is a similar document for themes as well.

Reply
  • 0
    gavinthomas said:
    i've pulled down all the less files and hoping to build them locally (but now running into issues as it's trying to pull those less functions and i've guessing they are defined on the server although i can't find any reference to them)

    That is correct. The platform-specific LESS functions are used by the default theme and widgets and are not functional outside of the platform.

    gavinthomas said:
    I was wondering if anyone has done anything similar  or had a different set up?

    We make use of

    1. A vendor-specific factory default provider
    2. The built-in IDE for widgets/themes w/ developer mode enabled (though we sometimes use text editors across the files if performing bulk replacements)
    3. Source control integration via the file system (using Git/GitHub)

    When prototyping markup, either a Raw HTML widget (when just testing markup) or a static HTML widget w/ its own LESS file, is sufficient for us.

      already shared the link to developer mode. There is a similar document for themes as well.

Children
No Data

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community