Good Day I am developing a *pattern library* which will live alongside a large scale angular application. For consistency purposes it is very important that this pattern library (which will also be built in angular) uses the exact *same files* as the large scale application does. This relates to the components/directives as well as the CSS.
What would be best practice for where I would develop this pattern library app? Would it make sense to have a central location for the template files and then find some way to serve these files to both applications, or would it make more sense to have the pattern library app in a subfolder in the large apps folder structure and then just link to the components it needs? Both apps will run on the same domain (e.g app.example.com and styleguide.example.com). Performance is obviously also an issue, I would imagine serving template files to the large scale app from an external source would mean performance would take a hit. Additionally, would AngularJS vs 2 make a difference on my approach here, the large scale app is built in angularJS currently. Extra Info -------------------- - I am a front end developer who's role is more focused on the design execution than the application architecture, hence I am not an Angular expert. - By pattern library I mean an app that will present all our UI components, essentially a collection of all our buttons, text styles, lists, modals etc. -- You received this message because you are subscribed to the Google Groups "Angular" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
