Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prune build process #1406

Open
HendrikStrobelt opened this issue Dec 20, 2021 · 3 comments
Open

Prune build process #1406

HendrikStrobelt opened this issue Dec 20, 2021 · 3 comments

Comments

@HendrikStrobelt
Copy link
Contributor

The current building pipeline requires knowledge about Jekyll (Ruby, Gems, Docker,... ) and Webpack (NPM, SASS, NodeJS,...). This makes onboarding of new chairs very very hard and also requires a stack of dependencies that is hard to maintain . Creating a set of static webpages should not be that complex. Maybe focus on a webpack or python stack only.

@HendrikStrobelt
Copy link
Contributor Author

Another example:

  • Where and how is governance/ served ?
  • Why is there one VUE component ?
  • ..

@spetruzza
Copy link
Collaborator

Agreed, for example if we could go down to simple github pages, the entire build and deployment process would become trivial... We'll talk about it.

@yelper
Copy link
Collaborator

yelper commented Jan 3, 2022

Vue component was made by the designer we hired to redesign; it handles the navbar and the accessibility for it.

Governance is placed by the last-built branch, then "placed" by calling https://github.com/ieee-vgtc/ieeevis.org/blob/vis2022/scripts/fix_file_extensions.sh via make2022 (etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants