zhehaowang / issue-tracker

Keeping track of what I learnt and scheduling compaction efforts have become such a pain that I need an issue tracker for it.
MIT License
0 stars 0 forks source link

A home for zhehao.me #4

Open zhehaowang opened 4 years ago

zhehaowang commented 4 years ago
zhehaowang commented 4 years ago

Hence the key design goals:

zhehaowang commented 4 years ago

Currently the pipeline looks like

We thought about onboarding arbitrary html (space invader)

The generated site setup (theme modification, google api python client setup) has become non-trivial and we are uploading the generated result to be displayed directly.

Currently theme update and generated content update are two distinct steps in remote. This seems unideal. (submodule? might come in handier as we onboard demos from github)

We should also take another look at haproxy and letsencrypt setup, possibly setup auto cert renewal.

zhehaowang commented 4 years ago

In the initial development with the template minimal, I think we should be mindful of how coupled the approach is to the particular template. The first iteration looks fine though there are a few things I want to try / experiment differently.

Namely, any edits to the theme itself won't be carried over. (Think Search and Gallery)

Particularly when we set up the projects / demo page.

zhehaowang commented 4 years ago

I'm not happy with how the Gallery page is constructed / maintained. Storyboard / Apple newsroom style would seem far more engaging.