0:0:0.0 --> 0:0:27.40
Bethany Pass
Yeah, no worries. See, I'll just share my screen a second, I guess. Take you guys through kind of the core things that I've been doing. So this is the storybook site for the new Helix React core package to try to make it as helixe as possible. But yeah, I'm trying to make it really clear what people can expect from this. Obviously, it's only been me working on this since January, so.
0:0:28.360 --> 0:0:29.680
Bethany Pass
Really needed to set expectations.
0:0:30.330 --> 0:0:51.970
Bethany Pass
So yeah, you can see all the components that I've developed up to the newest documentation standard. So what I've tried to make sure is like any behaviour that is documented in Helix is like super easy to recreate within the components because I think like based on feedback that was something that people were finding quite challenging to create all those variations.
0:0:53.370 --> 0:1:1.610
Bethany Pass
Also, I've also most recently done the date picker and the time picker and the header as well, so that'll be in the next release as well.
0:1:3.90 --> 0:1:32.810
Bethany Pass
So yeah, I've been just working through making it really clear for like how people can install it. So same process As for the Helix plus one. So it's just an NPM package from the idea join jfrog and it works in the same way with the translations as well. So if we do move towards needing multiple languages that's built in there as well and set up all the kind of like get in touch. So as I said we've got like the JIRA project for this. So there's ways to.
0:1:33.200 --> 0:2:2.960
Bethany Pass
Support bug fixes. We've also got our Helix teams channel as well, where we which I think most of you are part of that. But Matt, maybe if you want to drop the link in the chat anyway and that's why we kind of communicate releases for both documentation and the MPM package and it's a place to sort of we were kind of hoping it might develop into an open forum where people can like chat about how they've used components, maybe request new features.
0:2:3.470 --> 0:2:20.190
Bethany Pass
Things like that. But yeah. And then you can just literally see each of the components. So I've tried to keep the documentation page at the start as like an overview of all the different types for the component and you can see the code. Then for how you would recreate that in.
0:2:21.590 --> 0:2:35.510
Bethany Pass
Would you'd install the package into your product so you could literally just copy and paste that and you would be able to replicate that. And again, this is probably really familiar from what you've seen before, but you've still got all the controls to then interact with the.
0:2:36.200 --> 0:2:48.920
Bethany Pass
The different components like set, set, custom things on them and see how they behave so you can sort of play around with them in there. So yeah, as I said, these are the components that I've currently updated.
0:2:50.360 --> 0:2:56.160
Bethany Pass
That is still the other components that were in the library before, so we've got things like the table.
0:2:57.720 --> 0:3:2.880
Bethany Pass
That's still in there and all the other fields that I haven't updated yet, but they are still in the library.
0:3:4.520 --> 0:3:12.0
Bethany Pass
They're just not to the 2.2 specification. Yeah, I've just not reviewed those yet, but they're still accessible.
0:3:12.560 --> 0:3:44.560
Bethany Pass
And yeah, we've still obviously got the iconography set as well, and then most recently what I've kind of been working on is then linking that to our existing documentation. So if you go to a component in here, there's now a build tab and you basically just get like a snapshot view of the Helix storybook. So it saves you having to like, go to a separate site if when you're building, you're kind of looking at the design specification, you can then just flick across to this tab.
0:3:45.440 --> 0:3:53.600
Bethany Pass
And get the code straight from here or you then obviously got the option to view that in the storybook. If there's different things you want.
0:3:53.640 --> 0:3:54.960
Bethany Pass
To change.
0:4:6.60 --> 0:4:6.340
Megan O'Brien
Yeah.
0:3:56.0 --> 0:4:8.0
Bethany Pass
Yeah, I feel like I just spoke at 1,000,000 miles an hour, but that's kind of the Helix package in its in its infancy. But yeah, the hope the hope is that.
0:4:9.720 --> 0:4:16.680
Bethany Pass
So these components are listed on the home page or the components that we've currently scoped as core components core components.
0:4:17.0 --> 0:4:39.360
Bethany Pass
Like the priority because they're being used across multiple products, multiple business lines, but that doesn't mean that this has to be the only list. And like if there's something that we can discuss as a team and we actually think actually know this is this is something that needs to be in the core library, then this is by no means a finite list, I would say.
0:4:40.840 --> 0:4:41.480
Bethany Pass
If that makes sense.
0:4:42.310 --> 0:4:43.630
Megan O'Brien
Yeah. Thanks very much.
0:4:42.730 --> 0:4:50.610
Mah Jin-Khai
That's just one question, right? Regarding those portal types component that we've seen in the margin prototype is that using?
0:4:51.850 --> 0:4:56.810
Mah Jin-Khai
Is that gonna using the 2.21 or gonna be something? Something else? More new one?
0:4:56.300 --> 0:5:27.340
Megan O'Brien
Yeah, yeah. So it's actually a really good question. And I think Matt can kind of just touch on this just now after I've I've given a bit of context around Helix in its entirety. So we've taken a bit of a different approach with Helix as we're moving, you know, forward into this new financial year. And one of the things that we're trying to look at is around flexibility. Historically, we've tried to kind of keep it as you know, concrete in its form as we could in the sense that we create consistency across a lot of our products that utilise Helix components, but actually.
0:5:28.100 --> 0:6:0.660
Megan O'Brien
When we look at it holistically across the board, the rate at which we acquire products and the number of products that we already have within our portfolio doesn't allow for it to be an indefinite one-size-fits-all approach to Helix, right? So Matt and I've kind of looked at this as well as Beth and the rest of the team and said, OK, fine, we want to move towards a unified UX and UI in, in a sense of an identity with an idea Gen across our portfolio within you know, X amount of time, whatever that time be, right, we're going on this journey. We started that journey with Loki. We're all familiar of this.
0:6:1.410 --> 0:6:23.90
Megan O'Brien
When it comes to Helix, we cannot have a sit component library that will be used across all of them. That's why we've split it into core and what we are looking at is calling common or plus or something else like extra where we can have this other library that has components that are utilised around many different products like ARC potentially in exchange products, them so forth. So.
0:6:24.530 --> 0:6:36.290
Megan O'Brien
In saying that, 2.0 is more kind of just the update that we've done to to certain core components components that we refer to as common across multiple different products, things that we could utilise.
0:6:36.610 --> 0:7:5.970
Megan O'Brien
Across a few different use cases, whether it's an acquired product or something that we already own, that is is quite consistent, it's not something that's more complex in its nature. So when it comes to kind of working to the specific specification within Helix, we are working on a new strategy around how we're going to do this moving forward, because it is difficult for for Beth to continuously update those components. So we will get to a point where we're happy with the core components where we once year we'll push and update to those what are the cases. But that's more on the core libraries and not necessarily the complex.
0:7:14.100 --> 0:7:14.300
Mah Jin-Khai
Yeah.
0:7:27.310 --> 0:7:27.470
Mah Jin-Khai
Yeah.
0:7:6.500 --> 0:7:35.740
Megan O'Brien
Kind of what we call common components right now, but they're more around those extra components, if that makes sense. So when it comes to my Gen, a lot of the components that are sitting in there are actually new components. So they they're components that we've looked at possibly, you know, designing from scratch and maybe building because they fit the use case a bit better. You know this will be the case with my gene. And as we're going through it now, we will be kind of making a little bit more consistent as we can to Helix. So those core components, core components, but.
0:7:36.90 --> 0:8:7.170
Megan O'Brien
You know, we will have extra ones that will need to be built from scratch. So why I'm saying this is when we're moving forward what what Matt and I have kind of agreed on is that we cannot take the stance of you have to be up to 2.1 kind of specification. We need to explain what that means. So that's more on core components. If you have core components cool, you can align to that. But there's also this level of flexibility that needs to be had within the way that we reskin products and the way that we we utilise Helix because as long as we belong to a well, as long as we look and feel like we belong to the same family, I think that's enough for us to get this common.
0:8:28.940 --> 0:8:29.620
Mah Jin-Khai
And and.
0:8:7.590 --> 0:8:30.190
Megan O'Brien
Identity, as we call it across our suites of products, right. So we're in the stages of of outlining that strategy and defining exactly what the mechanics are that move, that there will be some consistency in some form or another, but also a huge level of flexibility, JK. So I know that there was a whole lot of information, but I hope that that makes sense in the direction in which we're moving.
0:8:31.560 --> 0:8:41.920
Mah Jin-Khai
OK, S South side, we're gonna call it like 2.3, something like that. But not gonna be a huge changes there because you didn't mention this additional components of additional new component.
0:8:40.470 --> 0:9:11.270
Megan O'Brien
Yeah, those. Yeah, exactly. And I don't think that we would. I mean, even when we look at the documentation, right, Matt is actually racist. He's like we can't continue to document every single thing that like, we'll have to be figuring out the way in which we can utilise the documentation in a way that makes sense, but also have what we're calling kind of patterns in sets of components that are specific to a use case for specific products, right. So we actually in a really good space of the strategy at the moment, we're looking at not only redefining how we reskin and what that actually means, because a lot of people get confused when we talk about.
0:9:11.630 --> 0:9:29.470
Megan O'Brien
Plays one resin opposed to phase two or three, right? Like we need to define exactly what that is. The business of the line to what that means from a Helix perspective. And then what actually that includes, right? So and then what the expectation is, we cannot expect every single product to abide by a specific set of rules.
0:9:30.710 --> 0:9:43.430
Megan O'Brien
Across every single instance with this instance within that product. But we can certainly look at some core components that you know we can standardise and creates consistency across the board. But as long as it's a, it's a unified identity in the sense that we are sticking to the guidelines.
0:9:43.790 --> 0:10:3.790
Megan O'Brien
In a sense of the style guidelines, the colours, you know, the kind of way in which we design components and those patterns in in you know as we call it, I think that we'll get to a place where we are happy with identity and kind of that consistency. Matt, do you want to add something to this because I know this is your baby and we've spoken about this a lot.
0:10:3.870 --> 0:10:7.590
Matt Everitt
He pretty much covered it. Yeah, the kind of whole purpose of core is to.
0:10:27.790 --> 0:10:28.910
Megan O'Brien
Yeah, a huge principle.
0:10:9.150 --> 0:10:44.230
Matt Everitt
Give developing teams a foot up when transitioning over to Helix, so the idea of core is that it will cover you know, typically depending on the product around 60 to 70% of kind of most interfaces. So you know by default you're only going to have to do say this with a pinch assault, 30% of the developing work of those kind of bespoke, what we're calling common, which will be changed soon, components which are kind of more product specific components, but it's a it's essentially a way of kind of giving you a foot up. So you're not starting from kind of scratch having to develop every single component.
0:10:44.630 --> 0:10:45.70
Matt Everitt
Essentially.
0:10:45.240 --> 0:11:16.200
Megan O'Brien
Yeah. And those are more whether whether whether that kind of what's the word for that's governance, if you wanna call it, we'll sit. So we can own that because we we have basically, we'll update those components and assist you guys and say OK guys like we've got a bit of an update, don't worry, we don't expect you to kind of not put this into your build pipeline or your kind of work stream because we know it's not priority over other projects that you're already working on. We'll do that update, we'll push it up and we'll send that through to you at you know so it's more like a helping hand of what how we're looking at it. We want this to be something that developers can use.
0:11:34.870 --> 0:11:35.70
Mah Jin-Khai
Oh.
0:11:16.640 --> 0:11:45.840
Megan O'Brien
But it's also not something that is, you know, a kind of dictated to, to to developers or product lines. Like if you're not built in, you know if we have the React Library and you guys, you know your your front end is built with an angular for example. We're not saying you have to move over to RCC. That is very much a product decision that has to be made by the product leaders, you know, so and the people that that are in charge of that, that particular product and business line. So we see ourselves as being of service to the business, OK. So we are an in house service to the business.
0:11:46.120 --> 0:12:16.400
Megan O'Brien
Where we, you know, provide but kind of mechanisms that will assist the teams to be efficient in all instances. So we we've very much taken that stance with core. We would like to get to a space in a kind of in time where where developers are contributing to our libraries and we have this you know flexibility in terms of how we work but also kind of how we store code and how we have these repositories sitting within the business that we could utilise code. So for example if platform team have developed.
0:12:17.600 --> 0:12:45.200
Megan O'Brien
Certain components, say within a different front end. Then we have those those libraries that are stored, and we have those repositories that if we acquire a product, say in Angular we can say hold on. Actually we've got this repository of code sitting over here. Would you like to utilise that you know, so we're not wasting and duplicating effort in terms of building Helix components, we're going to be you know creating loads of components work throughout the business as we go on this journey. Most of the products in play for this year are Helix fine in some sense or another.
0:13:2.410 --> 0:13:3.530
Mah Jin-Khai
Oh oh.
0:13:4.830 --> 0:13:5.550
Mah Jin-Khai
Any production?
0:12:45.590 --> 0:13:6.710
Megan O'Brien
So we need to work smarts and there's two aspects that the core libraries are one, but then the other one is actually finding a way in which we can house this code and then, you know, consume it in the business and share that code. How we do that JK is really what I need. Your guys's help with. And I think Beth is also kind of really looking for that assistance because we obviously don't have the experience to make those decisions.
0:13:8.40 --> 0:13:36.760
Mah Jin-Khai
I I think my point of view is is better to stick to one language, but if there's certain product they can move to reactive to certain reason, I think they need to they need strong testification or else everyone will be building on things. So in the end we we we go back to the square that there's a, there's a, there's a lot of duplicates of it by by looking at the training right now. So if if all the product are building their own, so you're gonna have.
0:13:36.800 --> 0:13:48.840
Mah Jin-Khai
So at least you have a three different type of language that that gonna be quite tricky one. So we can like set some guideline. So the.
0:13:50.920 --> 0:14:29.520
Mah Jin-Khai
Guideline is like you focus on using react as your main choice as a top rating. If you if you can't you need to justify why you can't. Then you need to perform to another options. So it's a it's it's the same thing goes to cicd. There's four pipeline obviously so they are product using they gain their product using Team CD. Some product using Azure and NWS is gonna be very difficult. So we also having the same challenges as well. So we're kind of like decided OK let's let's stick to let's say if at that committee stick to Jenkins so this is our top priority. If we're building new product there's no sort of reason there's no excuse you you have to build something else.
0:14:39.660 --> 0:14:39.860
Megan O'Brien
Yeah.
0:14:29.600 --> 0:14:44.680
Mah Jin-Khai
But you already have assistant for that running in Team CD. Then you you you have to stick to it because it could take a long time to move to everything, to to a new tools. So I believe that I like facing the same same same challenge. But how how?
0:14:46.360 --> 0:14:58.600
Mah Jin-Khai
I I'm I'm certain I quite certain that platform teams it would help to build some of this component, but I think we we need to know I I think we need to know the specification for the migrant component.
0:14:59.350 --> 0:14:59.550
Megan O'Brien
Mm hmm.
0:15:1.80 --> 0:15:1.400
Megan O'Brien
Yeah.
0:15:16.40 --> 0:15:16.280
Megan O'Brien
Yeah.
0:15:0.160 --> 0:15:16.800
Mah Jin-Khai
As early as possible, I think Keith Keith will set up probably I think He've did double check to do the other groups talking about doing some of these specification. I'm not sure what would be the priority, but my imagination I'm thinking maybe the net panel would be first one to to start with Adam. Yeah.
0:15:39.750 --> 0:15:39.950
Mah Jin-Khai
And.
0:15:17.810 --> 0:15:48.810
Megan O'Brien
Yeah. And I I I've mentioned just to Keith when he came in the call this morning that Matt and I have spoken about it, he messaged us this morning. So obviously off the back end of the platform meeting, we had the kick off we need to we had last week we have we have been looking at that so kind of pushing just those I suppose priority component all the components that we don't feel necessarily need to be tested as heavily as others. So pushing those through. So we can just start that development work. So we are working on that at the moment. So yeah I do see you know the platform team.
0:15:49.530 --> 0:15:51.610
Megan O'Brien
As a team that could possibly contribute to this library.
0:15:52.500 --> 0:15:52.740
Mah Jin-Khai
Yes.
0:15:53.250 --> 0:16:16.810
Megan O'Brien
Because we'll be building some components that we will probably define as core anyway. But then those are the kind of more complex components we can also house as well because we could still utilise those in other areas. One of the questions I do have JK for you and and the team is around, I do agree that you know we in this space because we have multiple different technologies within the products you know and and it's kind of left us in the space where we can't really own.
0:16:33.350 --> 0:16:33.590
Mah Jin-Khai
And.
0:16:18.210 --> 0:16:34.770
Megan O'Brien
This and it's, you know, it's whole form, but moving forward I think I agree that you know I in an ideal world we would want every product to be on reaction that would just be great because then it's so much easier for everybody involved. But how do we future proof or acquisition acquisition then because I think that's my biggest thing here is that these repositories would be useful.
0:16:35.320 --> 0:16:49.120
Megan O'Brien
For products that we acquire because you know, then it would get them onto Helix a lot quicker then then what we've done in the past. So I don't know if that's something that you agree with, but I think it's worth a yeah.
0:17:1.80 --> 0:17:1.320
Megan O'Brien
Yeah.
0:17:21.870 --> 0:17:22.190
Megan O'Brien
Yeah.
0:16:48.820 --> 0:17:23.340
Mah Jin-Khai
Yeah, I I think future acquisition, uh, I kinda quite like your previous vision concept you displayed to different phases as you remember. That's a that's a wonderful faces one on phase one to phase four. I think we kinda like my my probably I could I think kinda we can stick to that. So the the moment right, the moment when the acquired company they let's say example the acquire company using Angular so he's very he's gonna be very challenging for them to actually move to Helix if we are using react so I don't think we can run away because.
0:17:58.550 --> 0:17:58.870
Megan O'Brien
Yeah.
0:17:23.940 --> 0:18:9.300
Mah Jin-Khai
We we have to fire balance unless unless unless the original Helix call, we are right within JavaScript or else is impossible for angular to to use it. I mean it's kind of portable. There are people doing some POC using angular to call React component before but there there's still some risk there you know. So it might not be really working in certain cases. The behaviour as well might be different. So I I guess we have to we have to find a balance and decide that vision and then you we have to we have to accept the fact that something product we could have a drawback give you because because if if you if you using pure JavaScript to write a code right in the end you could have other phones like it would take long time for to build 1 component this thing goes to Helix question mark.
0:18:25.800 --> 0:18:26.120
Megan O'Brien
Yeah.
0:18:10.380 --> 0:18:27.980
Mah Jin-Khai
So but the the the good thing is, like anyone can portable to to use it. So if you want to use mu do something on top of mu then we we have to accept that maybe certain certain product are using angular or other tech could be having challenges to to move to the final phase.
0:18:30.150 --> 0:18:30.710
Kar King Siew
And.
0:18:28.580 --> 0:18:32.60
Megan O'Brien
Yeah. OK. So yeah, sorry. Yeah.
0:18:32.310 --> 0:18:59.390
Kar King Siew
Oh, so sorry, Megan. I actually, I do have a suggestion that actually I I like the idea that to have a call library to have all the components that is commonly used like buttons, right, that that is pretty obvious. But for those complex components as a developer, I would like to build it for different technology. Let's say if I were using Angular, I will build it myself.
0:19:0.270 --> 0:19:9.30
Kar King Siew
The biggest challenge I'll be facing is this style itself, so it if I would have to have.
0:19:10.350 --> 0:19:13.670
Kar King Siew
Those CSS utility just like tailwind CSS.
0:19:13.920 --> 0:19:14.120
Megan O'Brien
Yeah.
0:19:15.470 --> 0:19:25.870
Kar King Siew
Which provide all the styling available I can use and I can mix and match that will be quite helpful in developing the component itself so.
0:19:27.550 --> 0:19:35.310
Kar King Siew
Apart from the Helix Core Library, probably we can provide these kind of CSS utilities for the developer to use.
0:19:36.170 --> 0:20:2.290
Kar King Siew
Then the component itself will be sits on. It depends on the pillar or the product itself whether how they want to manage their share components. One of the way is I already posted on the chat. We can use the bit bit is a platform to share a piece of code and you can install that piece of code using the NPM.
0:20:2.330 --> 0:20:14.970
Kar King Siew
Mpx command, so yeah, yeah, it's up to the team to resolve how they want to share the piece of code, but the style link is common across all products and is freely used by everyone.
0:20:15.500 --> 0:20:44.500
Megan O'Brien
Amazing. That's really helpful. Yeah, that's super helpful. So just on that note, would we be able to do that across obviously different technologies, right? So whether that's in react or whether that's in angular, whatever the case is, we could share because when I'm talking about these repositories, I suppose what I mean is exactly that just sharing code, but we need to know where it sits as well, right. So it's like, I don't know if that's going to be a value. And I think what I'm asking is, is, is for you guys to say is that of value, would it be of value if we had a mechanism in place to?
0:20:45.540 --> 0:20:49.580
Megan O'Brien
Know where some of this code is sitting in the business. So say for example, if you've built a component.
0:20:49.860 --> 0:21:11.820
Megan O'Brien
That now we see is gonna maybe be useful in another product and it's in the same front end technology. Could you share that and say OK well actually we could just use it instead of building it from scratch again and change some of the CSS styling to match what they need to do. So is that something that's possible? Is that something that's useful sharing code, this idea of sharing code from the business outside of call as well.
0:21:16.30 --> 0:21:18.430
Kar King Siew
I I can't think of a better way to do that.
0:21:19.160 --> 0:21:19.280
Megan O'Brien
And.
0:21:19.790 --> 0:21:28.30
Kar King Siew
Probably we need. Yeah, someone to consolidate all the repository. And yeah, have that piece of probably a centralised page.
0:21:28.710 --> 0:21:28.990
Megan O'Brien
Yeah.
0:21:29.710 --> 0:21:34.990
Kar King Siew
To point out where are those components? Yeah, so probably that that is one of the way.
0:21:36.710 --> 0:21:45.750
Kar King Siew
Another way will be, yeah, I wish I have posted in the chat is the we will you fully. Yeah. We will utilise the big platform.
0:21:48.380 --> 0:21:49.980
Megan O'Brien
Yeah, OK, got you.
0:21:51.560 --> 0:21:52.520
Megan O'Brien
Yeah, I couldn't go.
0:21:46.850 --> 0:21:53.650
Kar King Siew
To upload the code as a yeah and install it from there. Yes that.
0:21:55.660 --> 0:21:56.460
Kar King Siew
Oh, OK.
0:21:51.760 --> 0:22:22.640
Matt Everitt
That's that was originally what we were going to do 'cause we created a a spreadsheet and we thought we started thinking about how that would be maintained and there's kind of a lot of areas for things to get missed essentially. So we're going to own that. We, we are going to do a kind of like off the record sort of audit of different products to see what components they've made and in what frameworks that's in. So then if you know another team comes in and says, well, OK, we we want this.
0:22:23.130 --> 0:22:54.170
Matt Everitt
This certain component that's in Angular, then we'll have a spreadsheet to say OK, yeah, this this product over here has it and his access to their repository and so on and so forth. We were originally going to kind of have product owners do that, but I think that it's probably better that we organise that ourselves. Additionally, I think that what we were planning on doing is having some sort of code snippet within our specifically for the common libraries on our documentation for exactly what you're saying. So.
0:22:55.830 --> 0:22:56.270
Megan O'Brien
Yeah.
0:22:54.370 --> 0:23:0.650
Matt Everitt
It's quite validating to hear that that's probably one of the best ways of going about it. So yeah, we'll be definitely adding that to the documentation soon.
0:23:1.700 --> 0:23:32.540
Megan O'Brien
Yeah. I think one of the biggest things that we've struggled with is just that kind of governance of it. It's like, how do we know where a lot of it's sitting and how do we keep that updated because it can get to a point where you know, and I think that just in to Matt's point, it's going to be up to us to do that. But then also when we're designing things, our our designers will know what kind of complex components they've used that are similar to the other ones in a different project. We might know where those consistencies are sitting as well. So it's not going to be up to the developers to say, oh, can I please have the code for this, we'll probably just hand it over.
0:23:32.870 --> 0:23:40.910
Megan O'Brien
When we do handover anyway, so there's all these things, but I just I suppose this call is just to validate that that is going to be of value in the first instance.
0:23:44.970 --> 0:23:46.450
Megan O'Brien
So thank you very much for your feedback.
0:23:59.50 --> 0:23:59.370
Matt Everitt
Yeah.
0:23:47.650 --> 0:24:3.530
Mah Jin-Khai
And I think the other day also talk to Matt about the terminology. Uh umm, by personal feeling. I think we should. We should rename the common common component to product component. I think there will be quite a lot easier. I don't understand it. Yeah.
0:24:5.480 --> 0:24:5.520
Mah Jin-Khai
I.
0:24:20.760 --> 0:24:21.520
Mah Jin-Khai
OK. Thank you.
0:24:30.430 --> 0:24:30.670
Megan O'Brien
Yeah.
0:24:2.90 --> 0:24:32.450
Matt Everitt
Yeah, we've, we've been trying to think of names since JK and that it's it's not as simple as we would support. It was going to because we want something that's, you know it kind of does what it says on the tin, but also at the same time in an ideal world, it would have been Helix plus, but that would be we feel that that's going to be confusing because obviously we had Helix clips which is now react core. So yeah, we're trying to find out the right naming convention and then we're going to change it. So yeah, watch this space hopefully within the next week or two that will be changed. But yeah. Thank you. Thank you for that. That's.
0:24:32.500 --> 0:24:32.740
Megan O'Brien
Yeah.
0:24:33.720 --> 0:24:33.920
Mah Jin-Khai
And.
0:24:33.410 --> 0:24:34.770
Matt Everitt
Put a lot of things in motion for us so.
0:24:35.780 --> 0:24:35.980
Mah Jin-Khai
Mm hmm.
0:24:35.200 --> 0:25:4.640
Megan O'Brien
Yeah. And I mean if you guys have any suggestions like any of your team have suggestions, please feel free to send it Beth on Matt's way, if they would like it to be called something that they think makes sense at the end of the day, we want to make this as as kind of simple and kind of easy to to understand because I know that there's a lot of different concepts around Helix floating around the business and a lot of people get, you know confused, let alone ask. We also get confused ourselves to be better. So we just want to make it simple and just easy to kind of know the difference. Yeah.
0:25:31.300 --> 0:25:31.580
Megan O'Brien
Yeah.
0:25:5.570 --> 0:25:39.850
Mah Jin-Khai
Yeah, most of the time when we have discuss situation, we will we put down some information in the conference page to give explanation to what is the meaning of the terminology. Just to let you know, Keith Kingswin the the call itself is like it's like a component used by multiple product like text box everything. So sometimes you do have a certain very unique component like metrics, risk metrics or something then that that that only used by rice products. So now now we're calling that as a common component. I I suggest to to change it.
0:25:40.940 --> 0:25:43.100
Megan O'Brien
Yeah. Perfect.
0:25:43.930 --> 0:25:44.490
Bethany Pass
Sounds good.
0:26:11.430 --> 0:26:11.510
Megan O'Brien
Mm.
0:25:45.320 --> 0:26:15.160
Mah Jin-Khai
But now now I try to think about a little bit more deep right. Let's say if we had a specification for my Gen application, I I I do see that there's a possibility we need to move to version three or something like that. Why? Because although the the first obvious will be the navigation panel, the navigation panel with the designer mouse Gen Portal that is totally different from the Helix tool version two. So if we don't move it to.
0:26:43.870 --> 0:26:44.190
Megan O'Brien
Yeah.
0:26:16.320 --> 0:26:46.120
Mah Jin-Khai
A major break in versions I think people might might confuse a little bit is is that is that a new component or is that upgrades from navigation better? I think we need to think through a little bit further because normally in a in a, in A tag world when we have a so-called breaking changes we will we will change the number for the first first step for the 1st digit. So I I do see this as a breaking changes it'll be a a lot easier for people to understand so.
0:26:47.40 --> 0:26:58.480
Mah Jin-Khai
If if we stick to 2.32 point 5 or something like that, people might see it, see it as like a new component instead of a replacement of the existing navigation panel. That is my, that's my favourite.
0:26:59.60 --> 0:27:6.100
Megan O'Brien
Yeah. So I think I think my gene isn't just as as a whole is probably like an.
0:27:6.140 --> 0:27:27.660
Megan O'Brien
It's probably a something that is different to kind of the rest of it. So if I said that in the base way, it's the exception essentially and it's not the exception to the rule, but it's basically just something that we've created from scratch as a proof of concept. So I'm fully aware that my gene and the way that we've designed it is completely different to the traditional approach of how we design Helix components and what we have within our library.
0:27:28.300 --> 0:27:58.300
Megan O'Brien
If we look at home right now, as it stands, obviously we have the navigation already and they sort of probably just easier just to utilise that and we probably can do that JK. So this is a conversation we can have right. Like if we say well, we feel that actually we should have stick to the same kind of navigation we had previously, we should push that through. The biggest thing for us is that we want to make it simple. So when we discuss this and when we went through this kind of POC journey, we discussed that kind of we feel that less is more when it comes to navigation in home in particular because it's going to be so much.
0:28:19.390 --> 0:28:19.550
Mah Jin-Khai
Yeah.
0:28:27.0 --> 0:28:27.120
Mah Jin-Khai
Umm.
0:27:58.690 --> 0:28:31.570
Megan O'Brien
That's in there that needs to be really easy, just kind of navigate and understand what's what. So the the left hand NAV that we currently have is a little bit more complex in its nature. So we've stripped that down and then it's also enabled us to have the flipping mechanism at the top, which allows us to use that elexian approach to, you know, switching between products, right. So we'll need to bake that in in some form or another. And maybe that's just a home bar that we have at the top. And then we obviously have the left. And so we I have discussed this with Matt and Ryan because initially my thoughts were no, no, guys, we can't have something different. We need to have the original map like that's what we need, but.
0:28:53.260 --> 0:28:53.900
Mah Jin-Khai
She says.
0:28:32.360 --> 0:28:58.760
Megan O'Brien
We will only really know the the truth about what is needed from a user perspective when we test it, and that's what we're trying to do now. I do believe that it is going to what you call a breaking change. It's going to be, it's going to be regarded as that because it is so different when they move into products, it will be the lifetime app anyway. So I'm happy to go with your suggestion. Like we we talking about this at the moment and saying, OK, well, do we just say that? So I've got a bit of feedback. Do we just?
0:28:58.500 --> 0:28:59.660
Mah Jin-Khai
That's one.
0:29:0.400 --> 0:29:4.960
Megan O'Brien
Go with the fact that we're going to keep the lifetime, maybe just reduce that to simplest form.
0:29:5.970 --> 0:29:17.50
Megan O'Brien
Or do we potentially just create the simplest version of of that NAV like we've created in the POC and move with that because there's gonna be a lot of variations in a navigation in itself is probably one of the biggest components, right? It's one of our most important so.
0:29:18.610 --> 0:29:27.210
Megan O'Brien
I'm happy to hear your thoughts and then leave it with us and we'll we'll probably get that to you guys. But you guys have really built that component anyway. So I believe that that's something we can just start to implement.
0:29:29.100 --> 0:29:34.420
Mah Jin-Khai
I I quite like the late this design for my channel. I think it's Umm is is quite.
0:29:39.270 --> 0:29:39.510
Megan O'Brien
Yeah.
0:29:36.100 --> 0:29:40.420
Mah Jin-Khai
It is quite, quite quite shoved to the whole user experience so.
0:30:4.690 --> 0:30:4.890
Megan O'Brien
Yeah.
0:30:12.240 --> 0:30:12.440
Megan O'Brien
Mm hmm.
0:29:43.20 --> 0:30:14.260
Mah Jin-Khai
It was, but it's just solely on on my opinions. So but. But anyway, just to let's just let you know the the home, the my Gen we we are not going to enhance for the I mean we we we're gonna we're gonna branch out from the current current source code and then we're gonna enhance what the current source code but we we are not gonna patch back for the app so so they will have to they will upgrade to we're gonna call this version 4 hydration version 4 for my Gen.
0:30:28.50 --> 0:30:28.90
Megan O'Brien
M.
0:30:28.170 --> 0:30:32.50
Mah Jin-Khai
The desktop? That's the technical plan for for the.
0:30:32.670 --> 0:30:33.150
Megan O'Brien
OK.
0:30:41.450 --> 0:30:41.530
Mah Jin-Khai
Oh.
0:30:47.250 --> 0:30:48.330
Mah Jin-Khai
Yeah. OK.
0:30:51.950 --> 0:30:52.110
Mah Jin-Khai
OK.
0:30:34.870 --> 0:31:2.510
Megan O'Brien
OK, perfect. Yeah, I think that the navigation is is one thing in particular that we need to just, I'd like I think like I said, the only the only way we're going to really know this is when we test this with the users, which is going to happen in the next week or so. So you know when when we actually test because our our theory is that actually within home if we keep it less is more and simple, it's not going to be too jarring when they move into products. It's almost something that you know the user could expect. So you have the navigation and home as you land in obviously once you navigate your product.
0:31:3.120 --> 0:31:11.480
Megan O'Brien
Change to the lifetime navigation that's in play within that product, but that's obviously a lot more complex, you know, so.
0:31:17.260 --> 0:31:19.860
Mah Jin-Khai
Hey, let me show it.
0:31:24.240 --> 0:31:24.520
Mah Jin-Khai
Oh.
0:31:29.340 --> 0:31:29.500
Mah Jin-Khai
You.
0:31:31.40 --> 0:31:31.240
Mah Jin-Khai
Yeah.
0:31:11.520 --> 0:31:32.680
Megan O'Brien
That's our theory. Our theory is that it's not going to be. We will get. It'll be fine. And then the other theory that we have is that actually we can create consistency within product for having the home bar sitting at the top that even when you navigate into product, that home bar will always remain the same, which allows you to flip between home and any other product that you own a licence for. So that's why we've done it the way we've done it so.
0:31:35.430 --> 0:31:36.870
Megan O'Brien
I'm happy to. Kind of, yeah.
0:31:54.840 --> 0:31:56.400
Mah Jin-Khai
So I'm telling.
0:31:35.620 --> 0:31:57.500
Bethany Pass
I see it. I was just gonna say, like, just from the perspective of the core libraries, all that I've been working on, we actually descoped the navigation. So that is the old navigation. I'm not changed any of that yet. So we're kind of waiting out to see if we're going to go down this route or stick with the old one. So that might be something we can work together and collaborate on if to create a new one.
0:32:26.410 --> 0:32:26.690
Mah Jin-Khai
Yes.
0:31:55.860 --> 0:32:35.860
Megan O'Brien
Yeah, yeah, yeah. And and even that base, it's like the the new one in. We will always have a need for lifetime NAV, right. And I would, I've said to Matt and and what we've agreed actually as just a design system and you know the UX team is that the level of flexibility is needed where we all need probably an option for top end navigation left hand navigation as well as the home bar because if we acquire a product now that has top hand navigation and we say, OK, cool, move on to Helix, we're going to do a phase two. Sometimes you know the the juice is not worth the squeeze. It's a large change to make for a product and it's a large change from the customers to make innovation. We can maybe get there, but we've created this flexibility or we've we've agreed that we're going to look at creating this flexibility where we can accommodate for both, right.
0:32:35.900 --> 0:32:38.100
Megan O'Brien
Matt has created a lovely kind of new approach to how we.
0:32:38.730 --> 0:32:47.490
Megan O'Brien
We can have use the the left hand NAB that design has been changed and kind of, but we haven't put that into play. Oh, sorry, JK, I think I'm getting a lot of feedback.
0:32:45.10 --> 0:32:47.570
Mah Jin-Khai
Yeah, absolutely.
0:32:49.630 --> 0:32:51.150
Megan O'Brien
Paying through from your screen.
0:32:51.480 --> 0:32:53.680
Mah Jin-Khai
I'm sorry. Is it freezing?
0:32:52.990 --> 0:32:53.910
Megan O'Brien
Then don't sit.
0:32:59.390 --> 0:32:59.550
Mah Jin-Khai
OK.
0:32:55.670 --> 0:33:0.30
Megan O'Brien
Anyway, so Long story short, we'll get back to you on that JK, but.
0:33:3.520 --> 0:33:4.360
Mah Jin-Khai
I think.
0:33:0.230 --> 0:33:11.470
Megan O'Brien
The left side NAV will still be in play in product, right? Like we'll still utilise that and we'll still have that in product. But then it's just a version of that will be used for home if that makes sense. All very confusing. We need to kind of streamline it.
0:33:13.870 --> 0:33:14.30
Megan O'Brien
Yeah.
0:33:14.750 --> 0:33:14.750

