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.

Sign up for GitHub

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

Jump to bottom

Migrate to Hugo #50

Open
dannycolin opened this issue Jun 26, 2019 · 0 comments
Open

Migrate to Hugo #50

dannycolin opened this issue Jun 26, 2019 · 0 comments
Labels
discussion enhancement New feature or request
Milestone
3.0.0

Comments

@dannycolin
Copy link
Member

dannycolin commented Jun 26, 2019 •
edited
Loading

Here's a list of reasons why we should migrate to Hugo:

  • It supports translation (Add translations support #43) out-of-the-box
  • Easier to install and run locally.
    • People will be about to test there modifications before pushing to the website in production
    • Help prevent people to crash the website by accident
  • It's faster to generate the website
    • It takes ~6sec with Jekyll to regenerate the website each time you save a modification
  • More powerful template language.
    • Reduce the complexity of the source code
    • Easier to maintain
    • Can add new functionalities to help people how wants to add content to the website
@dannycolin dannycolin added enhancement New feature or request discussion labels Jun 26, 2019
@dannycolin dannycolin added this to the Future milestone Jun 26, 2019
@dannycolin dannycolin modified the milestones: Future, 2.0.0 Jul 9, 2019
@dannycolin dannycolin mentioned this issue Jul 9, 2019
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion enhancement New feature or request
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
1 participant
@dannycolin