 yw'r cyfrantau cyfrantau, dwi'n credu fydd yn y rhaid. Mae'r ddweud yn John Enw, rwy'n gwybod i'r ddysun, mae'r ddysun o'r agensiol, mae'n ddysgu'r ddysgu'r ddysun. Rwy'n gwybod i'r ddysun, mae'r ddysun i'r ddysun i'r ddysun, yn y ffair o'r ddysun i'r ddysun. Felly, rwy'n gwybod i'r ddysun i'r ddysun i'r ddysun. Felly, mae'r gwybod yn session, mae'n mynd i, a dymuno i'r ddysun y Troporol Carlos i ni, a i'r ddysun ancia, oedd yn Ashwyl Eich yn y ddechrau yn gyffaporeill. Dwi'n bwysbeth fod yndog, a ar ddence revelationet yn Llyfridog. Bued y cryr a'i bobl yn graws, am y tro o Anglesis ac Arctic Rerich Red pushing. Felly, mae'n ben 말고 yn cael patientsar slumu loads. A hynny, a gweld wrth Mynd ti'r cyfrifyddy i ddweud cyfrifyddy i ddefnyddio y sgol i'r eich drwsgol, a dwi'n wneud mewn y gweithio am y frontend yw'r sefydliadau gan y frontend, a gallwn ei chwyl i'r frontend yn y bwyddiol a'r cyfrifyddynt i g colleagues ac mae'r cyfrifyddynt i ddefnyddio'r frontend o hyn ar y frontend o'r cyfrifyddynt, ond byddai'n gwybod, gyffredig mewn cyfrifyddynt o fynd sydd yn dweud y frontend o gyfrifyddynt. Mwneud hynny i gydadaeth o'ch byddun o'r driffyn o'r tenfodol ein adroddur wedi'u bod yn gwneud â'r astud oedden nhw'n gwirio. Mae'n meddwl i'r oedd sydd wedi gweithio ffordd o'r poolad yn gwneud hynny i gyd. Mae gennym gorau ond i ni'n gweithio. Mae'r gweithio'r ddeunio i mynd i ni. Dyn ni fydd wedi gweithio'n gweithio a'u gwestfynNog yn dwi'n golygu'r awdd. Mae'r dwylaid sy'n tyfu iawn, mae'n swyddog o'r newid yn fwyadech ar wathrif o'r ddedg a'i wneud dod i wneud ynol â'r ddweud. Roedd yn lle oedd ydych chi'n ei gweithio'n gweithio, ac mae'n dod i chi ddweud ar y fantau. Yn gwaith o'r cydwyddiadau, o'r ddiwedd o'r ddiweddol sy'n dwylo gyda'r dddugos a'r cydwyddiadau a'r ddwylo cydwyddiadau, ac yn ymgyrch chi i'r ddweud o'r ddiweddol â'r cydwyddiadau, felly dyna'r cydwyddiadau yn y lluniau lluniau. Yn gweithio, yma yw meddwl yma. Yn ymgyrch ar hyn, mae'r cydwyddiadau yn y meddwl. Yn dweud hynny mae'r ysgrifennu要an o ddod o diolod ar awr, nywedol yn ddweud yng Nghymru i'r teimlaes sy'n arnyn o'r pAAGE. Felly mae'n storient gwahanol ac mae ditherdau'r anghariaeth a phanol o'r llangog ac mae'n dillwedd yn ddylai'r hynny, nad yna'r ymlaen cyd Inside. Mae gweithio'r pAAGE yn ei d Hooker, neu mae'n gweithio, wrth gweithio'r hwn mae'n llawddio'r pAAGE. Felly mae'n ddim yn byw o'r cyfeithio'r holl o'r pAAGE. We want to try to change that approach. This is a quote that we've seen in a number of places, Steven Hay. We're not designing web pages. We're designing systems and components. I think this is the approach that FrontEnd would like to be able to take. That we're talking about the domain in terms of the client's domain. And that we're building components that make sense for the client. At the same time, the thing we're actually building, the web application itself, is primarily a user interface. Oes o'r ddweud o ddlefnodd y gweithio ddechrau o'r ffwg ysgol yw ddweud eich sgol, o'r rhai'r sgol yn dda, o'r ddweud eich ddweud o'r ddweud eich rhaid gan fynd yn ddweud a'r cyfrifiadau i'r Systemau, yn ystod o'r gweithio i'r cyfrifiadau i'r gweithio. O'r ffordd hynny, y cyfrifiadau a'r ddweud eich ysgol yn oed yn y webbion, ac yn y ffordd hynny yna mae'r ddiweddio'r cyfrifiadau. y dyfodd wedi byw yw'n fawr gofo chciw, a yn dda nhw'n siŵn cymdeithasol i'n mynd i i gyda chymo'r ddweud ymlaen yma'r hefyd, a'r llychyn o'r dda'r ffrwstiant llywedd yma yng nghymru. Rydyn ni'n cyfnod o dda i chi eur, w nad yw'r peth oedd eir unrhywg taeth os yna ymdilyw unrhyw o'i awdurdod rwy'n cyffredig sy'n gweithio'r ddechrau'i gilydd i'r dwylo. o'r component elders am bobl ac mae'n rhaid o'n rhyw baston rhai ond y flynedd ac rydyn ni'n Ethioshima, a cael y cyrolygu eff talented o base byddw yna'r plan crynid Renwarth Use Mirror P consistduًn dd Sean E claygyneth ar yn amlwg, ni wnaeth yr penderlaeth favourite cyllid bobl yn gweithio'm dda, So, y fathon ni o bwys pwynd gwaith. Mae'r fathon ni o ddadw am hwnnw, mae'r mwneud o'r fathon wahanol, mae'r fathon ni o bwneud, mae'r mwneud o'r fathon ni o ddadw am gynnig a'r mwy sefydling. Yn gwirionedd rygwun'r rangyfl ar g夫, mae nid yw'r fathon ni o ddweud. Mae'r ddweud o ddweud a gondall y interpret yw eu maen i wneud a mae'r rhan o fod yn iawn sawl yn ddeud i gydig ar gydig ar gyfeill ymddangawr. Felly, nid i'w ddweud y rôl yma y maes ar dda i'w ddweud yma, ac roeddwn i'r rôl yma sy'n credu'r gweithio'r bobl yn ymwrth�l, ond ond, mae'r bobl yn dweud yma, ac mae'r bobl yn unwyddiad o'r bobl yn ddweud yma yn ymwrthwynt yn ymwincio'r gweithio'r bobl, sy'n golygu'r ymwincio'r pannol cyfrifetau. Ac o'r nifer o ddau'r panell yn ddod o'r ddau'r gweithio i ddim gynnig i'r eich larchor, yn fwy o'r ddau'r ddau'r ddau'r ddau. A'r proses yw'r frond dynedd, oherwydd, yn ddod o'r ddau'r ddau, yn ddau'r ddau'r ddau, i ddim yn HGOL a CSS ac i ddau'r ddau'r ddau'r bai sydd wedi gydag o'r ddau'r ddau'r ddau'r ddau'r ddau'r ddau'r ddau'r ddau'r ddau'r ddau, Oni'r gwybod ychydig yn ystod chi'n ddysgu ddechrau o'r ffordd y Cymru yn ysgol. Oni'r gynhyrchu'r gwybod ar y ffordd, y pethau, ac y dywedig yna ar y cyhoedd. Ym mwyaf ar gyfer, ac ym mwyaf ar gyhoedd starg fod yn y ffordd. A ym mwyaf ar gyhoedd starg yn y ffordd, yn ymwysig ar gwybod ym mwyaf, yn ymwysig ar gyhoedd ei ddweud, yn y gwisifio'r gweithreduol, Bring in the design and the development teams together so we can all look at these things and try to understand what the individual parts of the website are. So as well as a tool to break down the user interface components into its component parts rather than just thinking about it as a whole or as a series of pages. Of course they also serve as the resource for new designers and developers to locate existing patterns in the future. That website there, styleguides.io is a collection of style guides that other people have produced. It's a really useful resource to go and have a look at and get that kind of inspiration of what these style guides are. Particularly good style guides as well as defining those base patterns. They also start to demonstrate exactly how the code is going to work with each of these elements. It also describes the purpose of each of these elements as well so you can understand what these things are and how they're going to be used in the future. You can even extend that even further and start to actually talking about them as something that's useful to the content editing teams as well. So that they can look at these things and understand not only the purpose but perhaps the tone of voice that should be used when they're being used. So that's kind of an overview of the process. I guess I haven't looked at the atomic design principles as a particular place to pick up some of this information. Now I just wanted to go through how this actually works in practice. I haven't looked at how you might fit it into an application development workflow like a Drupal build. So this is probably a typical place that we were at a few years ago where you'd have a sort of waterfall pattern. You'd start off with some people doing some UX work and then the output of that phase would be some wireframes. Those wireframes would be passed to the designers who would then transform those into colour PhDs, but full page designs and those would eventually be passed down to your application development team who would then be told here's the beautiful designs you've got to go and build them. In the case of a Drupal build this usually means kind of installing Drupal, getting Drupal to a point where you can then create your nodes and your various elements of the page. So you get things to as close as you can to those designs and then you start theming. The Drupal theme is kind of an exception there. I want everything that Drupal does apart from I'd like some different CSS and different styling in these places. So we're overriding what Drupal does in each of these points. We kind of wanted to be close towards was actually saying can we take the front end out so that we can produce these HTML style guides. So we've got these HTML CSS guides that allow the front enders to work in isolation of the back end. So it adds this extra layer into the process. So UX produces wireframes, designs producing their designs and then front end producing their HTML CSS style guides and then your application development team have then got something they can work on. So their process is still pretty similar. But front end now has been freed from whatever that back end technology happens to be and they can now try implementing these things inside of, on their own, on their own models. When you free that then you get a slightly different approach to actually, rather than that waterfall approach, what we can do instead now is have an approach that looks more like this where the project timeline goes along the bottom and the initial phase of the project UX is spending more time on the work and the design can get involved a little bit earlier. Front end can get involved a little bit earlier and the application development team can get involved a little bit earlier as well. So you have, instead of having those kind of strict sign-offs, we can kind of morph and evolve the solution as time goes on. So I think one of the things we were finding is that we were saying we were an agile delivery team but realistically the only agile part was the last part, the application development. Once all of these things had finished, they had a clear sign-off in between each one and then we started the application development. But this is where we wanted to be. So under the way this works in practice then is that there will still be that UX phase at the start. There will still be wireframes produced but the UX team needs to be thinking in terms of components. So they are actually building, rather than thinking in terms of pages, they themselves, the UX team are thinking in terms of components and so they're kind of building blocks on the page and these blocks need to be given names. So they're actually defining it at that time. So we go, yeah, here's the wireframe, here's a pattern within that wireframe. I suppose it's not coming out very well on the slides. But there's a pattern within the wireframe and that pattern has got a name, it's got fields and these fields are defined and this is the team defining these elements. So this isn't UX person working alone, or UX on the designer, but there will be a developer there as well and front-end will be thinking about it all together. One of the critical points of this phase is naming the components so that we all have an understanding of what these components are and what their purpose is right from the start. And if possible, you can then get in the flow. So we're a distributed team, so we're doing this on a wiki and if you're co-located, you just do this on the wall in the office and everyone can kind of look at it and grab things and understand what's going on. But we have wiki pages which exist for each of these components. We're defining the components collaboratively, we're giving them names and then, because there are individual things, they can be given jurid tickets and they can be tracked through the process. So whereas before our front-end process might have been and our design process might have been a bit ad hoc where people would design things, showing the client things, showing the client. This time we can actually say, well, this component needs designing and if you get good at this and over time it's possible that you can get to a point where on the right-hand side here we've got the top, we've got the wireframe, underneath we've got the designed component and then at the same time evolving the solution, the front-enders in pure HTML and CSS are constructing a web page which is also evolving as the design solution evolves. So they can take those elements as wireframes to build the components but just grayscale and then if the design is completed they can come back and start adding the details of the design into the front-end. This is quite a difficult thing to manage, mostly because the clients are going to want to see that they like the sign-off points, they like those points in the project, they say like, yes, now a design is finished now let's move on to the next thing but as we all know that's not really how projects work because design will evolve over time anyway and we can get to a point where we can convince the clients that yes, it's important to get some direction so we'll have maybe one or two page designs that are finished but we can get into this kind of iterative build cycle earlier I think it's better for the project it means that things can evolve a lot quicker. So that's the evolving solution that we can imagine this starting to be produced but at some point it also needs to then flow into Drupal so once a few of these components are ready the Drupal back-end is because they'll also have access to those same wiki pages they'll be producing the Drupal assets and then we need to then integrate the two things so what's coming out of front-end is HTML, CSS, JavaScript, some static assets like images and these things now need to be integrated into your into your Drupal theme and one of the problems with the static style guide is you've now duplicated effort in some situations so you've now got HTML in your static style guide and you also have your take templates inside your Drupal theme and these are two separate things and this is a big problem for us so front-enders are maintaining HTML over here in the static style guide but your Drupal people are maintaining take templates over here and over time these things diverge and as the effort required to maintain your application increases and the demand for new features increases the style guide quickly becomes out of sync with the Drupal application or whatever the back-end application happens to be it comes out of sync with it and it stops being useful as a tool anymore and one of the critical reasons for having a style guide at all is not as a a nice styling just to show off the design features of the site it's a critical part in collaboration and it's also a critical part in what happens when new people come onto the project trying to get that overview of exactly what exists on the site what things are there and how they're supposed to be used so it's important that your style guide is kept in sync with your Drupal theme and doing that is going to be a reasonably large administrative effort if you have to copy from one to the other so what you really want to do is get to a point where all of these squares on the left hand side are the same squares as on the right hand side so that when a change is made to the style guide it reflects inside a Drupal and if a change were made inside a Drupal the same thing is going to happen the style guide would update automatically so your front-enders can still live in the style guide they can still live outside of the application layer but your Drupal developers can also be involved in the maintenance and evolution of the front-end components as well so these are called Living Style Maintainable Style Guides I think is the correct term so with that in mind we're just going to have a look at some tools and approach so this is the approach we've come up with and I'll just go through this so this is looking at code and structure of the project so I'm looking at a Drupal theme here this is a 7th theme out of Drupal 8 and the way it kind of looks at the theme as I was mentioning before is that I mean it's still separating it's still separating elements of the front-end out by effectively by file extension so you've got a JavaScript directory there and all your JavaScript lives inside there as a CSS directory and I think if we open that up you'd see that there was a Components folder but inside the Components folder we've got a separate CSS file so again the CSS just lives on its own and then the static images and that templates folder is where your HTML effectively exists your templates so your templates, your JavaScript, your CSS, your images they're all separate they're all separate from each other and conceptually we want to think about things in terms of components so we want to have everything that's to do with the same component living together because it makes it easier to reason about so this is the approach we'd like to take at the top there we've got a button this is our simplest component one of our simple components inside of our source directory there we've got a Components directory and inside of that we've got a component called button and the button has HTML associated with it CSS and if there's any JavaScript there we have JavaScript in there as well so you see things are corrected together they're easy to reason about everything to do with a button and so looking inside looking inside the template file there you see that inside that trig template file there's just a simple button or a markup and we can take this one step further with the idea of a molecule so this is the component that's composited of other components and again this is just a this thing will have a name so I think this one's called an item info feature that was a name decided on by the project team and it's carried through so we see the name inside of the wiki we see the name inside of the front-end code and we'll see the name inside of Drupal as a thing that exists and that continues on so an organism if this happens to be one and the way these are cut up they're just for the purpose of the demonstration like the way that you would actually cut them up would depend on your projects the idea again is the same we've got an element composed of sub elements inside it and this thing can exist on its own as an HTML entity and it can also exist inside of Drupal so the funny thing is how do you bring these templates inside of Drupal so the front-end process we've put together which has that file structure you saw earlier each of the each of the components has SCSS, it has HTML templates inside it, twig templates and it has JavaScript as well we have a bold tool which goes away and loops out all those components and creates a single CSS file a single application JavaScript file and a folder that's full of twig templates so it pulls them all together and separates them out in the way that Drupal wants to see them and then we just simulink that into the Drupal theme so this Drupal theme is called DOM and inside this our theme file we've got a hook theme implementation and effectively that hook theme function we're running now is built for us by our build process but all it's doing is providing a theme definition for each of those templates each of those components and so underneath we've then got an example of how we would then it's just a simple example of how we might use one of those components inside our Drupal theme and how we would use any theme function theme template file so I just had a question which was is the text being set directly in the template file this is just a really simple example and this is a pre-process function so you do whatever you want here at this point what we're creating here with the hook theme is just a theme there are a series of theme functions as you'd create anywhere so how you use them how the Drupal developer uses them is completely up to them this is a really trivial example just to demonstrate how it's an example of how it might be used but the parameters you pass in here are for you to change and define you're in Drupal now so you can use all Drupal's functions and functionality but yes all we've done is we've created a whole bunch of components in HTML, CSS the front-ender doesn't know anything about Drupal they've just defined things how they want to and we've brought in those templates in a way that Drupal understands I know it's on the timing process so we're going to make some of these things available so you can have a go with them with some instructions so we're going to be doing some of these in the next month the tool chain underneath is using word pack front-enders in the room might be familiar with Gulp or Grunt a similar tool but it takes a slightly different approach and if you haven't looked at it before strong way to suggest you do because it's quite an interesting way of bundling your module so it allows us to do what we've been trying to do which is to see all our assets iechyd o'r sorg fawr i gael ystafell hynny, ac maen nhw i'r sorg fawr angylchedd eu hunain. Felly, y gallwn gennym, y RWC yn ryeidydd, ac mae'n ddiddordeb bod yn oed. Mae'n amddangos ymddangos saig ei fwy oedd ac eich мира eich rŵn, mae ei ddweud o'r problemu, ac mae'n gwneud o'r dyfodol gan maen nhw'n rhywbethol can you can agree on disagree with the approach taken. But that decoupling of the user interface elements from the application development allows your front-enders the freedom to rapidly iterate over the design and to start building things out much much more quickly and also allows them to build things like the static style guides or the maintainable style guides, which really help with the understanding the conceptual understanding of the system as a whole and the front end system as a whole. Ie, bydd y bwysig ginwch gan gweithio Plasus ydw i gyntaf i ddweud cael cyfle i'n dweud y cyfle a gweld rhywbeth yn y cyfnod. Do rydych chi ddweud gwahanol y gallai ei ddweud ei wneud, yr ystod o gwell fyddai y byddai yn cyfnod y wahanol. Fyw ddweud o Rice ond o єn gwyllteol i gydag o wahanol. Sabaeth oedd gweithio i gydag o'r hawdd yn gweithio wedi'i gynnydd arall. ac mae gweithio gydag i ni gynnal fod yn gweithio'r unig mae'r ddweud yma, yn dda'r unig mae'n gweithio'r unig a ydych chi'n ei ffordd a ydych chi'n gwneud i gydag y cyfnodol. Mae gwahodd o'r ysgrifennu i gydag y gwaith o ôl, yn y cyfnodol, yn gweithio'r unig. Felly, ddau i chi i'n gweithio. Felly, dyna ar ddiwedd yr wych yn amlwg chi'n gweithio? Felly, dwi'n gofyn o'r pwysig. Felly, iddyn nhw'n cael ei gwrsio ar gyfer nôl ymddylch yn ymddylch. Felly, ychydig o'i oedd yn cyfwyr o'r cyfrifnig o'r cyfrifnig ac oedd yn cyfrifnig o ddwyfodol yn ysgrifennig ac mae'n gyfrifnig o'r cyfrifnig o'r cyfrifnig. Mae y proses rydyn ni'n gwybod o'r llwyll. Felly, mae'n ei ddweud wedi'u ei cyfrifnig wedi'u gweld o'u llwyth. Felly, mae'n ddweud yn cyfrifnig o'r cyfrifnig. y gallwn ni wedi gweld y targedd arllun. Rwyf ar y ffordd y dyfodol, mae rhan o'r rhan o'r syniadau ar y ffordd yma? Mae'r targedd yn ei ffordd, rwy'n ddigon o'r modwl ydym ni, ac mae'r targedd yn adeiladu'r modwl... Sry? Y modwl yw'r modwl yw adeiladu'r modwl. Mae'r targedd yn adeiladu'r modwl yn adeiladu'r modwl. Felly, y dyfodol mae'r modwl yw'r modwl yn ddewch yn edrych i ddweud y modwl yma. o'r ddamplau mwg yw'n ddigonol? Cymru. Felly, peir o'n ddamplau'r gwahanol, mae'n bod na iswr i fynd i ddau o ddain o brwyntiau ond nifer y ddweud o ddim yn y mynd i chi felly. Rydw i'n cael ei bod yn dweud ar gael darllwyr eich ddweud ac yn credu pa wahanol o'r ddamplau sefydlus? Rydw i'n chi'n fwyder, dwi'n credu y cwmpozaethau? ac fibreoedd wedi amdano y dweud o gael eu gyd, ac yn amlwg gyrraedd gwerth gyrddiaeth. Felly, sef i'w geitio'r p weet тыrf sodau i gyd ymgyrchiol a'r pataen sydd wedi gyrddiaeth pataen mae'r pataeth. Felly, fel yw'r pataen mwyaf, mae'r byd eioshod yn gyd i gynhyrchu'r borew. Felly, mae'r byd eich pataen mae'r byd i gyrdd, mae'r byd eich pataen, mae'r byd eich pataen, mae'r byd eich pataen syth y gallwn i gyd. First level. I mean what you're actually creating as a render array, with something large at the top and small underneath. These are the sort of things you'd pass through and it's a very programmatic approach to how you do it, so if you're used to building things, if you're used to building Drupal sites, building UI, this approach isn't going to be immediately obvious how you would go about using it. But this is, in order to get that data into your node template you would use a node preprosess function and you would sy'n gwybod ei ddatblygu'r ddau'r wneud yn y rhai format bwysig i fynd i'r newid ymwylliant. Cydur wedi bod yna arweinyddio ei ddylch. Yn ymryd ystod ym Mhwy, ystod y gallai ymweld i'r newid. Ymryd ystod ymweld i'n gwybodaeth ymwylliant, mae'r dweud ystod yn ôl. Yn ymwylliant, mae'n gwybodaeth ymweld i'r newid ymweld i'r newid ymweld. Mae'n gwybodaeth sy'n ei ddweud o'i ddweud ymweld i'r newid. there's tools out there that will produce you a style guide from CSS, but we prefer to take the approach of crafting that style guide because it's quite, because it's so important, I think it needs to be that but it's no more than just saying, well you've got that list of components, it's just another page that says, it just lists the components one after the other and just embeds them in with some dummy content, so you have it. It's using the same two attempts but it's done in the front end rather than in Drupal, so yeah. but you are the same template, it's just there's a there's a page that kind of pulls it all together but it's ultimately just pulling in those templates. Any questions? Concerned that we use the patinaff floor to draw this bit of ages and lots of work to work on accessibility, I think that's still worth it to context your links or to pick up these examples available. Have you had any issues with making tools available Mae gwaith y cyfnod yr un wedi bod yw eich beth bwrdd yn ei wneud yn cael botel yn werthiau a the druple adro i ei ddweud sy'n ei ddweud yn y cyfrähwch yn diodol. Dwi'n edrych i'r cyfrhwyr deabod. Dwi'n edrych i'n ddweud. Mae'n ein bod yn todos yny'r ddweud yn dweud ei teulu gyda'r ddweud. Mae'n edrych i'n ddweud am y ddweud yno. Mae'n edrych i'n ddweud am y ddweud, mae'n edrych i'n edrych i'n ddweud. prevents you for that, because you're going to be doing better and I'm going to do everything myself so you have to think about the project and the size of the work that you're taking on and of the people that are on your project team and everything else now. If you want this level of control you're going to be giving up something else, which might be the automation of the things like accessibility so if you've got people that know what they're doing with it then it's fine because we want to have the control but we lose the flexibility. The soil this building happens that like our stool guide has to be accessible and that's something we have to build outside a droop hole It's because we want this thing to exist Felly mae'r bwysig i'r ystyried. Rym ni'n ydym ni, yn ymweld i'r bwysig unig o'r bwysig, mae'r bwysig i'r bwysig i'r bwysig i'r bwysig i'r bwysig i'r bwysig? Yn y gallu gwneud o'r gwybod yn ystod, yw'n gallu bwysig, ac yw'n gallu bwysig o'r ffordd dwy gweithio gyda'n hynny? Felly mae'n gymhwymo'r cyfrif ymgyrch, mae'n crofiadau'n ei ddweud o'r ddweud o'n gweithio'n hynny. Rwy'n gallu gwneud o'r ddweud o'r ddweud o'r ddweud o'r ddweud. Felly, dyma'r gweithio, rym ni'n gweithio'r ffunctio a gweld y pethau a'r gwerthio'n dda. Ond, mae'n ddiwedd y dyfodol yn yn dod i'r gwahonydd. Fy enw'r gweithio'n gwahanol, mae efallai mae'n cael bethau, ond mae'n gweithio'n ddiwedd gyda'r proses yn ymgyrch. so any other questions? I personally, we don't usually have a solution. Okay, so the comment there was around, the paragraph module allows you to have a hybrid approach where you can think about components within the page but actually just leave the rest of the page to how Drupal comes out. I think that's a good approach. Interestingly, that was a step along the path that we took Wrth gwrs, bynnag mae cyfrifwyr yn ymweld i'w capwys會 gael yw'r hynny, gan yndeud y tradd iawn i gael. Mae'n cyfrifwyr yn ymddangos ddwych yn storfod ar y cyfrifwyr yw daeth yr cyfrifwyr. Ac mae'r cyfrifwyr yn cyfrifwyr, yn cael y cyfrifwyr a'r ffordd, hynny'r cyfrifwyr yn ychydig i'r cyfrifwyr. Mae'n kan cos ryw bwr Wrth gwrs. Mae'n cynnig i gael y gallwch ar hyn o'r cyfrifwyr. Ond yna mae ydych chi'n creu i'r dda ni, ac yna mae'n allan o'r arwyddiadau ffwrdd y cyfnodd mwyaf. Rydyn ni'n gobeithio'r gweithio'r gweithio'r gwaith i'r modellau cwm yn gyfrifio ar y drapa, ac mae'r gyfnodd gyfoedd yn cyfrifio ar yr arweithio ar y gwaith, ac mae'n gwaith i ddim yn ei gwybod i'n rhaid mewn cyfnoddau i'r pwgethau. Mae'n gweithio'r gwaith i'r gwaith i'r pwgethau, Byddai Techfiedd yw'r han dim, mae hi'rchent ar gyfan i ddylunio i ffodol yma, a'i siaradiau fyddechrau i chi, os ydych chi, rwy'n ddim yn gweithio'r pwysig. Yn ychydig, mae hi'r cyfrydd, mae'n siaradau i'r cyfrydd, mae hi'r cyfrydd, mae hwnnw'n ddweud, a yna rwy'n ddweud yn cael ei chyfrifio'r cyfeisio a'r cyfrydd함au sydd ym Llywodraeth Cymru, i ddodod ym Gweithio. Ac mae oedd ymwylo yma, mae oedd wir i'r tyfnwyr i fy ystafell, ac maen nhw'n meddwl hefyd yn olygu gyda'r byw. i fydd y tîm yn ymwylo a'r byw'r gweithio ar y llyfr yn gyfanyddio nhw. dyma yn ymwylo i'r gweithio yr ysgolion, yma, a dweud rydyn ni'n rhaid i'r arddangos iawn. Gweithio, yma e'n rhaid i'n arweinyddio ymwysgol, yna? Can you please tell us a little bit about both the building and the set of the structure and the building of the building. I know the build of Cittles. I know them as a builder build of Cittles and they said I'll just build a TPL to it. And then they've got a motor, motor model list, and also the motor group rules take the ride and then just build their own homes. Sure. Yeah, so the common goal is around panels and Cittles and the ability to use those building plugins for that architecture, yn gwneud o fy mwr o'r pwysig, a'r gweld arwag os ymwneud gan y cyfnodd pwysig i hynny'r pwysig a'r cyfnodd yw gynnwys i lewed y mae'r cyfrwnglau ein gwerthoedd, unrhyw fwrdd mae'r prysgol yn y canddoedd yn gyfrwng o'r unrhyw gyda'r cyfrwng llythau. Rwy'n meddwl fywch yn gwneud, mae'r cyfrwng llythau beth yn gyfrwng llythau yn cyfrwng llythau, ac mae'n gofyddio sianol ymlaen o'r cyfrwng llythau. Sorry but I'm not sure if you guys are Lester Howe, which is that my project is a programme for the global economic world that it renovates and renovates. I think for us we're thinking of a process that, because we maintain a lot of sites and a lot of technologies, actually this is just one integration point, so we also have integration points into WordPress and to Laravel as well. And so we are thinking quite outside of any Drupal technologies. ac n turnoutóא� beaconion yr ateb clock. A abaithio r peuthe. So, mae'n meddwl surface of this is, processing it through lens to to fit you and to allow you to work in this methodology so really pattern value, which is for the same people that think at nearly about atomic design is an excellent tool. We have used that a lot in the past. It's quite large. It doesn't want to go to any way but it is quite a large tool but it does give you that stylewild out the back. Fe'r cyfrifol wedi cyfrifol, fe'n gwneud y ffaith, mae'r bobl yn cyfrifol ar ddyntgen y gydig a'r ffaith yn gwneud ddyliadol, ac yn cyfrifol, ac mae'n gwneud arall yn y ddysgu'r gwrth stori, ond rydyn ni'n golygu, ac mae'r cyfrifol o'r ddylch yn cyfrifol ar y ddysgu'r gyrdd cyfrifol, ac yn cyfrifol y byddai ar ddysgu'r gyrdd cyfrifol, oherwydd mae'n gydag o'r ddysgu'r gyrdd cyfrifol. So we're looking at open sourcing some of this stuff. We're going to keep putting it on to get up. But it's probably also worth looking at what phase 2's been up to as well, cos it's very similar. Yeah, exactly. I think that's what they've done is that integration point from phase 2. I believe so, yeah. Any other questions? Okay well thanks very much for your time, and I'll hang around for another 15 minutes or so if anyone wants to ask me any other questions. Rhaid i chi'n gwybod.