<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Websites on Lyndon Sanche</title>
		<link>https://lyndeno.ca/tags/websites/</link>
		<description>Recent content in Websites on Lyndon Sanche</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Apr 2021 01:20:00 -0600</lastBuildDate>
		
			<atom:link href="https://lyndeno.ca/tags/websites/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automating Your Resume with Github</title>
				<link>https://lyndeno.ca/posts/2021/04-apr/2021-04-24-online-presence-resume/</link>
				<pubDate>Sat, 24 Apr 2021 01:20:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2021/04-apr/2021-04-24-online-presence-resume/</guid>
				<description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;Making your resume easily available and up to date can be quite the task. The approach I have taken is to host my resume on Github.&#xA;Github has tools that make it easy to have links that always point to the latest version of a file, which is what we need for my approach.&lt;/p&gt;&#xA;&lt;p&gt;What this approach uses:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A repository for hosting the resume LaTeX &lt;strong&gt;code&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Github actions for building the resume.&lt;/li&gt;&#xA;&lt;li&gt;Git tags to tell Github when to build and &amp;ldquo;release&amp;rdquo; the resume PDF.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The final result of this process is something that, when set up, can be operated completely from the Git command line. All you have to do is commit changes to your&#xA;resume repository, then create a tag when the resume is in a presentable state. A link can be put on your website that always points to the latest PDF.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
