-
Notifications
You must be signed in to change notification settings - Fork 76
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
Use a static site generator ? #4
Comments
According to me, we need not to use it here. Our primary goal is to build a running static website before 18 May. 25 is not such big number and old school copy paste techniques would do great. |
@ansarimofid @KamalAwasthi @mayankpi @Navneet8 Any views? |
Considering the deadline ,copy paste would be good. |
I think this work can be done by copy paste. As we have many collaborators, we can easily distribute pages to work on, if a layout is decided for such type of pages. |
Yes! I would like to go with @singh-pratyush96 . Some minor changes in the code for each page would do the work. And we have many collaborators hence the number of pages should not matter. |
Done then, we are not using a static site generator. Once the layouts are made, individual content pages can be created. |
As there are about 20-25 pages and lots of pages in them will have a common design scheme, I suggest using a static site generator for automation of page generation.
I suggest pelican because it is written in Python which most of the collaborators are aware of.
Once a pelican or other site-gen project is setup on the master branch, we can use TravisCI for auto-pushing the build site to gh-pages.
The text was updated successfully, but these errors were encountered: