Solutions Architect | Design System | Community & Developer Avocado | Founder @jslovers_del ; Talk to me - JS, PWA, Web, React, calligraphy, veg , accessibility Working on a11ytips.dev
Tech Talks, mentoring
Good read...I would like to add a few more points: 1) Following class naming patterns such as BEM etc. 2) Following the common format for the color codes, units, etc. 3) Working with CSS selectors rather than having a long nested declaration of the class, elements, ids. Do check when you get time: https://hellonehha.hashnode.dev/css-for-large-projects-ckq25g1wk064qtys1e38k2phs
It is a good question. The reason is as a user you want to have 100% flexibility but as the design system developer it could be a challenge for you to maintain so much. From my experience, keep it to a few but a few doesn't mean that missing the flexibility. For moving to a new file, the rule one can follow is if by changing the one variant we need to change other varients too then move to a new file.
Google gives a very good insight into this. To start, minify the CSS, Javascript, assets such as images, etc. Cache the static assets. There are different approaches for breaking long CSS and JS files such as you can have critical CSS, load JS on a modular basis to improve the performance. My goto guiding tools are Google Lighthouse and Network panel. Lighthouse gives you the issues and solutions too.
There were many challenges. As when I started meetup and community was not an acceptable thing in India. For me, it was like I am explaining the folks first what meetup is and then doing tech-session. Also, there were no resources to host a meetup at any place. We did our starting meetups for a year at a cafe where I used to pay for venue and food. Apart from logistics challenges, even attendees were not keen to spread the word about the community. Now, everything is sorted. Every company now supports Meetups and communities and so is co-working. So, there are not many challenges. My advice : 1) Do not look at how many people came? Look for how many interested people came. At JSLovers, I never focused on having 50-100 folks. My focus was on quality over quantity. 2) Getting speakers is hard. Try to push from your attendees to be a speaker (but do not compromise on the quality). Do a dry run with them, ask questions to them, and also be prepare might be you need to chip-in while speaker is giving session. 3) Have a code of conduct always 4) Do not be afraid of taking negative feedback.For me, feedbacks are my next steps :) 5) Always remember the community is about 'sharing' not about 'marketing'.
Hello, #1 As a dev the top-most thing to do to have an accessible site - write semantic & structure code, provide alt tags, add lang, title attribute, do not remove the outline from the CSS, make sure color contrast is passing, should have label tags and use Lighthouse and wave tool to assist your inaccessibility. #2 For now my favorite is VueJS Gridsome (it has GraphQL support too) if I am looking for something UI Framework based otherwise I just go vanilla - it is superfast. #3 I am pretty active on Twitter and Linkedin. I keep sharing my daily learning there and I keep interacting with devs there. Apart from these, attending Meetups help a lot and appreciating developers on their blogs, work, etc on DMs
1) I am an accidental speaker :). When I started JSLovers it was impossible to get a speaker. My co-founder used to give a session and I used to manage everything. Then one day he was not able to give a session and I delivered my first session. It was the worst session. I didn't give any session for 3-6 months and then 1 day I just decided to give a session and since then no looking back. 2) I feel for me it was the zeal to just face the fear and also when you know something very well and not memorizing for faking you already know there is nothing to fear. Just to go and face the crowd. 3) My advice would be - "Do not go to public speaking because everyone is doing it. If you are passionate about knowledge sharing then only go. Also, there is nothing like a basic or advance topic there is always an audience for everything. All the best!!"