The "bower install patternfly" command will create a bower_components
directory. If you clone the repo and run "bower install", you will then
have a components directory.
Looking at the Quick Start Guide, under the "Using Patternfly In Your
Application" section, I see "bower install patternfly" for step #2. This
is a different approach than building the Patternfly repository, which
is where the "bower install" command is used. If you're interested in
building Patternfly, please see the "Development" section in the
README.md file.
Dan
On 7/21/16 11:08 AM, Adam Jolicoeur wrote:
Good Morning,
I recently cloned the PatternFly repo and ran the ‘bower install’ command, as
directed in the installation guide. According to the Quick Start Guide steps
for including PatternFly in my application, I noticed that the references
dictate that ‘bower_components/…’ should be included for both the CSS and JS
files. In my environment, there is not a ‘bower_components’ directory, only a
‘components’ directory, breaking the reference links. Is this an intentional
difference, has the bower script changed from the current Quick Start Guide, or
am I missing something?
Thanks,
Adam
_______________________________________________
Patternfly mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/patternfly
_______________________________________________
Patternfly mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/patternfly