Umm.
0:33:14.770 --> 0:33:25.890
Mah Jin-Khai
Who, how, how? How long? This uh stakeholder will take to review that I genuxus uh user experience gonna be happen this week or something.
0:33:33.810 --> 0:33:36.290
Mah Jin-Khai
Yeah, yeah, yeah. Today today's calls.
0:33:53.250 --> 0:33:53.450
Mah Jin-Khai
8.
0:33:26.540 --> 0:33:57.820
Megan O'Brien
Yeah. So we saw in testing this week, so we've got our you were in the kick off, right. So we're in the kick off with us where we showcase all. Yeah. So yeah, so we've got our plan, but then obviously as we agreed from the actions from that meeting is that we need to actually start pushing some some lower priority components through to you guys that don't need to be tested. So they've already started to analyse that, that and kind of do that work. So Matt and Ryan are saying working on that way we're going through and saying OK cool this component, this component, this component needs to be built. You know things like.
0:34:3.540 --> 0:34:3.700
Mah Jin-Khai
Hey.
0:33:58.790 --> 0:34:18.70
Megan O'Brien
Card or, you know, there's so many things in there that we'll need to either update some of the components or potentially build from scratch. So we're putting that list together so we can start saying to you guys and saying, well, actually start building these, which is fine in the meantime. And then once we've kind of done our round of testing, got enough feedback and iterated, we can then move on to the rest.
0:34:22.320 --> 0:34:22.480
Megan O'Brien
Then.
0:34:20.510 --> 0:34:23.950
Mah Jin-Khai
OK, OK, sorry 22. Sorry. Two weeks, 2 weeks.
0:34:35.210 --> 0:34:35.770
Mah Jin-Khai
OK.
0:34:37.440 --> 0:34:38.480
Mah Jin-Khai
If you feel like.
0:34:41.50 --> 0:34:41.170
Mah Jin-Khai
And.
0:34:44.210 --> 0:34:44.330
Mah Jin-Khai
And.
0:34:45.930 --> 0:34:46.250
Mah Jin-Khai
OK.
0:34:25.340 --> 0:34:56.460
Megan O'Brien
Yeah. So in the in the plan that we have, obviously the the tasting will take a little longer. So we're hoping by kind of mid to end June that'll be finished that we'll be finished with it and kind of hang a baby, but we'll drug feed in the meantime, whatever we can drug feed, we're going to be drug feeding. So anything that we can from now from this week will start to push through to you guys. And then Keith and Joanne and yourself can just work with my team closely and say, OK, cool, this is what we're going to work on. This is what we're going to do, blah blah and make sure that that's that way of working is is streamlined and efficient.
0:34:57.840 --> 0:34:58.80
Mah Jin-Khai
And.
0:34:57.300 --> 0:34:59.620
Megan O'Brien
So we all kept in the name loop, so.
0:35:1.710 --> 0:35:2.390
Mah Jin-Khai
Yeah, because.
0:35:1.660 --> 0:35:3.700
Megan O'Brien
If that's OK with you guys, we plan on doing this week, yeah.
0:35:5.950 --> 0:35:24.750
Mah Jin-Khai
Looks OK for me, since just to let you know, Bobby, there will be another team free up for to put as well your favourite team audience as well so they can build components then meanwhile can build some of it and build the screens or something like that.
0:35:31.690 --> 0:35:32.890
Megan O'Brien
Yeah. OK.
0:35:24.790 --> 0:35:33.190
Mah Jin-Khai
But potentially I just to let you know, in the end of my Gen write to be three teams working on the UI, so being quite challenging. Thank you.
0:35:33.750 --> 0:35:38.230
Megan O'Brien
OK. Do we have a period of time whether those teams are a little bit free up right now?
0:35:40.520 --> 0:35:44.600
Mah Jin-Khai
So when any comments are on the team or team will be.
0:35:44.640 --> 0:35:46.360
Mah Jin-Khai
Early on next or you know next month?
0:35:48.920 --> 0:35:49.40
Mah Jin-Khai
And.
0:35:53.340 --> 0:35:54.580
Mah Jin-Khai
And yeah.
0:35:46.940 --> 0:36:15.340
Megan O'Brien
OK, cool. So we have a little bit of time 'cause. I'm just thinking, if we do have, if you guys do have any developers at the moment that could start to just build some components we could really utilise some help with in the call library. So we'd and I mean you're going to use those those components anyway, right? So you could you could assist us in helping build those that would be huge benefit to Beth, but that's only if you guys have assistance right now to to to help if you're busy with other thing, then obviously as we drip feeding that will kind of go into your backlog and then the team can pick it up when they're ready. So that's fine.
0:36:16.420 --> 0:36:16.740
Megan O'Brien
And.
0:36:32.880 --> 0:36:33.320
Megan O'Brien
OK.
0:36:16.550 --> 0:36:37.870
Mah Jin-Khai
I think it should be OK, but then just, uh, maybe it will get back to you again. So after switching with the teams because uh, uh, the original platform team, he stays very busy with the licencing and so on. Some of these dev OPS, so once again maybe a few more teams maybe at at least two teams will be able to build this.
0:36:39.630 --> 0:36:54.550
Mah Jin-Khai
I I I do agree that we need to get this been reviewed by some this user user within either Gen, but I don't think they will comment about a component itself. Mostly it's about fuse and the navigation and everything, yeah.
0:36:57.510 --> 0:36:58.70
Mah Jin-Khai
OK.
0:37:0.930 --> 0:37:2.570
Mah Jin-Khai
OK, OK.
0:37:10.130 --> 0:37:10.290
Mah Jin-Khai
Yeah.
0:37:23.240 --> 0:37:23.720
Mah Jin-Khai
OK.
0:36:54.780 --> 0:37:30.940
Megan O'Brien
And it won't just be internal. So we're doing a little bit of internal majority of it's going to be external testing. So actually testing with our users, right and saying is this because I mean as you guys know, if we don't do this discovery up front correctly, we're just going to build technical data for ourselves later down the line. We're going to build something that is not of of of value to our customers, right, like we need to, we need to basically just validate and confirm that what we're building is actually what our users want and and meets those needs, right. So we're going to be tasting over the next, that's what, that's that whole end to end kind of user testing plan that we all the testing plan that we put together.
0:37:31.880 --> 0:37:32.0
Mah Jin-Khai
Huh.
0:37:31.340 --> 0:37:38.740
Megan O'Brien
It includes some internal testing with stakeholders in the business, but then more importantly testing with our users within different markets within.
0:37:43.190 --> 0:37:43.710
Mah Jin-Khai
OK.
0:37:40.280 --> 0:37:51.320
Megan O'Brien
The user groups that we currently have within our products, right? So. So yeah, so that that's going into play. And so we're making sure that we're very specific in, in the way that we're doing that so that we can be efficient.
0:37:53.400 --> 0:38:4.440
Megan O'Brien
Yeah. So that's where I think a lot of the, the the valid, you know that that feedback is gonna come back and will be very really useful for not only us but you guys as well. And understanding are we are we building the right thing.
0:38:7.100 --> 0:38:7.340
Megan O'Brien
Yeah.
0:38:11.140 --> 0:38:11.300
Mah Jin-Khai
OK.
0:38:8.820 --> 0:38:39.580
Megan O'Brien
Hopefully, fingers crossed we have. I'll, I'll, you know, ideas and and hypothesis are are correct, but I believe nothing's ever perfect. So we'll iterate and and make sure that that's refined, but we'll get to a point hopefully where home is a place that people want to be users find value and you know really do engage with it the way we're hoping and so yeah so that's that's our plan. So Suanne and Keith could you guys confirm with me and once you've gone back to the team's or even just if you really know the answer to this.
0:38:39.950 --> 0:38:53.150
Megan O'Brien
How long we have before you guys like will be, you know needing the first set of components kind of your teams have got you know they need to start working on it immediately. Is that right now or do we have a grace period of a week or so?
0:39:8.900 --> 0:39:9.140
Megan O'Brien
Yeah.
0:38:56.500 --> 0:39:9.180
SueAnn See
Oh, so right now the new screen just started yesterday, so we probably can wait for two weeks as in until June the seven then.
0:39:12.940 --> 0:39:13.140
Mah Jin-Khai
Gener.
0:39:10.740 --> 0:39:16.780
SueAnn See
We will start a new Sprint, so ideally we get a sense of what we need to work on in the next Sprint.
0:39:19.550 --> 0:39:19.710
Mah Jin-Khai
OK.
0:39:26.400 --> 0:39:26.600
Mah Jin-Khai
Maybe.
0:39:17.400 --> 0:39:27.320
Megan O'Brien
Perfect. That's brilliant for us. That's perfect. Yeah. Thank you so much for that. That gives us enough time as well to not rush through it and, like, push whatever we can because I'd rather it be.
0:39:28.920 --> 0:39:36.880
Megan O'Brien
Yeah, it kind of we would do that due diligence and and seeing what we can push through and and feel comfortable with not testing.
0:39:37.0 --> 0:39:45.480
Megan O'Brien
And then Suanne and Keith, you'll just let me know kind of we'll send over what we can and just kind of as we as we get it done, we'll send it over to you guys and then you guys can just let us know.
0:39:47.890 --> 0:40:9.810
Megan O'Brien
How we want to work moving forward so I know we have different ways in which we've worked previously. We're happy to kind of fit into the way that you guys are working and I don't know if you're working in the hall where the tickets are kind of being put, whatever the case is, we're happy to pick that up and kind of just lay that out with you to say, OK, cool. And we aligned this to to what we need to do and how we need to feed it through to you.
0:40:16.850 --> 0:40:17.690
Megan O'Brien
OK, that's fine.
0:40:19.760 --> 0:40:20.40
Megan O'Brien
Yeah.
0:40:12.830 --> 0:40:23.630
Keith Low
The the Dev team are mainly working through through JIRA, but I mean as a product major myself it's more more on uh huh? But then, uh, actually we are dealing more with the dev team, not not myself.
0:40:51.120 --> 0:40:51.280
Mah Jin-Khai
Dele.
0:40:58.30 --> 0:40:58.150
Mah Jin-Khai
I'm.
0:40:51.830 --> 0:41:2.510
Megan O'Brien
What are we working from? You know? So I'm happy to work with you guys and see what's what's best fit. And then obviously the teams can just get integrated and and follow that as normal.
0:41:5.60 --> 0:41:14.340
Mah Jin-Khai
If the platform team implement this component, who who should test this outside? We we we let the platform team to test it, but who should we include in the code review?
0:41:33.180 --> 0:41:33.260
Mah Jin-Khai
Oh.
0:41:15.860 --> 0:41:48.940
Megan O'Brien
Yeah, that's good. That's a good point. So as I said in the team when I sent that document through JK, it said the key stakeholders. So those people on that document. So from my team, it's Bethany. I mean, you don't have to include everybody. But essentially Ryan is spearheading this project from a UX perspective. So he'll need to be in there alongside Matt and Beth will probably be key as well, just from a kind of code perspective. But you guys can choose who you would want in there that are that you know, in between my team, they'll decide who reviews those. But Gavin is also important. So he's more important when it comes to, not necessarily the tasting from a component perspective.
0:41:49.230 --> 0:41:52.430
Megan O'Brien
But as we build out, you know, certain elements within.
0:41:53.790 --> 0:42:9.550
Megan O'Brien
Home we will get a stage where we will want to do our final testing with users to say OK, is this what we want? Is this what we've do? You know what I mean? We'll have to do that final Test or user testing, right? So they'll come later on once we've kind of built majority of it.
0:42:11.150 --> 0:42:20.30
Megan O'Brien
But yeah, I would say probably Matt and Ryan are the veins who kind of individuals that will be involved from a component perspective.
0:42:21.760 --> 0:42:46.480
Mah Jin-Khai
I think the initial first spring if uh team really pick up the recover, I think first thing they need to improve is the maybe I'm not sure, maybe need to make some changes. So the pipeline because the the current storybook, it looks like publish Helix version 2 component if if we decided to stick to a version three or somewhere that probably better to be to have A to have a separate story book.
0:42:48.290 --> 0:42:48.610
Megan O'Brien
Yeah.
0:43:4.940 --> 0:43:5.180
Megan O'Brien
Yeah.
0:43:5.240 --> 0:43:6.640
Mah Jin-Khai
OK, OK. Yeah.
0:43:15.330 --> 0:43:15.490
Mah Jin-Khai
Yeah.
0:42:48.740 --> 0:43:18.300
Bethany Pass
The thing no one's actually using this package at the minute, so I think this like the way I've thought this was kind of working is this is like the next Gen of Helix, so I wouldn't see any. I can't see any risks with us just using this in it's in its current situation because yeah, as I said, the only people that are really using it is arc anyway and they've kind of kept their own branch from it. So this is ready and kind of set up.
0:43:18.780 --> 0:43:20.300
Bethany Pass
To facilitate this project so.
0:43:20.890 --> 0:43:21.50
Megan O'Brien
Yeah.
0:43:21.320 --> 0:43:23.960
Bethany Pass
I think we're happy to just utilise those.
0:43:23.920 --> 0:43:24.360
Mah Jin-Khai
OK.
0:43:23.330 --> 0:43:34.930
Megan O'Brien
Yeah. And Beth has updated all those components, JK so well not all of them, but she's done as she as you can see my list, she's gone through a fair amount and she'll continue to do that. So with you guys, you're obviously able to just assist her and add to that.
0:43:35.810 --> 0:43:36.290
Mah Jin-Khai
OK.
0:43:36.590 --> 0:43:37.70
Megan O'Brien
But yeah.
0:43:37.550 --> 0:43:41.550
Mah Jin-Khai
Do do, do do you know which version they are they are using right now? Is it 2.1 or or?
0:43:43.890 --> 0:43:43.930
Matt Everitt
I.
0:43:43.440 --> 0:43:44.480
Bethany Pass
Wait, who? Sorry.
0:43:45.320 --> 0:43:48.320
Mah Jin-Khai
The the activist. Yeah, the the our product.
0:43:47.110 --> 0:43:56.150
Bethany Pass
So they've yeah. So they've stayed on Helix, they're they're still using the Helix plus package, which was built to.
0:43:55.20 --> 0:43:56.740
Matt Everitt
At one point, something, isn't it?
0:43:57.800 --> 0:43:58.120
Matt Everitt
Yeah.
0:43:57.740 --> 0:43:59.140
Mah Jin-Khai
OK. OK. OK.
0:43:59.670 --> 0:43:59.950
Megan O'Brien
Yeah.
0:44:5.970 --> 0:44:7.130
Mah Jin-Khai
OK, OK.
0:43:56.190 --> 0:44:7.870
Bethany Pass
Like one point something. Yeah. Whereas. But they're not consuming the react call package at all. So we can kind of freely make changes to this without any risk dot arc.
0:44:26.390 --> 0:44:26.550
Mah Jin-Khai
OK.
0:44:7.750 --> 0:44:38.750
Megan O'Brien
And they will move. Yeah, we've agreed with that team that they, they're not in a position to make those changes and it's honestly mine. It's not like in my mind and I think Matt and Beth can agree, they're not major changes. It's not like like where you can like drastically see that there's something it's it's, you know, minor tweaks and changes to certain components, some larger than others, but really nothing that's going to, you know, be breaking. But the ARC team have said, look, we understand that that's in there. We will move to that as we we get to it to move to, that's fine. Cool. We we're happy with that so.
0:44:38.350 --> 0:44:46.870
Mah Jin-Khai
If he if he don't have any consumer right now, I think it's OK to if you to use better the existing one so so this Helix.
0:44:48.760 --> 0:44:54.960
Mah Jin-Khai
My Jen's complaining of I should design on top of you or or or no.
0:45:4.650 --> 0:45:5.250
Mah Jin-Khai
OK.
0:44:56.720 --> 0:45:8.320
Bethany Pass
Yeah, well, so their components in Helix react core do some of them are built using MUI. Some of them are built from scratch. It kind of varies. But yeah, Mui is in this, so.
0:45:9.660 --> 0:45:11.380
Bethany Pass
Is available to kind of be used.
0:45:11.260 --> 0:45:23.500
Megan O'Brien
Yeah. And I mean, it's not entirely like what what they did initially as far as I'm aware is they they basically utilised parts of, you know, memory components, whatever the case is and installed those to be like. So we got to a point where.
0:45:47.910 --> 0:45:48.110
Mah Jin-Khai
OK.
0:45:25.740 --> 0:45:59.300
Megan O'Brien
We had Helix five that or styled those components to match our UI. So now Beth has gone and obviously just had updated those and we've updated them. So they're matching what we call our Helix UI. But yes, I think that they are in, it's basically Helix plus. That's why Matt is kind of steering away from calling it Helix plus because we had Helix Plus which was that kind of combination of Helix and mue meshed into one. That's what core is. But then also with you know what we call in build essentially on top of that. So I'll kind of you, yeah, it's quite confusing but call in its entirety is Helix. That's what we're trying to build.
0:45:58.490 --> 0:46:21.770
Bethany Pass
Yeah, this is just meant to be like, yeah, the reason we created this new library is because we knew that we can't keep building Helix. Plus, because we couldn't, we obviously need to make a lot of big changes. And we knew that like arc or obviously like really enthwined with that. So, yeah, this library has been created to kind of be broken. So yeah, we're happy to move forward with that.
0:46:36.730 --> 0:46:36.850
Mah Jin-Khai
Is.
0:46:21.770 --> 0:46:53.290
Megan O'Brien
Yeah. And we split it because we also knew that we can't have core being the whole of the ark component like a lot of those components are not going to be utilised in other places. So NHC, big, so and too much work for us to go in and change and do all blah blah, we can probably assist as we get you know, go down this journey, but it'll assist the Ark team, but we understand that core needs to be core where we can utilise it across the business. The rest of it will obviously just be use case by use case and more complex, you know components that are specific to a particular product.
0:46:54.320 --> 0:47:1.40
Mah Jin-Khai
OK, so so let's say if we build new component we have to where to review and see if.
0:47:2.390 --> 0:47:9.910
Mah Jin-Khai
Can we use uh? Can we build something a customise based on view? If we can't then we have to be ourself. Is is that still the case?
0:47:10.810 --> 0:47:26.730
Bethany Pass
Yeah. So. Oh, well, that's how I've been kind of working. Sorry, Maggie. I didn't need to jump in, but yeah, like, say, for example, the daytime picker is not using movie at all because of the customization that we needed. So that's been built from scratch.
0:47:28.250 --> 0:47:46.90
Bethany Pass
And things like the Moodle, the content card done from scratch, but there are then obviously the components where it's just quicker to use the movie 1. So yeah, happy for you to like do that work. I think it, yeah. It's just those cases where you can't achieve the level of customization that we really need where I've kind of had to then go back into it from scratch.
0:47:46.760 --> 0:48:12.200
Megan O'Brien
Yeah. And I I just want to add and send it exactly that. I think with Beth and Matt and I, we've we've just come to the conclusion that at the end of the day, we need to, we need to make business scenes, right? Like if it's easier for you guys to utilise a movie component and style that and build on top of whatever the case is to get to achieve the same, you know, result at least as close as we can to that. We're OK with that because at the end of the day, you know, time is money and we we know that it needs to be efficient as well for the developers, so.
0:48:13.520 --> 0:48:24.280
Megan O'Brien
That's why I say it in the beginning. It's called the level of flexibility that we've now realised we need to have is, is, is open to every each instance, whether it's something that you're building.
0:48:24.640 --> 0:48:45.960
Megan O'Brien
For utilising a component that's already been built in, you know home as it stands now or whatever it is, as long as we can get it as close as we can to what we've designed. Because when we design it, we obviously stick to the guidelines that are set within Helix as close as we can and that's where I'll you know, main identity releases, how we design it is obviously based.
0:48:46.40 --> 0:48:55.720
Megan O'Brien
Search discovery and then our Helix UI and kind of you know those behaviours that sit within that around the UX. So what I've said to the teams is that we need to assist the developers in creating.
0:48:56.140 --> 0:49:16.940
Megan O'Brien
In hand in any way we can, but also give the developers the autonomy to say, OK, fine, we're going to get as close as we can to Helix and make sure that we can standardise certain components like the core components. But the rest of it, if you want to use MUI or you want to as long as we can kind of make it, you know look and feel and behave what we've designed that's we'll be happy.
0:49:18.270 --> 0:49:18.750
Mah Jin-Khai
OK.
0:49:18.260 --> 0:49:21.620
Megan O'Brien
'Cause, that's not always the case, you know? And and we understand that so.
0:49:22.920 --> 0:49:26.240
Megan O'Brien
Matt, do you have anything that you want to say on that? Because I know that's what we've discussed.
0:49:41.30 --> 0:49:41.150
Mah Jin-Khai
Huh.
0:49:25.320 --> 0:50:1.960
Matt Everitt
No, no, no. It's it kind of exactly that. In terms of movie components, I don't think there will be too many more opportunities to utilise those components because the ones that have been developed so far, you know they are have been built off of mowing. They're just looking at kind of specifically the core ones right now you're probably talking select drop down ones and maybe a search bar, but but outside of that you might struggle to achieve the Helix design using those mirror components. Again, I'm happy to be wrong and you're more than welcome to give it a go. That's absolutely your decision but.
0:50:7.110 --> 0:50:7.350
Mah Jin-Khai
Oh.
0:50:9.950 --> 0:50:10.830
Mah Jin-Khai
Yeah, no.
0:50:16.860 --> 0:50:19.260
Megan O'Brien
To its extent, yeah.
0:50:2.560 --> 0:50:25.800
Matt Everitt
I think kind of given the the difference in design and because Mooi is quite a limited library at the end of the day Mooi is kind of a core library in itself, isn't it? So I think that at this point we have kind of utilised Mooi to almost to its full capability. But but again completely happy to be wrong on that one and you're more than welcome to use Mooi if you see it necessary.
0:50:26.630 --> 0:50:26.990
Mah Jin-Khai
Thank.
0:50:45.270 --> 0:50:45.390
Mah Jin-Khai
Hey.
0:50:50.310 --> 0:50:50.470
Mah Jin-Khai
OK.
0:50:25.980 --> 0:50:50.860
Megan O'Brien
And Jacob, this is this is like a bend Inflexion, both teams right, like we're super happy to say jump on a call with the developers and say cool you know they they would be like OK we want to use this and this and this if you can style that and get it as close to our design as possible like by all means we're we're OK with that, it's just abandoned. It's just kind of that that you know collaboration between teams and saying cool. Let's work towards the same goal of trying to make this as best as it possibly can be.
0:50:52.790 --> 0:51:7.390
Mah Jin-Khai
But based on my experience, it will be so easy to be customised because it's no no matter how the whole look and feel for meal and Helix is designed by two difficult people. So in that it's gonna be very challenging but.
0:51:8.510 --> 0:51:23.630
Mah Jin-Khai
Just just do. Do you know how many components right now in Haley's call building on top of mail and customer on top of mail, I I just curious like in the long term, should we just just build everything ourselves instead it be a lot easier like for sure just a just a thought.
0:51:24.340 --> 0:51:24.380
Megan O'Brien
M.
0:51:28.210 --> 0:51:28.730
Matt Everitt
Yeah.
0:51:24.940 --> 0:51:54.780
Bethany Pass
Yeah, I think me and Matt were kind of having this discussion like 'cause, we've been to a few talks now from like people working on design systems and the industry as a whole is kind of saying you build these design systems using like Mimi 'cause. It's quick, but eventually you'll have to go back and untangle all that and do it all yourself from scratch. So if we have the time and the resource, I would like, I'd personally feel like eventually we're going to have to go back and do it ourselves anyway. So if you can do it.
0:51:55.20 --> 0:51:55.220
Matt Everitt
Yeah.
0:51:55.420 --> 0:51:56.300
Bethany Pass
From the start, then.
0:51:53.510 --> 0:51:56.430
Mah Jin-Khai
It's OK.
0:51:58.460 --> 0:51:58.660
Megan O'Brien
Yeah.
0:52:3.830 --> 0:52:6.790
Megan O'Brien
100 percent 100%.
0:51:57.40 --> 0:52:7.880
Bethany Pass
Why wouldn't we? But yeah, obviously up until now, I feel like it's always been that kind of like time resource. It needs to happen yesterday. So I think that's where that's come.
0:52:4.710 --> 0:52:20.670
Mah Jin-Khai
OK. Then you may maybe if you got time maybe find out how many couple using build and I am judging between like resources as well be if if you needed to let's say example right if the mygen needed to.
0:52:33.650 --> 0:52:33.970
Bethany Pass
Yeah.
0:52:39.570 --> 0:52:39.850
Megan O'Brien
Yeah.
0:52:22.70 --> 0:52:40.230
Mah Jin-Khai
Use some of this component and needed to customise and then he's is. I mean we can just take the opportunity to build something from using react and don't use mu. Maybe it'll be quicker in the end because it doesn't need to tweak and turn customise and do a lot of. Yeah that is my feeling.
0:52:41.450 --> 0:52:41.690
Bethany Pass
Yeah.
0:52:51.500 --> 0:52:51.740
Mah Jin-Khai
Yeah.
0:53:0.320 --> 0:53:0.480
Mah Jin-Khai
And.
0:52:41.270 --> 0:53:9.390
Megan O'Brien
I mean, in an ideal world, I think basin Matt would agree that if we could create our cool library, essentially we're creating our own movie, right, like we create, we're building like our own. So that that that's the whole point here essentially. And I mean we we would love that, but we've often been told, you know obviously we need to bend and flex to to make sure that it's feasible not only for the time constraints and budgets, but also the resource available to do that. So yeah, Jacob, that would be I think our first prize wins.
0:53:11.900 --> 0:53:12.100
Bethany Pass
Yeah.
0:53:13.550 --> 0:53:14.150
Bethany Pass
I would say.
0:53:10.290 --> 0:53:16.490
Mah Jin-Khai
I think I didn't need to. Yeah, that's high level. Just just just curious like how many, how many, yeah.
0:53:21.510 --> 0:53:22.910
Mah Jin-Khai
9797.
0:53:16.780 --> 0:53:22.980
Bethany Pass
Yeah, I would say like around 90% of them are using it at the minute. It's quite yeah like.
0:53:24.310 --> 0:53:26.350
Mah Jin-Khai
It is it's, it's got a lot. It's got a lot.
0:53:27.970 --> 0:53:29.370
Mah Jin-Khai
Yeah, if you.
0:53:24.300 --> 0:53:32.20
Bethany Pass
Hi there. Yeah, it's quite it's. It's a lala. Yeah. Yeah, yeah. Because obviously we just branched from Helix plus and they were all using them.
0:53:31.460 --> 0:53:32.20
Mah Jin-Khai
OK.
0:53:34.0 --> 0:53:34.160
Mah Jin-Khai
OK.
0:53:33.580 --> 0:53:36.140
Bethany Pass
And so I've literally just updated what was existing, but.
0:53:37.700 --> 0:53:40.180
Bethany Pass
Yeah, looking at the.
0:53:36.610 --> 0:53:42.130
Mah Jin-Khai
And and he will. He will get harder and harder because you when you.
0:53:40.220 --> 0:53:48.900
Bethany Pass
Yeah, exactly. And like looking at the Mygen prototype, like a lot of I think a lot of the stuff that's in there can be created from the components that we've.
0:53:49.940 --> 0:54:3.60
Bethany Pass
Like already got like the content card is so flexible 'cause you just like put whatever you like. It's just a wrapper, really. For whatever's in that, so it doesn't feel like loads of new stuff needs to be created. But yeah, maybe this is our opportunity to go back and.
0:54:4.260 --> 0:54:6.420
Megan O'Brien
We're fine. Yeah, exactly.
0:54:4.380 --> 0:54:6.860
Bethany Pass
Most like refine again, yeah. What's existing?
0:54:8.470 --> 0:54:37.630
Mah Jin-Khai
Yeah. When we when we come to each component, we can, we certainly can can then discuss a bit. I also do want the team to build something on spend weeks just to build component, but in the end the ROI is like oh, that's a component, maybe we can we can we can discuss a little bit. I just worry about MIMO upgrade because normally when you use a third party library you try to customise it when you are going to a latest version or something, most of most of the broken and gonna be very difficult so.
0:54:38.850 --> 0:54:41.370
Mah Jin-Khai
So I I don't, but that will be the drop in.
0:54:42.330 --> 0:54:42.650
Megan O'Brien
Yeah.
0:54:44.100 --> 0:54:45.500
Megan O'Brien
OK, perfect.
0:54:47.340 --> 0:55:5.700
Megan O'Brien
Alright, so we I think next steps then. Thank you so much, Beth. Honestly, just amazing work as always and thank you JK and just the rest of team for being willing to assist Beth and Matt in kind of their journey on on kind of getting core to where they want it to be and where we want it to be and where we where essentially you guys need it to be.
0:55:7.900 --> 0:55:29.860
Megan O'Brien
So next steps just from a platform perspective, Jki obviously have mentioned that the team already working on that. So we'll utilise the next week or so and hopefully have that ready sooner than you know two weeks. So that we can start to just push that through, make sure that we work with the likes of Srian and Keith and the rest of the team on on the school just to make sure that we are aligned to the ways of working and fitting into that.
0:55:31.140 --> 0:55:37.380
Megan O'Brien
And then I think working closely with Beth is going to be really instrumental moving forward. So as you guys can see what you can utilise from libraries.
0:55:37.780 --> 0:55:54.780
Megan O'Brien
What you can start to build to add those libraries and then what we still need to do moving forward from there. So yeah really exciting and and I hope kind of I've encapsulated all of those Agnes kind of steps and actions correctly. Does anybody else have any final kind of feedback or?
0:55:56.290 --> 0:55:57.290
Megan O'Brien
And they wanna enter that.
0:55:58.520 --> 0:56:13.120
Bethany Pass
I'm just thinking like to get prepared and stuff. Would it be useful if I could have like a list of the people that you want to have, like access to the new Helix Realcore repository and I can start getting them all set up for like read and write access to that as well.
0:56:14.590 --> 0:56:14.870
Megan O'Brien
Yeah.
0:56:16.80 --> 0:56:16.800
Megan O'Brien
Good chance.
0:56:18.620 --> 0:56:20.980
Megan O'Brien
Take it. Will you be able to provide that for us?
0:56:22.60 --> 0:56:26.540
Mah Jin-Khai
Do you mean the the list of Sir or the the list of users?
0:56:25.560 --> 0:56:31.720
Megan O'Brien
The key the key the key stakeholders that will need access to the libraries. So developers.
0:56:33.340 --> 0:56:37.340
Megan O'Brien
Individuals and different stakeholders that you think would need just in that to be.
0:56:36.210 --> 0:56:43.290
Mah Jin-Khai
I yeah, I I will. Yeah. I will create a loop paragraph here. Maybe I need parking and sued to.
0:56:51.800 --> 0:56:52.200
Bethany Pass
Yeah.
0:56:44.830 --> 0:57:0.30
Mah Jin-Khai
So so headings assess who who need heading. Assess. Right. So yeah, that could be cutting would be the best person. Karin, can you fill out your team's name here? And maybe I think the product owner needed to know as well. Yeah.
0:57:1.330 --> 0:57:1.810
Kar King Siew
Yeah, sure.
0:57:3.510 --> 0:57:35.990
Megan O'Brien
Yeah. Last question I have is just I think Keith, Keith, will you create kind of AI don't know. Do you want me to? I can I can happily create kind of a UX chat like we've done before on teams. I don't know if you want to do that just so that we could have a centralised place where we can obviously outside of meetings you know share some feedback or or any kind of you know questions or whatever the case that we might have or you guys might have and then that that may just also ease the efficiency of of working together moving forward.
0:57:36.270 --> 0:57:45.70
Megan O'Brien
So you know, a lot of the time a lot of us have many meetings in the calendar, so it might just be useful for my team as well. We've done it with a few other different.
0:57:45.110 --> 0:57:51.270
Megan O'Brien
Products that fall within the business line is just to make sure we're all aligned, I suppose, and have that open kind of.
0:57:51.240 --> 0:57:56.400
Keith Low
Yeah, yeah, sure. I can create it. But uh, who? Who do you? Uh, would like to be in this uh group.
0:57:57.350 --> 0:57:57.990
Keith Low
I mean.
0:57:57.160 --> 0:58:15.800
Megan O'Brien
Yeah. So I can send that to you, Keith. It's it's on the document that I originally sent to you guys, but it's basically just those key stables. But I'll just send you the names and you can just add the individuals from my side and then obviously everybody from from your guys side, from a platform perspective. And then it's it's nice for my team to also have direct access to exactly who they need to talk to.
0:58:16.810 --> 0:58:18.690
Keith Low
Mm hmm sure. OK.
0:58:18.320 --> 0:58:20.720
Megan O'Brien
Perfect. Brilliant. Thank you, guys.
0:58:21.720 --> 0:58:22.640
Keith Low
Gary, thanks a lot.
0:58:24.200 --> 0:58:24.680
Bethany Pass
Problem.
0:58:23.800 --> 0:58:24.760
Matt Everitt
Cool, right, Prince?
0:58:23.570 --> 0:58:33.610
Megan O'Brien
Thank you so much, everybody. Thanks, Beth. I really appreciate it. And thanks to the team for, for, yeah, the kind of time that you've given us this morning, really appreciate it.
0:58:34.900 --> 0:58:37.940
Keith Low
OK. Thank you. Thank you. Bye, bye.
0:58:36.420 --> 0:58:38.660
Megan O'Brien
Have a great day. Thanks guys. Bye.
0:58:36.570 --> 0:58:39.130
Keith Low
Later bye. Bye. Cheers.
0:58:36.780 --> 0:58:39.300
Yip Fan Wong
It does. OK, thank you. Bye.


extract all the points in the meeting as per transcript. Also list down the next steps required. Go as detailed as possible.