Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/wkaisertexas/wkaisertexas.github.io
My portfolio site built as a Static Site using Astro and Deployed to GitHub pages
https://github.com/wkaisertexas/wkaisertexas.github.io
astro portfolio tailwindcss threejs
Last synced: about 1 month ago
JSON representation
My portfolio site built as a Static Site using Astro and Deployed to GitHub pages
- Host: GitHub
- URL: https://github.com/wkaisertexas/wkaisertexas.github.io
- Owner: wkaisertexas
- Created: 2022-02-18T16:24:12.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-11-06T20:39:00.000Z (about 2 months ago)
- Last Synced: 2024-11-06T21:35:13.663Z (about 2 months ago)
- Topics: astro, portfolio, tailwindcss, threejs
- Language: C++
- Homepage: https://wkaisertexas.github.io/
- Size: 65.4 MB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# William Kaiser's Blog and Portfolio Site
After the unmaintainable train wreck which was my past blog and portfolio website, simplifications were in order to more effectively communicate what I do as a programmer.
## Technology
**Astro** forms the near-perfect minimalist framework from which to build a blog. Enough customizability exists in `.astro` files through leveraging the `.md` and `npm` ecosystems to create a great blog. Through **GitHub** pages, the site was able to be deployed so easily and assets be managed with a breeze.
Additionally, for blogs like [Binary to Hex Pratice](https://wkaisertexas.github.io/blog/binary-to-hex-pratice/), I was able to use React with the client load directive to get this game to work.
Common libraries like **TailWindCSS** were instrumental in getting a common and consistent styling.
## Analytics
Because I love tracking things, Google Analytics will be included on every page through PartyTown as per [Kevin's blog on integrating PartyTown Google Analytics on Blogs](https://www.kevinzunigacuellar.com/blog/google-analytics-in-astro/).
## Articles
Articles are important and a key point of differentiation, a way to build repository and more. Adding [structured data](https://developers.google.com/search/docs/appearance/structured-data/search-gallery) would also be interesting. An author is basically all it is. There are also how-to guides which are interesting.
## Theme
A highly-customizable theme is a must and tailwind will play a role in that. However, proper CSS has not been my strongest suit (I use too many div).
Some ones which I liked:
- [brutal](https://developers.google.com/search/docs/appearance/structured-data/search-gallery) a brutalist site which i found refreshing and Google-esque.
- [portfolio with a blog](https://demo.maxencewolff.com) was good. However, too minimal for me.Google's design specification plus notes:
- Google has some things about variable type interfaces which talk about animation, simplicity of interaction and more. Furthermore, [v-fonts](https://v-fonts.com/tags/C20) has some really interesting demos for variable fonts, particularly Merit Badge.
Font decisions:
- **Ysabeau SC** is interesting as well
- **Helvetica** seems like a good choice overall.A great [book on type](https://static.googleusercontent.com/media/fonts.google.com/en//knowledge/stop_stealing_sheep.pdf) from Google. Some notes from this book:
- Grids are **unreasonably effective** I really need to exploit these.
- Darker fonts add to the weight of a letter. To be perceived as the same weight, a lighter font must be larger.[New York Subway font](https://nycsubwayfont.com/#:~:text=HISTORY%20OF%20THE%20SUBWAY%20TILES,enamel%2C%20and%20hand%20painted%20signage.) is something I really like through it's inclusion in the Clarke library.
Germanic typefaces were legible back in the day, but these have aged less well.
### Stripe's influence
I am really liking Stripe and the influence which stripe can have. The 5-column layout is really nice and will be the basis for the blog setup.
## Design-Doc Style
Projects will use the design-document style to provide a consistent way to explain each project. Style comes from _[How to write a good software design doc](https://www.freecodecamp.org/news/how-to-write-a-good-software-design-document-66fcf019569c/)_.
- Context and scope
- Goals and non-goals
- Design
- APIs
- Data Storage
- Code / Pseudo Code
- Degree of Constraints
- Alternatives Considered
- Cross-cutting concerns## RSS
RSS is a great way to get updates, and may not actually be as dead as some people may think.
So, a `.rss` file format is needed. So, the file name will change to `feed.rss` so that this can be recognized.