Layer5 Websites, 24 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Websites Weekly Meeting (Jan 24th, 2022)

Description

Layer5 Websites Meeting - January 24th, 2022

Agenda:
- Site Performance issues.
- Resources- categories and tags needed?
- Added BETA superscript to page title #2536
- Filters in mobile view (resources). #2527
- Create pattern button #4973
- RSS Feed - Blog, News, Resources(#2525)
- https://getnighthawk.dev/ responsive navbar #240
- Error codes navigation
- Footer: current color or (near) black?#4824

Join the community at https://layer5.io/community

Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/

A

Same website uh is this website adopting like changes of netlify.

B

B

This one, the navbar thing, is not working and not only that the word menu shows as well.

C

Like in the original code, which I got by forking it, there was nothing the word menu was not written anyway.

B

I know I realized that, because in the previews as well, it's not visible, but on the mean side, it is.

B

A

So me and andrew can like inspect this issue and we will get back to you and we will notify you uh if we found something. Maybe some classes are overwriting? Oh so yeah, maybe in include folder. There are many classes associated with stellar nap, so yeah. I think that might be the case.

B

Okay, that'll be great if you guys find something that is.

D

You might the other thing you might do is just to try to build the site now and and then confirm. If there's any differences between your local build and netlify and also then you can do the review.

D

um If there are you know if you are seeing the menu locally.

A

So, uh like I tried uh on my local build, it is working fine like it is not showing any menu icon and it is like adopting the changes. I know it did so yeah.

A

C

My local build it.

A

Is working fine? It is not showing that menu icon or something.

D

Nice yeah, it might be, um I missed all of the, but on that pull request. Have there been multiple commits.

D

Okay, so the second one, it might be the case that the I'm sorry, if you go back to the conversation tab are there, is there only one preview link or are there multiple?

D

Is there one after the last commit, I guess one two two. You can also.

D

One other item to explore it down below in the checks uh the build checks, yeah.

B

D

Is there another hyperlink under the details, link um might yeah if you go back to conversation, tab and you scroll toward the bottom.

A

No, it is not showing, as it is much so yeah.

D

So yeah, I guess boy we're really on a hunt, so I guess yeah. If you go back to the checks, tab and then you go to the netlify section, um yeah is there and you click on um yeah mixed content. Maybe in this case.

D

Anyway, the point is like there's often times two different two links and maybe they're the same. Maybe they're different um pages changed like do you see anything? I'm like.

E

D

E

D

Second, hyperlink.

D

Yeah like choose that second hyperlink, if you would.

B

You mean this one.

D

Oh yeah yeah, if you would.

D

F

In case of cat night talk, we only had one one comment for the bit. It gets updated itself because in that case we are directly using net effect. So.

C

We don't get multiple.

F

Previews for multiple comments.

D

Oh, I see nikhil, do you know if on the subsequent commits, if that, if we're having netlify rerun.

F

uh Yeah, it reruns and updates the first message itself, so basically the com, the first message where it adds the preview link that will that itself gets updated with the latest changes. Okay,.

D

Okay, so yeah so applejay and- uh and uh these guys are just wrong- I mean yeah, okay, so there's something something going on. Another thing that that will might rarely happen would be well, so that was the so there's the local build. There's the pre there's the deployment, I'm sorry that the deployment preview or the preview deployment and then there's the actual, build that would be done subsequent to that and that production build.

D

Maybe it didn't work you're like maybe it didn't so um and normally.

D

It's gonna kill you, I don't know if you know, but in this case so we're using netlify for preview builds. But then the production build I'm assuming that we're just using github.

A

uh I have a doubt like uh on, as debuff said we on that day we also managed a pr. So maybe, in that period we didn't like upstream those changes which which is done by another. So that might be the case like. Maybe those changes got rivered back for something.

D

So yeah, so it's door number one that you can.

D

It's it's usually it's it's a lot of times. It's like operator error like that and uh it seems to usually be me. That's the one. That's messing it up, but uh but congratulations. It's probably probably you guys.

D

Sorry, sorry to interrupt, I thought we would look for another link but yeah.

B

I think we should check this out after the call okay, so.

B

So moving on uh okay, so lately it's my topic. So lately we've been trying to improve the seo of our site. You know to improve the rankings, and the first thing which we are planning to do is change all the image tags to the static image text. Now I texted it out and I think abuser is working on.

A

B

B

Is working on the home page now uh I haven't created an issue for this yet because I think it'll be really difficult for one person to go all over the site and make changes to all the images first, because it's not as simple as you know, changing the image tag to static image. There are certain styles which get modified, and that is why, every time you change it, you have to actually go and verify that it looks exactly the same as it is now.

B

So what I am like, I thought I would do- is created this spreadsheet, where we can probably track which page like we can go page rights and I'll take up the community page that which is already doing the home page. So we can divide the work like this and maybe by the end I think this make it a little faster, separate pi's and, by the end of this week, probably cover all the easier pages.

B

One thing which will be left is the individual blog pages uh and the resource and everything so uh that we can probably group it up later, but first we should cover all these pages and probably check out the speed like after each pr is merged, probably come and see if we are actually making a positive impact.

B

So anyone has any suggestions of how everything can do it if, if this works, I'll share the link to the spreadsheet in the meeting minutes and if you guys are interested- and you want to work here- which will be very helpful- you can come and write your names down here, and you know start with just to like tell you quickly what this does like, uh what how this works is.

B

Basically, there are certain attributes by which you can um like make the edge like the entire page, node and the images will load later on, like it does not wait for the image to load and that will increase the page speed static image is used for the images which do not change like the ones which you just importing and using an image tab to. You know uh display on the page this one is used.

B

Gatsby image is used for dynamic videos, so right now we're looking at only static images, so uh yeah so any volunteers and any other suggestions, because this pause permit. You guys to ask your questions.

A

um I am thinking about like adding all the resources and stuff like how we are doing this, how we are changing images and what are the static images, so other contributors can also like contribute to these uh changes like uh if I am working on homepage, like anirus, can take any another page. He wants, or something so yeah.

B

David lee suggested, I just saw uh that we should add it to the contributing docs which I'll do, but that is for the future. This is for the existing pages like that is for the future right or the contributing. This is for the ones where we already have the image tag.

D

And that needs to.

B

The static text.

B

B

Any questions regarding this.

D

Yeah, I think aditya is raising his hand.

B

D

Oh, I'm sorry, yeah were you at, were you calling for volunteers or were you just saying? Is there any other comment, both okay? Okay, good? Okay, it's early! It's monday, it's like 7 15 a.m. It's early!

D

It's raining outside! That makes it even worse.

D

um Yeah, and by the way, this is um really rather important. The work that so layer, the the website layer 5io, represents all the projects that go on so more or less like all the work that goes on across all the projects.

D

It doesn't rank as nearly as high as it should for people who are searching for the projects that are searching for problems that the projects fix.

D

There's. There is a litany of reasons as to why as to how seo works or google google's algorithm for ranking works, and actually, if you dig in and assist here, you'll learn um some of that, maybe depending upon how much you dig in you'll, learn quite a bit of that, um but performance of a site certainly affects ranking, and so there's been a couple of issues that are have been open for a long time on this topic and debopria is advancing us in that vein.

D

So this is, I expect this is probably one of a few different types of um performance improvement, um seo, optimization efforts, um they'll be quite impactful and we'll be measuring them as well in terms of ranking for specific keywords or the current domain authority. That the layer 5 io domain has.

B

Backlinks, there's a bunch of measurements.

D

D

Leonard is on the call leonard is, uh is recovering um leonard. I muted you just because of the background noise but feel free to unmute. um It was really nice to have leonard on leonard, but I don't want to steal his thunder or anything, but he's been remiss not to be in a few of the calls and kind of active on a few issues um was in a well a car accident.

D

If I recollect correctly and just um um uh and has a number of injuries he's been recovering, so obviously recovering to the point leonard that you're back on this call. So that's good.

D

I hope your knee is doing much better, so yeah yeah good. So actually, speaking of these very issues about seo and site performance leonard was tackling a portion of this in the past, so very timely for him to join leonard. The first um bullet point under layer 5io, something for you to chew into to dig into a little bit.

D

Depo prio will add the link to a spreadsheet. That's going to track some of the work. So it's good.

B

Okay, so anyone else has any other suggestions. If not now you can look deep into it and uh get in touch with me later on. So another topic which I had was related to resources.

B

So uh initially, when we first made this, we had, you know, tags and categories which we do not anymore, but the thing is, uh we still use the category over here in the url and we use the tags and categories for the uh related resources.

B

Now, since we do not you like show it from the user side, do you think we should change? The url, do not include the category and probably something else in the filter, probably a type or something and similarly modify the related resources. Or do we just keep it as it is the categories.

D

My vote is for the categories, um not because it's more um for a couple of reasons, the most significant of which is seo um precisely for that the it's a little less helpful um like if the category is service mesh great, that's very helpful that that's very telling in terms of the content. That's there if it's interviews or news or that's still telling, but it's less it's so generic that is less relevant.

D

um So yeah there's been an open question that I've had for. I don't know about a year and a half, I suppose, on reuse of content. So if the same content is available under a category as well as under a tag, does that negatively affect um rating rankings?

D

Sure there can be the canonical url that maybe can help with some of that anyway. The point is like I, for my part, I would say like yeah, we would want to have it published under categories and under tags. It makes the site more usable, because people can choose different ways to navigate or discover other content.

D

But if having duplicative text is a negative, it ranks negatively. Then that would be dangerous. You know we wouldn't want to do that if it doesn't and if, if it doesn't good, if it does, but you have to manage a canonical url so that you're telling google this is duplicative, but here's the here's, the original source and that's okay, then find, and let's then I would suggest that we have tags and content both. I would suggest that the in the resources like on the cards themselves, it um might make a fair bit of sense.

D

Eventually, oh, I guess so we're putting the category type on there. So that's of the first one is of type blog. Second, one is a type demo. That's good.

D

Yeah, it might be that we would so by the way anyone else is welcome to chime in, especially, if you know the answer to the question that I'm asking about um duplicative content but but coming to understand. The actual answer to that question might be the most informative to answering your question. Devopria about you know where to categorize the stuff, because, like the blog post, for example, right now, do we are we, including.

D

Regular blog posts are those listed in the resources as well.

B

So, in order to avoid that, I added another field called resource yes to the blog post, so basically only the blog post, which you know count as resources, excluding all the experiences and everything. If we add that resource yes tag only then it just space over yours so right now, content wise. This page is not ready, because I do have to go through all the blogs and add which one is a resource, but that is how it works.

D

Is anybody is, would anyone like to take that as a piece of research like it's something that I've for my part, I've perpetually not gotten to, but so the question is: if you've got the same piece of content published more than once, does that hurt? Does google reflect poorly on that.

B

Okay, but in our case the url remains in same right, like even if we like open this under the tags or under categories. This changes to the category and the name. It does not involve.

D

And then, even if you open that, so, if you navigate to this blog post from resources, you'll still end up at the same url.

B

Yeah, so the url remains the same. I don't think it's like taken as a duplicate.

D

I think you're right, I think you're right, that's good! I'm good! I still have that same question, but that's actually good. It's immediately um comforting that we're not doing it twice.

D

But but the the thing is going forth: there's a ton of content that we need to publish about cloud native and service meshes, there's a there's, a ton and uh and uh yep. I wonder um nobody wants to take that as research last offer.

A

I will give it a try: okay,.

B

B

B

B

It could be open to questions right now, so these are certain changes which I suggested based on what he has right now.

B

So basically, this button looks like this and I think it merges like it is not very distinguishable with the rest of the text, so I suggested using the green button that we have the custom button in order to install this now. Another thing is uh like the clear filters, and this uh does not look good together, like it's not good, so uh one thing which I told them to do is change close filters to apply filters like and uh we could probably have to like in mobile view. We could have two buttons side by side.

B

One is for clear all filters and one is for apply filters and something which does not look like this so yeah. That was most of what I said for now. Anyone else has any other features.

D

Yeah, it's a bit weird in general, or it yeah completely what you said. It there's two buttons that are duplicate duplicative of each other, the it's a little. I don't know where it's placed. It's not centered, it's not off to the left. It's not off to the right. It's like a quarter of the way into a third of the way into the pit. It's not necessarily!

D

I don't know it's it's almost too um subtle, because it's just a piece of text. You don't know that it's clickable and also what does it mean to well? Okay, so so that we're saying that there's an action you want to open filters like uh okay, we could, we could just say filters or you could anyway yeah it needs, it needs distinction, and your feedback has been really good. On the pdr, the we were unabashedly taking inspiration from hashicorp.com resources.

D

We could do a double check as to what they do there and then.

B

B

They have open filters and then they do clear filters apply filters, but I think they yeah.

D

But they yep, but they have a blue hyperlink. That makes it look like it's something clickable, so yeah.

B

You suggested them to use the green button that we have, that shows it actually inside.

E

Instead of like, uh we are using a closed filter, we just make the icon off across.

E

So I was just suggesting that, like it's written like close filters, you can just uh remove filters and just write flows.

B

You can remove it.

B

Any other suggestions.

B

Okay, so I think it'll work, I've already reviewed and if you have any other, you can do this.

A

Yeah, I'm here.

B

Do you want to share.

A

uh So in this pr like uh in the patterns page, I have shifted the create button from the bottom of the table that was previously placed at the bottom of the table to the top of the table uh at first, I had uh yeah that this is the product at first I made because, as it was mentioned in the issue, but after certain comments and with like lease suggested that we should make a button in compliance with the current measure ui.

A

So later I changed to a blue rectangle box, just up top top left of the table.

A

Yeah this is the latest one. So so I think this this is the final state that we were expecting or should, I also uh add, the plus sign and the custom toolbar that was previously stated there.

D

um This is a good, so if I'll state an opinion but other other people can chime in um aditya, I would say this is a solid step that that is an improvement and um in an iterative fashion, you could go forth with this. It would be accepted, and then you can muddy your way through the rest of that more complex discussion with the old, the like yeah, which is going to result in like hey. We need to have a design because it needs to be a holistic consideration and so yeah.

B

D

Do it just need to do it.

A

Sorry yeah so yeah the adjective like uh in the pr he suggested, a design that I was also. I was also looking to implement the same thing and I think, maybe after merging this pr, I can work on that work on that a little bit, it's a little bit of yeah yeah yeah. That was exactly cool.

D

And then I pointed out what's wrong with it right.

A

Yeah yeah yeah.

D

Okay, so then so then don't go implement it because we're just gonna point out the same stuff and then I'm gonna choke you before not having incorporated my feedback and then.

A

So like this is the final state now there's no more nothing more to update in this yeah.

D

So, nice, okay, so this one's good to go because it just has a new button right, yeah, a button.

A

In the top left of the table,.

D

Nice and then yeah we should go uh um jump into aditya, chatterjee's design and further it. You know just the thing about it is it's a slippery slope because we'll end up in a good way, but what will end up happening? Is that we'll then say: okay? Well, hey? What does the table for applications? Look like?

D

Is it consistent? Are we teaching and training the user in the same way as you know, to expect a plus sign and for it to do certain behaviors and then we'll say, okay and then what does the filters table look like and then and uh yeah so?

D

Hence the design, um probably not much work, really just need to be consistent.

A

uh There's one more thing I think I pointed out the table for filter and application. I think, doesn't have a create pattern, create button.

A

Both application filter doesn't have a create, but I guess it just has the upload file and upload url button. I checked yesterday, but I don't know if my screen was not loading, but I didn't see the create button there.

D

Okay, a create button where, on the underneath, the patterns, notifications and filters page.

D

That was at the top left of the corner.

A

No, there were none of them button for creating applications and filters.

D

Okay, yeah, which kind of yeah, which um so technically all we're really supporting, is like importing yeah, yeah url.

D

That makes sense right now, because right like right now, we don't we support importing, not creating okay, okay, okay, that's fine.

A

So this pr isn't ready to merge. Then I guess.

B

So next up we have the rss speed, so the news and the block one has been merged already uh this one. This pr is there for the resources.

B

Now. uh One question that I had is: are we like putting in a different subscribe for these, like blogs is right now this one takes us to this page. So are we allowing the users to subscribe to specifically see the blogs or news resources.

B

D

Wow I keep letting myself get distracted um so on the rss feeds.

B

So I was asking if we need a new subscribe button or something specifically subscribe.

D

Other than the small, basically like the wireless signal.

B

So what this does is take us to this page.

B

D

Oh yeah, it is yeah. I realized that, like rss is almost dead. It's like a um still breathing, it's kind of laying on the ground um after people kicked it and kicked it, uh so it isn't necessary yeah. I mean um anyway yeah. That was the intention. um We, it could be the we do have a. We don't have a specific call out to say subscribe for new blog posts, which you know we could do um we. Hopefully we do have a call out that says.

D

If you scroll down on the right hand, side is, it basically says subscribe to the newsletter. If I um maybe we should change the verbiage there to say to new posts.

B

D

Yeah subscribe for updates, yeah, but uh yeah most, I guess suppose, you're in chrome at the moment. So when you click it, you get xml which is like if you're in safari and you click it by default. Safari will tell you hey. I don't know how to read this xml, but you might want to install an extension, a plugin that does so. Maybe some people have an extension, a plugin like almost no one will I'm sure.

D

I don't know, let's focus our energy somewhere else like it's about as good. I mean like hell. That's the way that, if you're older than 30 that's how the internet used to work now, maybe that's not how what we should do. um uh Hashicorp does it, uh which is one example of like well yeah. I don't know I mean like: do we have a tooltip on it that if you hover over it, does it say anything? No I mean like that might be.

D

Something to do is just just have an alt tag that at least lets people know it's an rss. You know subscribe to the rss.

D

So feed I recognized my and my response was like, if you objectively measure what I just said, it's kind of a crappy response, it's sort of like. Well, that's how the internet used to work. It's like! Well, that's a dumb response. Okay. Why would we keep doing this like we? Don't do that's not we're not doing old stuff just because you know like that, doesn't make sense all right, um you know.

D

Is there another way to help clarify to users that, like, like you know, I don't know something to not let users land on what looks like a broken site like just a bunch of xml and code in their face could be or in safari like where it just says. uh Sorry, I can't read this, and people might assume that it's broke. We could we could offer up a modal that says you know that basically says hey.

D

You know great, you know, there's here's two choices of subscribing for updates the this is an rs test link and so click here with use your rss reader here. Add this link to your rss reader and the other one says enter in your email. Address is possible, like the reality is like.

D

For my part, the reason I was giving kind of a crappy answer is because I feel like we should spend our time somewhere else, but uh but something like that mobile might work, because, because you could then suggest, like you know, if you'd like to subscribe to rss here's, we could make it convenient like here's, the direct rss link, which will maybe work, maybe won't for something you know, but then it could also say, like here's, I'm sure that um I'm sure that tools like feedly.com or others might make it easy to have like a subscribe to my rss button like using feedly, where you pass in your url and if they have a feedly account it would.

D

um I just think it's kind of we're sort of at a point of diminishing returns like I think that your questions about the resources is um um something to spend our time on. That's more of what we should spend our time on the seo stuff, the litany of like what is lighthouse looking at and why? How are we? Why are we not using the sharp plug-in and gatsby or we are, but we're not doing it right, like those things, I think will have a much greater impact. I don't.

D

I think that the uh so by the way, just the the um motivation behind creating rss feeds was um more or less. It was kind of sort of three reasons why the biggest reason was because the way that we're able to because some of the systems that we're using to help tweet something out or share something they will leverage an rss feed. So it's very it's convenient for for us to be able to have an rss feed for blogs, for news and kind of you know um hook into those systems. That was that's.

D

The biggest reason is the second one is like. Oh it. Well, I think. Maybe it adds something nice to the site where it doesn't just say blog, it's blogging, there's something else, and then the third one is like on the you know the two percent chance that there's a 40 year old out there somewhere that actually has an rss reader plugged in um or that like. Actually, I don't know that you, I don't think anyone on this call probably knows this, but um to fully.

D

If you visited um slash contact, there is a um well there's a web-based forum where you can contact us if you're having problems or questions or or you can email us, but the contact form this um there have been. I don't know quite a few people who've submitted this and one of the very first ones that was submitted was, I forget, the guy's name from here in the u.s.

D

He was asking for an rss feed, but then that's when mesh mate, mckills stepped in to actually create the first rss feed, and uh so there are in fact people who look for rss and in fact people looking for it on our site. So you know for what it's worth.

B

C

C

So uh this is the error codes table. So initially we had an uh like we needed to update the layout of the error codes table so like I uh like, there was a suggestion that we made it like something like this that we have in the compatibility matrix so yeah. So this is the table that we now have in which, if we click like uh the user, don't have to go through all the uh error codes, like only two which he wants like the comp.

C

He wants a component type uh component type, adapter and component name measure linker d. Then he should be. He should be only going through that uh components and reports, and nothing else is so yeah. That's uh that's what I've done here.

C

So any reviews or anything else which we can do here.

E

When we click, it doesn't look like there's a new codes open.

C

Okay, so we we could have like different background here.

E

um Different background won't look good.

A

Maybe a little indentation.

C

Or maybe we could uh remove uh this component time and component name from the uh like the the rows which opens afterwards when we click like we don't. We won't have anything here and only this.

E

Yeah yeah that could work.

D

I can't believe does anyone else have suggestions.

D

And yeah, I guess ux is like impressed incredibly hard. um Shoebom I'll shoot it to you straight. um This is not an improvement. um It's actually. It's actually probably a step backwards, so there now that I've completely insulted you. Let me um suggest some stuff. So thanks for taking this on, it's not an easy task.

D

There's a ton of data here and if you're trying to kind of keep things within just css and not pull in a bunch of javascript and stuff, then it's it, that's even more challenging so so this is a good challenge to take on um this. One kind of reminds me of I don't know if you've ever gotten a writing um assignment. Where someone says hey, you know here's two paragraphs you got to convey all the same info, but in one paragraph how's that how can I? How can I be that concise?

D

You know how can that's kind of our challenge here? um The reason I said it's not it's a step backwards is because it's not obvious that there are there today. If you visit the site, you'll see that there's the error codes are grouped by component.

D

So if you're interested in one component is failing, you you go to that area and then you look through the code. The error codes there um here isn't necessarily. I don't know that the columns are sortable. Moreover, I don't know that they're sorted by a component type and if that's the leftmost column, you generally expect the leftmost column. You know things to be sorted on that column. First, um there's um a bunch of stuff here, um one the actual the primary um call to action to refactor.

D

Is that like? If you look at the page now it's quite wide and too long for anyone's you know screen um the details that it's like here's, the task that someone goes through they're they're running measuring, I think, there's an error. Oh crap! What's going on, uh I'm not quite sure, but there's this error code, um good. That looks like something that google might be able to pick like they, probably google it and land on the page like okay.

D

Well, I'm looking for this error code, so so one the way that error code comes across is, if you go back to the left, some yes under there there's the error code. 1000, actually, what what the heck there's like three of them? Well, that's not unique! Well, yeah, it's kind of bad. Actually, I don't really like the design anymore, but um but what is unique is the error name plus the error code, the okay, that's good!

D

The problem is when it's presented to a user, it will say the error name, hyphen code and when you try to search your browser for that or search google for that, the two are not together on this page, so that makes it harder much harder to find, and you end up if you certainly you're like okay, well I'll, just search for the numbers like well, no you're going to end up with like a bunch of 1000s.

D

um So that's something to consider is combining error, name and error code into one column. That's number one number two is so when someone identifies that yeah, that's the one error reset mesh config code, one one thousand four, that's the one! That's what I'm getting what's going on here! Okay, that's! Their first task is just identifying that that's the one of interest.

D

They can then click to say. I'm interested in more info, so then the more info would be that everything at you that the way that they can so they can browse easily. If we leave component type and component name on the screen good, we should leave those. We should make those um faucets that they can open up and expand and kind of browse by search sort by the error, name and error code when those are combined. Those are things they're going to search by great.

D

They can either use their browser search today or if you bring in a javascript table that has that capability you know great. They could use the table's capability to search severity yeah they might want to sort by severity. Just you know, but, um and the short description like beyond the after for long description, probable, cause and suggested remediation, everything to the right of short description, it needs to go, be hidden, go away, that's something that they can click for and say yeah, I'm actually interested in those details.

D

Otherwise, don't show don't flood me with more things than I can. Possibly you know browse through I'll I'll. Tell you I'll click and I'll. Tell you when I'm interested in what the rest of that is, and that's actually the point and difference between a short description, a long description, short descriptions for you know. Space constrained display like this, so try that. So, if you would, you know, like kind of, I think the reason that that other page was highlighted, the one that um goes through the test results.

D

The reports was under the concept that long description, probable cause suggested remediation, that those would be things that would be shown in a subsequent row after you click after you identify that you're interested.

E

Okay, there's one we can do like, instead of showing the whole table beforehand, we can like let them have drop downs where we can choose competent, name and type, then, according to that that the table will show up without them.

E

That can be also a nice thing to have.

C

Yeah, so we we had something like no, we didn't had to drop down. I think.

A

We maybe like just want to say, like we can implement different filters in error codes.

A

The table will show up according to filters we can like uh have like either code 1000, then only that three uh code, which is associated with error code 1000, will show up.

C

A

Something like that.

C

We had something like this uh in which, if we click like on the component name, so we were directly to that table directly to that table in which- and I I get what you're talking about like we could have the component name and component like we could fill that drop down, and then they would directly direct it to that row. Right.

A

C

Yeah so uh like I, I think that's good but, uh like I don't know like what are the reviews of all of us about that.

D

What was the yeah? That's? I don't know what I can't really follow. What was said, but that's another. It's another place where we step back. It's like you can't quickly navigate by component, and so we.

B

D

And so there's a I put a link into the chat uh called it's called datatables.net.

D

It's. uh I think that on much to uh richa isn't on anymore. um That's all I'll ping here.

D

But I think we have bootstrap and jquery in the docs already.

D

um I think if we don't it's not that big of a thing to pull in just this data tables- and this is a good one to use. Thank you it'll, give us a lot of stuff we might we might want to use. Maybe this is the right thing to use. Maybe it's not. It would give us search. We don't entirely want to paginate. That's not I mean maybe, but if you would, if we were to have one data table per component, that might make more sense.

D

The first goal of what I was really looking for here is to just is to leave the existing formatting, the top level nav by component. Then each component broken down by section. It was to combine error, name and error code into one column and then hide the rest of the details by putting them into a subsequent row. That would only be visible if you click on the first row, like that.

D

Just doing that, and that's all through css, um that's a major step forward that addresses a lot of things without having to go to something else. Actually, now that I say this, I'm don't do this, because I think that it will be another month before something that we're done. That's not a reflection of you, that's just how this stuff goes, and that's actually why I was pointing to the other example: that's right in the docs. It's just an example. You can replicate over, hopefully.

C

Yeah so uh lee can you can you write down or the three points that.

D

You just told no, no, please you can you write them down, because if, if you can't and the reason I don't mean to be- I'm not trying to I'm, this is actually is I'm kind of hesitant to say it like this, because I don't want to come off. It's um that's a capability. You need to have like.

D

If it's it's uh yeah, you can repeat it back to me. That's fine like write it down and say: hey you check out these quick bullet points. Is that yeah, okay good and we should communicate like that. We should double confirm kind of back and forth. So the reason I say no is because at that point like I may as well just go do it. You know what I mean and.

C

Okay, so uh so like this, this layout is you are saying that this layout is fine and you want. uh No, so I'm saying it's backwards, saying it's two steps backwards. Okay, so uh we would like.

C

We would have something like this- that we currently have right now and uh we would have like uh not all the columns in the lower left. We would only have short description and when the user click on this row, then only the long description and probably should be visible. Something like that. You were saying.

D

You're so close, what else did I say twice.

C

I might have so I might have missed something.

D

Okay, all right well to be fair, like it's not 7am, for you, so uh good.

D

The other thing I said was it was about the error codes and the error names.

C

Oh yeah combine those two okay, okay, so this is this lot that we currently have right now is fine, but we need to focus on the combining of the error, name and error codes and uh showing of the long description only when the user click on the row like on that particular row. Something like that yeah chance. Are you okay? So we don't want uh anything like this layout, something like that this week, no.

D

C

That's exactly what I'm saying to do so uh like right now, so right now, like uh we have this, that this thing that hovering of the uh of that particular row.

D

Okay yeah, so um on the current page, you know how it has one section per component.

C

D

If we go ahead and leave one section per component but take the behavior of those test results that that row clicking behavior and integrated integrated into the same tables that are present today, so we would still have like 10 or 12 or, however many tables. Okay,.

C

Yeah, thank you. Yeah yeah.

E

B

E

Like uh we should also add the search.

C

Yeah we could do that, but first we could like focus on currently what we need to do. We could make another pr for that.

E

C

D

B

All right, so we have one more topic left.

B

I did not add this.

B

B

So I think this pr has enough reviews for the time being, you can probably call it.

B

I think this is the final step.

D

Yeah seems like it um he it's just that, like I don't know, if he hand drew that or what, but it is slightly off like um it's. It's actually funny yeah, it's it's like one, one pixel on the right hand, side it's.

D

Right, on the right hand, side it's a smaller width than, on the left hand, side it's really hard to tell. But I'll bet you, ten bucks, yeah. It's it's ever done right, which is it's like one of those things. Where is.

B

Not straight like not horizontal.

B

Okay, so I think that brings us to the end of the minutes.

D

What do you think about that? Does that make sense to do.

F

uh Yeah, we can't do that. I just need to add that link right along with the text for the discussion.

D

Okay, did you say hey? It would be helpful to offer up some text for it.

F

Yeah like uh similar to what we have for the links right right right.

D

F

D

F

Like check out our discussion forum also.

D

Yeah right yeah engage in there drop your questions, yeah yeah, right right.

D

Nice, thank you yeah um by the way, just so the the context for what's being discussed. I know that we're at the top of the hour. The context for what's being discussed here is um for all of you that joined the the slack or joined the community within.

D

I don't know, probably hopefully I think for all of you that have joined um in the last year so that you might have gotten this message. It might have been with a dark mode background. I don't know.

D

Is there anyone that doesn't remember seeing this.

D

I ask because we want to make sure that automation is working.

D

So this would have come from a bot sending you a private message.

D

um You know shortly after you originally joined slack.

D

Did anyone not get this? First of all? If you didn't get it like hey, we should go check out the automation but b. Then you might be missing out on some stuff. Some free learning that you otherwise didn't know about.

D

D

Okay, good sounds like everybody got it, um but yep, that's the context, so nikhil will iterate on this. I do think that it might make sense for us, like a couple of weeks after someone has been here, maybe um to send them another message that gives them a link to a copy of one of the service mesh books.

D

Something we could think about too.

D

More work for nikhil.

D

Yeah potentially like um we after this change, uh maybe we would add another one to run a couple of weeks after someone has joined, to send them a link to download a free copy of one of the books.

D

That seems like a good thing to do. One issue might be trying to discern to whom we've sent that who's received that message and who hasn't so.

F

Yeah yeah not sure, but like I doubt if there would be any way, we could store that information, but we'll have to check ones. But again that will again bring us the uh that ap limitation for how many messages equals and then month also.

D

Yeah yeah yeah yeah, two two thoughts come to mind quickly been bearing in mind what you said about not going over the number of activities and the number of is one. Might I don't know if there is such a query or how much this would cost us, but is to say, give me a list of the users who have joined after or um give me a list of the users who joined after a certain time stamp a certain date and and that date would be just like a rolling.

D

It would be joined two weeks prior to today, and so we would just kind of keep a rolling. um You know we, so we wouldn't actually track state. We would just figure out, you know who's new kind of a thing. um That's one way now depend if that takes 15 you know calls to figure out, then maybe that doesn't work.

D

um The other way is to potentially use a stateful system like mailchimp, so if folks, that sign up, if they get dropped into an audience there, um or rather not mailchimp, but the spreadsheet, you know if, if folks, that sign up put them and enter them into a spreadsheet, just tag tag enter a tag in there. That says either that uses a timestamp just like I just said, or that just has another call, there's actually columns in there for did. We send them certain things, and so you know that could be used.

F

uh Yeah, maybe you can try that one, because, uh as of now, we don't check on the when the user joins right, we check when the user submits the form, and only then we send a message.

F

So we we can use a similar approach in that case also to check the google sheet for the time field. When the user turns when the sheet was updated. I then landed.

D

I'm just full of like great ideas today, it's just.

D

That and if shubham was here, he probably slapped me but uh so.

D

Cool uh yeah that sounds like both of those things sound like something to potentially explore.

B

Okay, I think we are done with all the topics today. uh I've shared the link in the meeting minutes as well for this spreadsheet. You guys get this up. Okay, so thank you for joining.

B

You think it's the third time I'm hosting this week. People are probably bored of you, especially that call will be hosted by someone else. So don't tell me.

D

Think about that uh somebody else might want to host next week.

D

I'm pretty sick of listening to devil, breathing.

B

No, I meant from the newcomers, because some of them have been hearing me from new covers.

D

Oh, oh, okay, okay, good good yeah by the way on the newcomers call um lots of like so josh is a name that pops out as like having been around quite some long time worked on various things learned, you know, cut his teeth on some gatsby stuff and other things like um the newcomers call is a great place to ship like share that back with others. You'll learn it more.

D

People won't make the same mistakes. People you know like um it'll make the newcomers call even better.

D

So all for all of you give that some thought, if you would doesn't have to be a big share, it could be something like shubham saying. Look, I don't know if you knew this was possible, you can take jekyll and take a collection of a collection, and you can iterate over it and do like you can just show something small. It's just nice to show some give some tips.

D

People have the same questions over and over shoe boom could say something like look: we've kind of been round on how to represent data, and this is a style that we've been trying to use, and so you know I've noticed there's a couple of other pages. We've got a number of collections, we have a collection of adapters and a bunch of info about them, like there's other collections in there that the pages themselves sorry to say it, but the docs need a little bit of an overhaul.

D

So um anyway, a good opportunity for you all to share back in the newcomers call.

D

Thank you deborah priya.

D

Thank you all. Thank you. Everyone see you next time.