View on GitHub

using GitHub Pages

(last modified: Sun Apr 11 00:00:00 2021)

viveret steele

Evolution of a Resume

career resume jekyll
blog projects
How my resume started, what forms it took, and why is it on GitHub Pages now (and why yours should be too)
April 11, 2021

  • very limited much server side logic (a ā€˜staticā€™ site is generated from data)
  • < partial > is converted to <div class="ContentContainer">

    First Review

    testtag
    My first book review

</caption> </figure>

        <div>April 10, 2021</div>
    

    <!-- tags: [testtag] -->
    <!-- category: projects -->
    <!-- Tags / categories -->
    <hr />
    <p>eeeeee</p>

    <!-- <hr /> -->
    <!-- Next post -->
    <!-- Related posts -->
</section>

</div>

  • Markdown (.md) is like a mix between view data (yaml) and view style / internal structure
  • .html template files are like the layout and partial views (https://jekyllrb.com/docs/includes/#including-files-relative-to-another-file)

Reasons for doing this:

  • Cut down on hosting costs (domain, server hardware, electricity)
  • Cut down on maintenence costs (static sites are less prone to unexpected runtime behavior)
  • Shift over to a streamlined development pipeline, from idea to release as a web page
  • Lots of public examples, documentation, and resources (even plugins for common tasks)
  • Make a siteā€™s code public without worrying about particular security risks (thereā€™s no endpoint to pass SQL injection scripts to)