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

Migrate to Gatsby #410

Open
4 tasks
kbariotis opened this issue Jun 2, 2018 · 4 comments
Open
4 tasks

Migrate to Gatsby #410

kbariotis opened this issue Jun 2, 2018 · 4 comments

Comments

@kbariotis
Copy link
Contributor

kbariotis commented Jun 2, 2018

Jekyll served us well but unfortunately, we've hit a point where development is not fun anymore and the tools right now seriously slow development. Moreover, Jekyll doesn't support modern mechanisms like code splitting and PWA features.

Gatsby is a modern static site generator based on React and Webpack while it implements a GraphQL server to feed data. It provides most of the functionalities we are looking for out of the box.

In order for us to do the migration though, there are is a thing we need to take care first and that is to remove the Bootstrap dependency which depends on a global layout stylesheet and on jQuery. Things we need to tackle are:

  • Implement a Grid alternative, probably react-flexbox-grid
  • Implement a responsive navigation top menu
  • Implement an alternative to Bootstrap's tabs module
  • Pass our data to Gatsby's GraphQL system in order to be used by the components

Other stuff might come out along the way and they will be stated here.

That would also be a great opportunity to get to know more Gatsby as it's a great and battle-tested tool.

@varemenos has already started working on the basis for the new project here

/cc @modkaffes @joskar @alexspyr Thoughts?

@modkaffes
Copy link
Contributor

modkaffes commented Jun 2, 2018

I agree 💯%.
Besides the technical hurdles, this is a great chance to sit down with the design team and whip up a design system, too. This will allow for faster and more consistent component-based development.

@joskar
Copy link
Contributor

joskar commented Jun 3, 2018

Also I think this is a good time to rethink the modeling of the data.

@alexspyr
Copy link
Contributor

alexspyr commented Jun 5, 2018

I agree that Jekyll is giving us a hard time ( although I have limited experience with it). Also I like the idea of using React components 👍 What's the timeline for the migration?

@kbariotis
Copy link
Contributor Author

kbariotis commented Jun 5, 2018 via email

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

No branches or pull requests

4 participants