Open matteofigus opened 7 years ago
/cc @elboletaire @matthewdavidson @navamgupta @Hobbit71 @gondar @NapoleanReigns @BhautikDoshi @gregoryStarr
Perhaps could be worth renaming this issue into something slightly more explicit, like "who uses OpenComponents".. Making it easy for people looking on who's using it to find such infos (until we have a website/section for this)
Hi :) Happy to provide the info here :
OpenComponents are great! It has helped us break our monolithic architecture into smaller components and achieve improved speed of delivery, team autonomy and ownership of different parts of the website. Independent ownership and releases of components have sped up our feature delivery drastically.
We have been using OpenComponents for bringing in flexibility of having a common layouts for different front-end blocks. Whether it's Header, or different related content widgets. We are actually in process of adding new OCs/enhancements every month. Its comes with joy of independent deployments, continuous delivery and integration, and of-course all the added benefits of Node.Js!
Need anything more - get in touch.
Note that we're currently using opencomponents for private components, mostly (that's why we never posted it here):
Whenever we have any other project more "visible" we'll try to publish it here.
Hi Matteo,
Sorry for delay on this one.
We at Cisco use it for UCS Intersight that we just did GA for.
OC has been extremely critical part of our UI component delivery mechanism
What is Cisco Intersight? https://www.cisco.com/c/en/us/products/servers-unified-computing/intersight/index.html
Cisco Intersight Site: https://www.intersight.com
OC Components: https://www.intersight.com/uistatic/oc/
We did made some more enhancements on top of OC which we haven't discussed or contributed back yet :
So I am quite sure we used OC in a bit non-standard way but for us its not just a legacy UI leveraging some OC components - our all UI is ground up build with OC with each framework layer(shell, dashboard, error-page, apidocs, docs - etc) as OC component and each microservice feature UI (authentication, server-mgmt, config, etc ) as OC component as well. So we had to introduce scope concept to avoid version matrix nightmare. We also packaged an old heavy duty (2000 page) app built with dojo as an OC component - this was most challenging part. Now doing other legacy UIs like wise.
So any UI app (new or legacy) to be published on our intersight cloud, has to be OCized (invented new term for you to use!) then it goes through our standard CICD pipeline through jenkins, artifactory, ansible to get it on S3 bucket.
A lot of thanks to you being so prompt in response and enhancements we needed. Let me know if this scope stuff sounds interesting then we will propose an issue now that we have a bit of breathing time after the release.
Bhautik
On Sun, Jun 11, 2017 at 11:56 AM, Matteo Figus notifications@github.com wrote:
/cc @elboletaire https://github.com/elboletaire @matthewdavidson https://github.com/matthewdavidson @navamgupta https://github.com/navamgupta @Hobbit71 https://github.com/hobbit71 @gondar https://github.com/gondar @NapoleanReigns https://github.com/napoleanreigns @BhautikDoshi https://github.com/bhautikdoshi
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/opentable/oc/issues/517#issuecomment-307647477, or mute the thread https://github.com/notifications/unsubscribe-auth/ACV1nPqKcruEkP50h-VVRF81d-JrorOYks5sDDh5gaJpZM4N2eEZ .
Inspired by: https://github.com/hapijs/hapi/issues/1613
We are compiling a list of companies or products using OC for a few reasons:
What we need from you: