<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bar Horing Amir</title>
    <description>The latest articles on DEV Community by Bar Horing Amir (@barhoring).</description>
    <link>https://dev.to/barhoring</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F181856%2F56e11033-3cf7-4949-9837-74759d5a2b4d.jpeg</url>
      <title>DEV Community: Bar Horing Amir</title>
      <link>https://dev.to/barhoring</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/barhoring"/>
    <language>en</language>
    <item>
      <title>Looking for a Frontend role in Israel</title>
      <dc:creator>Bar Horing Amir</dc:creator>
      <pubDate>Fri, 15 May 2020 06:46:42 +0000</pubDate>
      <link>https://dev.to/barhoring/looking-for-a-frontend-role-in-israel-1jm9</link>
      <guid>https://dev.to/barhoring/looking-for-a-frontend-role-in-israel-1jm9</guid>
      <description>&lt;p&gt;Experienced Software engineer is looking for a position in Israel. &lt;br&gt;
I am passionate about web technology and looking to become a top-notch Frontend developer.&lt;/p&gt;

&lt;p&gt;Contact me via LinkedIn&lt;br&gt;
&lt;a href="https://www.linkedin.com/in/bar-horing-3370a3130/"&gt;https://www.linkedin.com/in/bar-horing-3370a3130/&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Host you static site on Github</title>
      <dc:creator>Bar Horing Amir</dc:creator>
      <pubDate>Mon, 20 Apr 2020 09:35:15 +0000</pubDate>
      <link>https://dev.to/barhoring/host-you-static-site-on-github-3577</link>
      <guid>https://dev.to/barhoring/host-you-static-site-on-github-3577</guid>
      <description>&lt;p&gt;If you've created your site by hand like it's the 90's, then simply push your static assets to a remote branch called &lt;code&gt;gh-pages&lt;/code&gt; and you're all done.&lt;br&gt;
Your site is now live at &lt;br&gt;
&lt;code&gt;https://&amp;lt;USER_NAME&amp;gt;.github.io/&amp;lt;GITHUB_REPO_NAME&amp;gt;/&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;If you are using any kind of boilerplate code (like create-react-app or Gatsby) you would have to generate your code as static assets. However &lt;em&gt;before&lt;/em&gt; you perform the build you need to set the &lt;code&gt;homepage&lt;/code&gt; property in your package.json file to point to your Github repo.&lt;br&gt;
If you don't have a Github repo ready yet, don't worry because we will create one shortly.&lt;br&gt;
The reason for doing this is to tell the bundler (Webpack, Parcel) to treat the &lt;code&gt;\&lt;/code&gt; path as the value you provided in package.json. &lt;/p&gt;

&lt;p&gt;So, in your package.json:&lt;/p&gt;

&lt;p&gt;{&lt;br&gt;
..&lt;br&gt;
&lt;code&gt;"homepage": "https://USER_NAME.github.io/**GITHUB_REPO_NAME**",&lt;/code&gt;&lt;br&gt;
..&lt;br&gt;
}&lt;/p&gt;

&lt;p&gt;Make sure to enable Github Pages in Settings -&amp;gt;&lt;br&gt;
GitHub Pages&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--diRFN_iD--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/8sw0ky0amy7baozaxljf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--diRFN_iD--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/8sw0ky0amy7baozaxljf.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now, create a new branch called &lt;code&gt;gh-pages&lt;/code&gt;. Naming is important here, this is a Github thing. (You can &lt;a href="https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site"&gt;confige your static site&lt;/a&gt; to point to your docs folder on the master branch)&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;git checkout -b gh-pages&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;Now run the build command, probably:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;npm run build&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This will create a build (or dist) folder with your compiled code.&lt;br&gt;
Now, replace the root folder's content with the content inside the build directory.&lt;br&gt;
Simply remove all files and folders in the root folder, including the build directory, and spill the contents of the build dir into the root. If you've done the previous operations in reverse order it means you're following me 'till here.&lt;br&gt;
Remember to keep your .gitignore. README and package.json are optional&lt;/p&gt;

&lt;p&gt;Now push your branch to Github or create a new &lt;a href="https://github.com/new"&gt;repository now&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Your site is now live at &lt;code&gt;https://&amp;lt;USER_NAME&amp;gt;.github.io/&amp;lt;GITHUB_REPO_NAME&amp;gt;/&lt;/code&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Boilerplate for Chrome new-tab-override extension 🎊</title>
      <dc:creator>Bar Horing Amir</dc:creator>
      <pubDate>Tue, 25 Jun 2019 19:30:30 +0000</pubDate>
      <link>https://dev.to/barhoring/boilerplate-for-chrome-new-tab-override-extension-2f9</link>
      <guid>https://dev.to/barhoring/boilerplate-for-chrome-new-tab-override-extension-2f9</guid>
      <description>&lt;p&gt;I created a boilerplate for a Chrome new-tab-override extension.&lt;br&gt;
Remove the burden of the setup and start developing. More on &lt;br&gt;
&lt;a href="https://github.com/barhoring/chrome-new-tab-override-boilerplate"&gt;github&lt;/a&gt;&lt;br&gt;
If you like it I'd appreciate your starts ⭐&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>react</category>
      <category>parcel</category>
    </item>
  </channel>
</rss>
