Scaffold article about using frameworks in portfolios
This commit is contained in:
parent
7da300bb8f
commit
e3b247da46
1 changed files with 19 additions and 0 deletions
19
Rants/Portfolios without Frameworks.md
Normal file
19
Rants/Portfolios without Frameworks.md
Normal file
|
@ -0,0 +1,19 @@
|
||||||
|
---
|
||||||
|
title: Stop using frameworks for your portfolio!
|
||||||
|
published: false
|
||||||
|
description: or "why, in my humble opinion, you should refrain from using a framework intended for highly interactive web applications for a simple portfolio site"
|
||||||
|
tags:
|
||||||
|
# cover_image: https://direct_url_to_image.jpg
|
||||||
|
# Use a ratio of 100:42 for best results.
|
||||||
|
---
|
||||||
|
|
||||||
|
So I will admit, that title leans slightly towards click-bait.
|
||||||
|
I am not primarily a web developer nor looking for a job as one and my software philosophy is one of simplicity and minimalism.
|
||||||
|
|
||||||
|
With that being said, I have seen many developer portfolios reaching for modern frameworks built primarily for big, highly interactive web applications, and I believe that might not always be the best approach.
|
||||||
|
|
||||||
|
## Advertise core skills
|
||||||
|
<!-- TODO: Write -->
|
||||||
|
|
||||||
|
## Let your projects speak for themselves
|
||||||
|
<!-- TOOD: Write -->
|
Loading…
Reference in a new issue