<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kriszta Matyi on Medium]]></title>
        <description><![CDATA[Stories by Kriszta Matyi on Medium]]></description>
        <link>https://medium.com/@krisztamatyi?source=rss-1e0502ac4382------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dxFOUQRcRVl-m8T_0n78hg.jpeg</url>
            <title>Stories by Kriszta Matyi on Medium</title>
            <link>https://medium.com/@krisztamatyi?source=rss-1e0502ac4382------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:10:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@krisztamatyi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to deploy a website to Netlify]]></title>
            <link>https://medium.com/the-codelog/how-to-deploy-a-website-to-netlify-35274f478144?source=rss-1e0502ac4382------2</link>
            <guid isPermaLink="false">https://medium.com/p/35274f478144</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kriszta Matyi]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 04:41:51 GMT</pubDate>
            <atom:updated>2019-01-07T20:38:58.175Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a beginner level tutorial on how to deploy a static site to Netlify. It assumes basic knowledge of HTML and CSS and familiarity with Git and GitHub.</em></p><p>So you have built a website and are now wondering how to get it from your computer and onto the world wide web. Maybe you have completed one of our HTML &amp; CSS <a href="http://tutorials.codebar.io/html/lesson3/tutorial.html">tutorials</a> and are trying to show off the results to your friends and family, or perhaps you are looking to host your personal website online. Either way, deploying a site for the first time can be an intimidating experience, but it doesn’t have to be that way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*WMA_NYFfvZIpx_uvQxQQEA.jpeg" /></figure><p>Enter <a href="https://www.netlify.com/">Netlify</a>. Netlify is a tool that provides an intuitive online interface for deploying websites in just a few clicks. What’s more, it’s completely free for unlimited projects for one person, making it ideal for personal websites and small projects.</p><p>To deploy your site, you will have to commit your code into a git repository and push it to the git hosting provider of your choice (such as GitHub, GitLab, or Bitbucket). I will use GitHub as an example in this tutorial, as all codebar code is hosted on GitHub. If you don’t know how to use git or GitHub, take a look at <a href="http://tutorials.codebar.io/version-control/introduction/tutorial.html">codebar’s handy git tutorial</a>, or try <a href="https://try.github.io/">try.github.io</a>.</p><p>Once you have pushed your code to Github, you are ready to deploy your site. The first step is to visit the Netlify Create a new site page: <a href="https://app.netlify.com/start">https://app.netlify.com/start</a>. Don’t worry if you haven’t got a Netlify account yet, you will create one as part of this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pV0iG0v_6N00_YC07gP7qA.png" /><figcaption>Netlify Create a new site page</figcaption></figure><p>In the Continuous Deployment section, choose the git provider your code is hosted on, in our case GitHub. At this point Netlify will ask you to authorize access to your GitHub account. Once you have given permission to Netlify to access your GitHub repositories, it will ask you to choose the project you want to host (as an example I’m deploying my own personal website):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jji72OdIn5i-t_TN5d88rw.png" /><figcaption>Choose the approriate repository from the list</figcaption></figure><p>The next step is to tell Netlify which branch to deploy from. In git the default branch is called master, use this unless you explicitly want to deploy another branch, in which case choose from the dropdown. Netlify has built-in <a href="https://www.netlify.com/docs/continuous-deployment/">continuous deployment</a> support which means every time you push code to your chosen branch Netlify will re-deploy the site and your changes will be available right away. This neat feature allows fast iteration on your website and makes it a breeze to keep it up to date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w3vJwdrF1eT3Yno_uPUwFA.png" /><figcaption>Deploying krisztinamatyi.com from the master branch</figcaption></figure><p>If you built your site using a static site generator (such as Gatsby.js, Jekyll or Middleman) you will also have to specify two more options. Build command is the command you use to build your static files (such as gatsby build, jekyll build or middleman build). Publish directory is the directory where your generated files are located (such as public/ or build/). You can ignore the advanced settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hGtHQsxCQkVRh-bNDyu4Pg.png" /><figcaption>Optionally set the Build command and Publish directory settings</figcaption></figure><p>Once you have filled out all the required settings, hit the Deploy site button. In a few short minutes your site will be available at a public URL provided by Netlify. If you’d like to change this URL to something more sensible, for example [your_name].netlify.com you can do so under Settings / General / Site details, by clicking the Chang site name button. That’s it, you are ready to share your work with the world.</p><h3>That’s not all</h3><p>Netlify provides a super simple deployment process but it has a number of other powerful features. You can add a custom domain to make your site available at the domain of your choice. Securely exchanging information on the internet is important, so Netlify provides each site with a free and automatic TLS certificate. You can even add dynamic functionality such as forms to your site directly from Netlify.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35274f478144" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/how-to-deploy-a-website-to-netlify-35274f478144">How to deploy a website to Netlify</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[uncodebar 2: bigger, better, more absorbent]]></title>
            <link>https://medium.com/the-codelog/uncodebar-2-bigger-better-more-absorbent-532e9cb55736?source=rss-1e0502ac4382------2</link>
            <guid isPermaLink="false">https://medium.com/p/532e9cb55736</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[open-space]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[unconference]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Kriszta Matyi]]></dc:creator>
            <pubDate>Wed, 09 Nov 2016 16:12:00 GMT</pubDate>
            <atom:updated>2017-01-05T11:47:15.775Z</atom:updated>
            <content:encoded><![CDATA[<p>No sooner had last years uncodebar ended than all the codebar organisers and attendees declared in unison: let’s do it again!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkBL53bdXqbkM0hnaEbn4A.jpeg" /><figcaption>A portion of the attendees</figcaption></figure><p>After the phenomenal success of our little bootstrapped event last year, we decided to run uncodebar again and make it bigger, better and, well, more absorbent. We increased the number of attendees from last year in a bid to bring in more people from diverse backgrounds. We decided to invite students to participate who we thought might benefit from experiencing an open space format event. We reached out to the wider tech community to attract people who have never been to a codebar event before. But first and foremost, we wanted to capture the informal, open, community feel of the event last year and keep it geared primarily towards our coaches.</p><p>With that in mind, on a crisp October morning we gathered at Pivotal’s London office to share knowledge and catch up with members of the community.</p><p>The format of the event was the same as last year: an unconference style open space where everyone could pitch sessions with the schedule coming together on the day with talks, workshops and discussions from attendees filling the slots.</p><h3>codebar on Twitter</h3><p>Attendees pitching sessions for #uncodebar2</p><p>The breadth of topics was once again astounding: we had sessions ranging from an <a href="https://twitter.com/SamirTalwar">‘Intro to Elm’</a> to <a href="http://www.reload.me.uk/talk-typography-for-developers/#/">‘Typography for Developers’</a>. We talked about <a href="https://twitter.com/d_ir">‘Building Inclusive Teams’</a> and <a href="https://twitter.com/indykidd">‘Apprenticeships and Software Craftsmanship’</a>. We got an <a href="https://twitter.com/deniseyu21">‘Intro to Docker’</a> and saw a demonstration on how to build <a href="https://twitter.com/jsnightowl">‘IOT Puzzle Gadgets using LISP’</a>. We discussed <a href="https://twitter.com/susannehusebo">‘How to ask about gender and sex in online forms’</a> and <a href="https://twitter.com/thepreviewmode">‘How do we give feedback’</a>.</p><p>Here are a few trends I personally have noticed after attending the sessions at uncodebar 2:</p><ul><li>functional programming is the next (current?) big thing — we had both an Intro to Elm and an Intro to Elixir session, with the latter taking up not one but two slots</li><li>developers still struggle with how to talk about sex, gender and pronouns or how to ask for them in online forms (this is probably true for product type people as well, judging from the amount of bad examples out there)</li><li>apprenticeships and software craftsmanship are still a hot topic</li><li>as is Diversity in Tech — although we are making progress we are nowhere near cracking this topic</li><li>lots of folks seemed eager to live code their entire session — hats off to them</li></ul><p>We also had a round of lightning talks at the end where one of the attendees, <a href="https://twitter.com/WebDevBev">Beverley</a>, gave her very first talk at a conference. Moments like these is why we keep running codebar events in the first place.</p><h3>Cedric Kisema on Twitter</h3><p>The brilliant @WebDevBev presenting at uncodebar conf #codefirstgirls</p><p>On top of all that we had some delicious food in the form of breakfast rolls and Vietnamese banh mi and played what will most likely go down in history as the most competitive round of bingo. Oh, and some people discovered Pivotal’s ping pong tables.</p><h3>Rich Westerner on Twitter</h3><p>Amazing breakfast and lunch today at #uncodebar</p><h3>Denise Yu on Twitter</h3><p>No tech event is complete without ping pong #uncodebar</p><p>Needless to say we are already planning next years’ event. Here are a few things we would like to do to improve upon the current format:</p><ul><li>run a workshop before the event to help students or inexperienced speakers prepare a talk, workshop or discussion</li><li>create a beginner and more advanced track — invite more newbies to the conference</li><li>have space for shorter and longer talks and maybe even a track for a one day workshop</li></ul><p>Of course none of this would’ve been possible without the support of our sponsors. A huge thank you goes out to <a href="https://pivotal.io/">Pivotal</a>, S<a href="https://shutl.com/uk/">hutl</a>, U<a href="https://ustwo.com/">stwo</a>, D<a href="https://www.duedil.com/">ueDil</a>, <a href="http://www.saccade.co/">Saccade</a> and Prodo for their generous support of uncodebar. We’d also like to thank the attendees who came and made the day what is was. To sum it all up:</p><h3>Octopus in vitro on Twitter</h3><p>Amazing sessions, badass attendees, top notch food, smooth journey, lots of learning, that and much more is #uncodebar @codebar</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532e9cb55736" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/uncodebar-2-bigger-better-more-absorbent-532e9cb55736">uncodebar 2: bigger, better, more absorbent</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increasing diversity in Conference Talk Proposals]]></title>
            <link>https://medium.com/the-codelog/increasing-diversity-in-conference-talk-proposals-7d24a3aa0aa0?source=rss-1e0502ac4382------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d24a3aa0aa0</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[call-for-papers]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <dc:creator><![CDATA[Kriszta Matyi]]></dc:creator>
            <pubDate>Thu, 11 Feb 2016 11:33:55 GMT</pubDate>
            <atom:updated>2017-03-09T14:26:58.276Z</atom:updated>
            <content:encoded><![CDATA[<p>In an effort to attract talk proposals from a more diverse group of people, <a href="http://scotlandjs.com/">ScotlandJS</a> and <a href="http://scotlandcss.com/">ScotlandCSS</a> decided to host Diversity CFP workshops around the UK and Germany leading up to their conference in June 2016. codebar was happy to get involved and help run the London event. Workshops were also organised in Edinburgh, Glasgow, Dublin and Berlin.</p><p>The set up was simple. During the workshop people got the opportunity to work on their talk proposals, with advice from fellow mentors and other attendees. There were video talks from experienced speakers who have been through similar review processes, as well as speakers who have been part of talk proposal review committee.</p><h4>The London Workshop</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojHF4rjF3Ghdk4STh3O_gg.jpeg" /></figure><p>On January 30th we met at <a href="https://www.futurelearn.com/">FutureLearn</a> where the workshop took place. We kicked off the day with an intro of the mentors, followed by a small presentation on ScotlandJS’s CFP process. Next, we watched an inspirational video from <a href="https://twitter.com/rockbot">Raquel Vélez</a> and <a href="https://twitter.com/sarahmei">Sarah Mei</a>.</p><p>Both Raquel and Sarah shared insights from their experience as conference speakers. They offered tips and advice on topics ranging from how to choose a talk topic, to what to do if your proposal gets accepted. Some of the highlights were:</p><ul><li>choose a topic that’s comfortable for you</li><li>don’t worry if it’s a common topic. It’s your personal perspective on it that matters most</li><li>put out a few blog posts and see which one people most respond to</li><li>choose a topic that you are actually interested in; you will, after all, have to write a talk about it</li><li>the title and the abstract is your chance to convince your audience to attend or vote for the talk, so make it a good one</li><li>the more specific you can get in your abstract about what you are going to talk about the better. But also leave some things to the imagination</li><li>explore one topic per proposal</li><li>create a story with your proposal, think more sales pitch than scientific research paper</li><li>make sure your enthusiasm comes across in the proposal</li></ul><p>And, don’t forget:</p><ul><li>you have something interesting to say no matter where you are in your career</li><li>this is supposed to be fun. Don’t beat yourself up over a rejection or the process, try to enjoy it!</li></ul><p>We continued the day by splitting up into small groups. There, the mentors offered help and advice, whilst the participants worked on their proposals. At the end of the day we gathered once again to share learnings and do a short retrospective.</p><p>Part of the day’s feedback? Everyone felt a confidence boost in preparing for a conference talk proposal. Some attendees were inspired to do more writing and be more active in the tech community. Even mentors said they felt inspired and got some new ideas for talks. All in all, we had an excellent time!</p><p>A big thank you to FutureLearn for hosting, to the mentors for their time and energy, and to Peter Aitken and ScotlandJS for taking active initiative to increase diversity in conference talk proposals — we hope that other conferences will follow their lead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d24a3aa0aa0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/increasing-diversity-in-conference-talk-proposals-7d24a3aa0aa0">Increasing diversity in Conference Talk Proposals</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a good beginner open source issue?]]></title>
            <link>https://medium.com/the-codelog/what-makes-a-good-beginner-open-source-issue-5f666c61da37?source=rss-1e0502ac4382------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f666c61da37</guid>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kriszta Matyi]]></dc:creator>
            <pubDate>Fri, 20 Nov 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-09-02T16:17:28.233Z</atom:updated>
            <content:encoded><![CDATA[<p>In the days leading up to codebar’s <a href="http://24pullrequests.com/">24 Pull Requests</a> event, we asked the community to submit good, beginner-friendly issues they found on Github for our students to work on during the event. Our 24 Pull Requests themed event is a day of helping beginner coders get started in contributing to open source software. The most common question we got was what constitutes a good beginner open source issue? The question is valid, especially from the perspective of a seasoned developer who can easily make sense of developer jargon and can understand other developers’ intentions from a few brief sentences. That isn’t the case for a complete beginner. As someone who was once a beginner — some would say still is — I think I can give some tips on what kind of issues helped me get started with open source and what kind of issues might suit other beginners.</p><p><strong>Small bugs, or very small features</strong></p><p>As a beginner it is important to start with small, succinct tasks. Things that can be solved in a day or better, an hour. Remember, when you are a beginner, contributing to open source isn’t only about fixing the bug but everything else that comes with the process: forking the repo, cloning it, setting it up, finding the bug, fixing it, adding, committing, pushing, opening the PR and so on. This might mean relinquishing some control of your project and offering up quick fixes and small features to potential contributors. Yes, you might be able to fix that small bug in two seconds yourself and never think about it again, but for a beginner that two second bug might be the issue that sets them off on a journey of contributing to open source.</p><p><strong>Issues with a clear context</strong></p><p>We’ve all seen issues on Github with a non-descriptive title like ‘remove no-js tags with js’. No description, no context. This in principal sounds like something a beginner with very little Javascript knowledge could do. Right. Detect whether an element has a no-js class and consequently remove it. But the lack of context makes it almost impossible to understand what the actual issue is and what is expected of the contributor. A good beginner issue has a clear description and gives as much guidance as possible without actually solving the issue. You are a project maintainer and might have an idea where in the project the bug might lie? Good, include the partial you think the bug might be coming from. You have a visual representation of the issue? Great, include a screenshot of it. The more details you include the better.</p><p><strong>Projects with a setup guide</strong></p><p>Not once have I found an issue on Github I deemed solvable with my limited skills only to find out the project has no setup instructions. As I mentioned in the first point, setting up the project itself is one of the most daunting parts of starting to contribute to open source. I have personally abandoned several projects because I got stuck whilst setting up the local dev environment and found the effort of reaching out to the maintainer or figuring it out on my own too much compared to the relatively easy task of solving a simple issue. If you want people to contribute to your project please take the time to write clear and detailed setup instructions.</p><p><strong>Responsive project maintainers</strong></p><p>It can be extremely discouraging to finally open that first PR you’ve worked so hard on, to then not hear from the maintainer for weeks, sometimes even months. We at codebar are guilty of this too. It is hard to always be up to date on a project from a maintainers point of view, but it is extremely important for a beginner to get prompt feedback on their PR. Don’t be afraid to give feedback either. If you don’t like the design they did for example, or want them to refactor some code, let them know in a respectful and objective way. The key is clear and respectful communication and collaboration.</p><p><strong>It’s not only about code</strong></p><p>This has been said many times but code is not the only way to contribute to an open source project. Think about all the other components that make up a project: documentation, visual design, UX, user testing, accessibility, etc. These are all components of your project that you can open up to the community. But don’t over do it either. I’ve seen many, many issues that simply stated ‘write documentation for xy’. How would a beginner, who relies on documentation more than anything, know where to start with it? Provide a rough draft of the documentation and ask people to contribute to that.</p><p><strong>Conclusion</strong></p><p>All of this means that project maintainers have to put in the time to create issues that are clear and understandable. It means they have to aid and help out beginners to contribute to open source projects. This may mean holding someone’s hand in fixing their first issue and submitting their first PR on the project. Yes, this takes time and effort, but it’s the only way to build a community of willing participants around a project and to get more people involved in open source.</p><p><em>Originally published at </em><a href="http://blog.codebar.io/2015/11/20/what-makes-a-good-beginner-issue/"><em>blog.codebar.io</em></a><em> on November 20, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f666c61da37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/what-makes-a-good-beginner-open-source-issue-5f666c61da37">What makes a good beginner open source issue?</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>