Open zhehaowang opened 4 years ago
Hence the key design goals:
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.
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.
I'm not happy with how the Gallery page is constructed / maintained. Storyboard / Apple newsroom style would seem far more engaging.