Definitely. I think it’s a worthwhile update to the documentation. -Adam
> On Jul 22, 2016, at 9:53 AM, Leslie Hinson <[email protected]> wrote: > > Awesome, thanks Dana! > > Adam: Do you think Dana's suggestion helps to clarify? > > If so, let's make the update. > > Thanks everyone, > Leslie > > On Fri, Jul 22, 2016 at 8:51 AM, Dana Gutride <[email protected] > <mailto:[email protected]>> wrote: > Hi Leslie, > > I worked with Adam on this yesterday and I just re-read the documentation to > see where the disconnect might have been. From my perspective, I think > github is largely correct - there is a clear distinction between how to use > PatternFly in your project and getting started as a contributor. The issue > that might happen internally is people clone the PatternFly repo and then > switch to the getting started guide to try it out which leads them in > different directions by design. There should be two clear paths and we might > need to make it more obvious to people which path they need to follow. > > We could add an additional statement to the Development section to the effect > of, “This section is only necessary if you are contributing code to > PatternFly, if you wish to use PatternFly in your project, please follow the > Quick Start guide.” We might need something like that in the opening > paragraph as well to help people identify which path is right for them. > > -Dana > > > > On Jul 22, 2016, at 8:35 AM, Leslie Hinson <[email protected] > > <mailto:[email protected]>> wrote: > > > > How can we update our QuickStart to avoid this confusion in the future? > > > > Leslie > > > >> On Jul 21, 2016, at 8:13 PM, Dan Labrecque <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> 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] <mailto:[email protected]> > >>> https://www.redhat.com/mailman/listinfo/patternfly > >>> <https://www.redhat.com/mailman/listinfo/patternfly> > >> > >> _______________________________________________ > >> Patternfly mailing list > >> [email protected] <mailto:[email protected]> > >> https://www.redhat.com/mailman/listinfo/patternfly > >> <https://www.redhat.com/mailman/listinfo/patternfly> > > > > _______________________________________________ > > Patternfly mailing list > > [email protected] <mailto:[email protected]> > > https://www.redhat.com/mailman/listinfo/patternfly > > <https://www.redhat.com/mailman/listinfo/patternfly> > > > _______________________________________________ > Patternfly mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/patternfly
_______________________________________________ Patternfly mailing list [email protected] https://www.redhat.com/mailman/listinfo/patternfly
