Jekyll2020-03-11T15:22:55+00:00https://emory-libraries.github.io/feed.xmlEmory Libraries’ GitHub BlogEmory Libraries' GitHub Blog, for the Library Technology and Digital Strategies DivisionHello world2018-12-07T21:18:47+00:002018-12-07T21:18:47+00:00https://emory-libraries.github.io/dlp/scrum/2018/12/07/hello-world<h1 id="hello-world">Hello, world!</h1>
<p>We just kicked off our Scrum Team for the dlp (DLP/Digital Library Program) effort, starting development on our first two products, Curate and “Disco” (pending its final name).</p>
<p>Part of our startup work also involves getting our Scrum ducks in a row, and we’ve been scaffolding our internal processes and understanding of critical work entities into some very interesting outputs: glossary/definitions, entity hierarchies, process maps, tool recommendations, and templates.</p>
<p>After <a href="https://wiki.service.emory.edu/display/DLPP/">spending significant time collecting requirements</a> ahead of a large platform migration, it’s now time to shift into Agile. That meant compiling a large backlog of epic user stories for what ultimately turned out to be multiple products, and analyzing the warehouse of stories to generalize them into key product features. That then informed our v.1/MVP roadmaps which I’ll be adding to our github wiki soon.</p>
<p>Since we’re doing so much setup and startup work, it seemed like a great time to blog our progress along the way.</p>Emily PorterHello, world!Welcome to Jekyll!2018-12-06T17:45:47+00:002018-12-06T17:45:47+00:00https://emory-libraries.github.io/jekyll/update/2018/12/06/welcome-to-jekyll<p>You’ll find this post in your <code class="language-plaintext highlighter-rouge">_posts</code> directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run <code class="language-plaintext highlighter-rouge">jekyll serve</code>, which launches a web server and auto-regenerates your site when a file is updated.</p>
<p>To add new posts, simply add a file in the <code class="language-plaintext highlighter-rouge">_posts</code> directory that follows the convention <code class="language-plaintext highlighter-rouge">YYYY-MM-DD-name-of-post.ext</code> and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.</p>
<p>Jekyll also offers powerful support for code snippets:</p>
<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="k">def</span> <span class="nf">print_hi</span><span class="p">(</span><span class="nb">name</span><span class="p">)</span>
<span class="nb">puts</span> <span class="s2">"Hi, </span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span>
<span class="k">end</span>
<span class="n">print_hi</span><span class="p">(</span><span class="s1">'Tom'</span><span class="p">)</span>
<span class="c1">#=> prints 'Hi, Tom' to STDOUT.</span></code></pre></figure>
<p>Check out the <a href="https://jekyllrb.com/docs/home">Jekyll docs</a> for more info on how to get the most out of Jekyll. File all bugs/feature requests at <a href="https://github.com/jekyll/jekyll">Jekyll’s GitHub repo</a>. If you have questions, you can ask them on <a href="https://talk.jekyllrb.com/">Jekyll Talk</a>.</p>You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.