Send Byline Default with airSlate SignNow

Send byline default

[Music] [Music] [Music] let's get started i'm glad by leicester i'm working with adobe i'll be talking about the core components a bit my colleagues later on will deep a bit diver into some of the technical details and we'll also have a panel discussion and yeah let's let's get started i was saying that we've been working for almost four years on the core components we're 23 releases in and we got about 30 components built during this time we have almost more than 60 people contributing to the core components as they are developed uh in open source and we we've seen over this time more than one thousand issues and pull requests that's that's a lot that you as a community have have given back to us as well and by our records it's more than 300 customers which are using some at least some of the the components we also have a nice little website that we put together where you can see all the components uh i'll give you a short glimpse if you haven't seen it already it's the the library it's showing you the components and some of the variations for for them you can you can have a look of but how they work you can have a look at the properties and the markup and the json that's associated to with each of the component and lately we also integrate it along with the commerce team some of their cif components as well so make sure to to check it out and yeah have a look there so what's what's new since since last year we had a few releases we had 280 in december 2019 which was enhancements and some bug fixes this year in may we we added integration with the adobe client data layer uh jc my colleague will have a discussion and a deep dive in the technical aspects of that we also added one more nifty nifty little progress bar component and then later this year we had 210 which added document cloud and then 211 which added amp support to core components and that was followed which uh added some expanded json content for experience fragments and also added alternate artifacts for am as a cloud service so now you have the the core components inside aem as a cloud service uh meanwhile i was stating that the commerce team has integrated their their cif components which uh yeah they work nice with am and magento as well and like i said uh a big kudos for for the success of this project is actually to you the community we had more than 50 contributors over the last year that's that's a lot uh i want to give a special thank you to to our partners our volunteers which helped us with the implementation of the mp feature the partners at ensembl systems which worked on the pdf viewer and as always some of our favorite contributors conrad kyle and stefan zeifer which is uh also the one of the people behind this conference and yeah thank you all guys uh it's been it's been wonderful to have your support it's been wonderful to to see your comments to see the issues the fixes and some of the pull requests have really blown our mind so yeah thanks and for the rest of you which are wondering how they could contribute to this project it's easy you can file an issue if you have a problem uh file the issue make sure it's a good issue that means that it's reproducible and it's specific that that would allow anyone looking at the issue to to reproduce it and understand what this issue is about or better yet if you have a fix for something send a pull request we are trying hard to to keep on keep on top of these pull requests and merge them as they come in so yeah if you have a fix send it or if you if you want to have a look at the the existing pull requests or the issues uh have a look at them comment on them let us know if you have the same issues or if you see a better solution for some of the the stuff that we're working on and last but not least you could you could write a test it's as simple as that if you want to get started and work with the core components just yeah write a unit test write a an integration test we would we would appreciate it a lot if you if you are not into coding but still want to contribute maybe you can open an rfc issue a request for comment issue where you could describe whatever feature or new thing you you would like to see implemented and yeah we review them periodically we comment on them other people in the community comment on them and maybe something something good will come out of it we also have a mailing list for longer discussions so send a message there if you have some ideas or some comments and if you if you feel that something is not really that that useful to everyone using the core components we also have an alternate repository uh where we we allow people more easily to contribute something that doesn't get installed by default with aem but it's still a nice place to share whatever you are building which is related to the to the core components so head out to the country repository and if it's something that you feel doesn't make sense to be added to the main repository you can just add it there what's next we we plan to have a new release soon with some fixes and improvements and by the end of the year we plan to have a larger release which addresses some of the long-standing issues uh like improved link handling throughout all the components and that will also uh make us bump the up the component version for quite a lot of the components so we'll we'll we're looking at issues that require some some incompatible changes and trying to address these for for the 3.0 release as well so yeah we are targeting the end of 2020 to to do that we also have a roadmap you can see it on our wiki page we have link tracking on our roadmap and we have a bunch of components that we are we are still trying to figure out how to how to better add to the rest uh table of contents and model dialogues a dedicated search component with a search results page a new grid is something that we are we've been exploring and discussing about a lot of improvements are still are still irritating around the teaser we we definitely need to to improve a bit the form components and we've had some requests both internal and by from partners and customers for the author byline components and for email support in the in the core components apart from that we also are looking at how to better integrate the data layer with adobe launch that's that's coming up and the next talk will cover a bit this we are also uh looking at enhancing amp support we added that in the core components it's kind of basic at the moment but yeah it's uh it's coming we're gonna have some enhancements there as well we are gonna have uh a bit more polish on the am forms integration there's a there's a comp there are a few components that have been put together by the aem forms team we want to to have them as first-class citizens in the core components as well and there are also some ongoing changes some discussion about changes in the way we use the sling models api we had a lot of people commenting that it's complicated the way we use uh right now the the steam models api with an interface and it's it's kind kind of complicated to get access to the default implementations so that's still up for review and we would appreciate your comments uh on the mailing list on the corresponding issue for that that that will help us steer the the direction better we're also looking out at how to better accommodate front-end code uh and changes like that with the core components so yeah there's gonna be some something good there as well uh one of the things we did this year uh when when the whole pandemic struck was we work with the guys at deloitte on creating a website they put together some some analysis based on what people were thinking or feeling about the whole pandemic situation and they we worked together with them to to kind of get this micro site started that was some good practice for us because as a product team we don't always get to work on on customer projects so there's a bit of disconnect and we feel it and i'm pretty sure you feel it too that's why we always reach out to the community to get information on this right so we worked with them and the whole project took about one month trying to set up a website uh where they could just share their their information and their analysis it's a simple website uh but it has some some nice things to it and the the big thing with that was that they were able to create it in the end just using the core components with no custom components they just use what what was available out of the box they did some javascript magic around the graphics there but yeah that's that's mostly about it and it's been it's been interesting an interesting journey for us to see how our customers use the website however the partners some of them have some experience with core components and editable templates but some of them were still reverting to to the old you know static designs and yeah it's it's been interesting to see to see that happening i'll give you a glimpse of the of the website so yeah this is what they started with they had some mocks different pages with adobe xd and based on that the website they created looks like this it's a it's a nice presentation website they have some sections where they they they have some some graphs with some data uh what you're seeing here is just the the carousel from car components which allows you to to switch you know to to different data points and yeah it it's all core components in some creative javascript and being on this journey with them have made us consider the case of customers that might have some some smaller projects or they don't want to invest that much into into creating a full-blown project and a lot of customization so we are trying to find ways for them to to be able to have a website created in a more simple way that means using just the core components with no coding at all on the back end side at least with something that allows them to customize the look and maybe have some pre-made packages for them uh by by a development team but when they want to set up a new website they they don't have to waste time they just use those pre-made packages and they can quickly create a new website and something that allows them to update javascript and css fast so that if they need to make any kind of adjustments they they can be they can be agile about it so that's that's also on our roadmap so yeah that said if you have any kind of questions uh related to where we're heading where we're heading just hit me up i'll try to to answer them uh if i don't get to answer some of them or you think of some questions after you see the the next two presentations we're also having a panel discussion later on so yeah we can we can address whatever questions there are there as well i have a question already will there be an example css for for core components we already ship some css with the components library you can have a look at that and get inspired along with the components we we tried to to keep the css to a minimum just what's needed for them to to function maybe some resetting around the css but no opinionated css or look for the components after out of the box but with the simple website creation flow that i talked about that's that's probably gonna gonna change because we're gonna have some packages with some sample layouts and some sample css and yeah there's gonna be some default uh lit package that you can use with the core components another question was the design for deloitte made with component system in mind or was it more retrofitting retrofitting components in the mock-up actually when they started doing the mock-up they had no idea about the core components so what what we did and what we encouraged most of the customers to do is start from the mock-up create the wireframe and some templates which map to that and then adjust stuff in the css it's amazing how much stuff you can do with responsive grid and the style system and yeah just some thoughtful css how soon after a core component release will it be available inside am as a cloud service that's a few days usually it it takes a while until we integrate it and we validate it but usually it's it's a couple of days a good question we know core components are great but always end up in creating custom components can we find out where is the gap well that's that's actually our question to you the community help us identify those gaps we know for sure that whatever component library we will create it will probably not address 100 percent of the needs of the of the community or the customers and there's always going to be that that 20 that pareto principle right we try to address at least the 80 with 20 of the components we have i'll i'll take up the next questions uh to our panel discussion and we'll try to answer them there because there's there's no more time here and i don't want to keep you from from the next presentation which i'm pretty sure you will be enjoying see ya you