Skip to content

Latest commit

 

History

History
92 lines (76 loc) · 3.85 KB

README.md

File metadata and controls

92 lines (76 loc) · 3.85 KB
Raw

elizabrock.com

Development Setup

This site is generated by Jekyll. Ruby is required to install/run Jekyll.

  1. bundle install to install development dependencies.

You may need to gem install bundler if the bundle command is unavailable.

Running Locally

Run jekyll serve --watch in the root of the project.

Spell Checking

  1. brew install aspell
  2. for f in **/*.md; do aspell check $f; done
  3. for f in *.html; do aspell check $f; done
  4. for f in **/*.html; do aspell check $f; done

Deploying

  1. All code on master is automatically deployed by GitHub once it has been pushed to GitHub.

2020 Personal Site Update Checklist

  1. ✔ Update dependencies
  2. ✔ Set up SEO-friendly redirect from elizabrock.com to elizamarcum.com
  3. ✔ Set up GitHub pages to use elizamarcum.com instead of elizabrock.com
  4. ✔ Update markup (_includes, _layouts, *.md)
  5. ✔ Add Jekyll SEO plugin
  6. ✔ Add Jekyll sitemap
  7. ✔ Set up Google analytics snippet
  8. ✔ Update content
  9. ✔ Headshot
  10. ✔ Bio
  11. ✔ Skill list
  12. ✔ Resume
  13. ✔ Styling, from scratch with new color scheme
  • ✔ General
  • ✔ Don't forget about the 404 page
  1. ✔ Perhaps a little rewriting of git history before moving this branch to master
  2. ✔ Run spell check
  3. ✔ Move Primitive to the vendor folder
  4. ✔ Check on TO-DOs in the code
  5. ✔ Update updated\ats so that the sitemap will be accurate
  6. ✔ Relaunch personal site (by pushing this branch to master)
  7. ✔ Update personal URL on:
  • ✔ LinkedIn
  • ✔ GitHub
  • ✔ Twitter

After the daomin move settling-in period:

  1. Set up SEO-friendly redirect from elizabrocksoftware.com to elizamarcum.com
  2. Use jekyll-redirect-from to:
  • rename /social to /contact
  • set up canonical URLs for the old EBS pages
  1. Cancel Squarespace for elizabrocksoftware.com

Future Improvements

  1. Refine the merely acceptable status of the design implementation:
  • Use the version of the old logo with the outline, since that will look better on the dark background
  • Have navigation mark the current section
  • Separate out my CSS into more appropriately named files
  • Make the nav look better at the in-between sizes
  • Only include the versions of the font that are currently in use
  • Set bq-border to something I actually like (maybe the background blue so that it looks cut out?)
  • Revisit the blockquote markup: http://html5doctor.com/cite-and-blockquote-reloaded/
  • Refine the footer styling when the two halves of the content don't end at the same point
  • Override in my CSS the changes that I made in Primitive's scaffolding css
  • Eliminate unused CSS variables
  • Remove commented out CSS
  1. More updated content:
  • Set proper descriptions on the various pages
  • Update student testimonials with their current job titles
  • Add a link to this repo in the site footer
  1. Improve the case studies
  • Run all the logos through a resizer, a. la Gwen's Cookbook
  • Perhaps use CSS to greyscale the logos (filter: grayscale(100%))
  • Add screenshots of the guided selling tool from iGoDigital, or maybe just embed the video?
  1. Contribute my tweaks back to Primitive UI
  2. Update favicon with new blue color (remember favicon.io)
  3. Update GitHub settings to force https
  4. Take a final pass at my resume to be sure it includes all the cool stuff from my website
  5. Try implementing the skill chart I prototyped here: https://docs.google.com/spreadsheets/d/1-uCwT-ZM0ja8sknY5MjIQfv_uhB6QSa7uFVcxWzDC1c/edit#gid=0
  6. Look in Google Search Console
  7. Confirm that Google still finds the site mobile friendly
  8. Syntax Highlighting?