Conversation
martinthomson
left a comment
There was a problem hiding this comment.
Looking forward to this work being ready.
Are you planning to add a workflow for this?
tantek
left a comment
There was a problem hiding this comment.
Agreed with this direction and simplification.
|
I've made a new website here. To preview, check out this branch and start a local server ( 
|
7c6801f to
3fd8172
Compare
66bf7e5 to
8431e75
Compare
|
This should be ready now, except the GH Actions need a deploy key and environment secret for this repo which I can't add currently. |
This is now done. |
martinthomson
left a comment
There was a problem hiding this comment.
This certainly seems like an improvement.
I have a few questions about the complex deployment architecture here, but I assume that most of this is there for good reasons (that I don't understand). I'm OK with shipping this.
|
Not sure if this should be part of this PR, but it might be a good idea to enable |
|
I would really prefer that we write the content directly into index.html during merge-data instead of loading the JSON at runtime and client side templating (to avoid some of the workarounds for fragment functionality etc). That said, we can work through that in followups, and this is overall a big simplification for the frontend (including removing many dependencies) |
|
I'm good with the change, pending any updates to the actions that you're looking into. |
…merged-data.json.
This changes the data format for activities from JSON to YAML, and uses information from the GitHub issues (the OP and labels). The data is presented on a new dashboard website. There's a workflow to push the
merged-data.jsonfile togh-pagesto publish.