-
Notifications
You must be signed in to change notification settings - Fork 16
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
Better team page organisation #5
Comments
@anandabhishek01555 @likhithnemani Let me know your thoughts. |
We are not familiar with Jekyll instead . Since you say the code will be simpler in Jekyll , I think we should with that . |
Simpler as compared to Angular. Jekyll uses plain HTML in all files and allows us to divide components into separate files. That way we can have a file called - 2019
- Aditya
- Vice President
- LinkedIn: URL...
- key: value...
- Ajit
- Treasurer
- LinkedIn: URL...
- key: value...
- ...
- 2018
- Aditya
- Vice President
- LinkedIn: URL...
- key: value...
- Ajit
- Treasurer
- LinkedIn: URL...
- key: value...
- ...
- 2017
- ... We can then use this file to loop over the data and generate an HTML file. Later you can simply update the data file & HTML updates automatically. Check out their official website for learning more about how it can help us. |
It slightly looks like JSON file and it is also a good way to update details because we don't need to modify HTML file always instead we can just modify in that page. |
If we can all agree on using Jekyll as the base site generator then we can proceed with potential redesign ideas. We need to highlight our achievements, awards & metrics on our home page. |
I agree 👍
…On Fri, 3 Jan, 2020, 22:34 Ajit Panigrahi, ***@***.***> wrote:
If we can all agree on using Jekyll as the base site generator then we can
proceed with potential redesign ideas. We need to highlight our
achievements, awards & metrics on our home page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AK7L5BYWXB5J2WP7UVZ6KPDQ35VZ3A5CNFSM4KCKZIWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIBS2TA#issuecomment-570633548>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK7L5B3PO5UI2WNTG5T67NLQ35VZ3ANCNFSM4KCKZIWA>
.
|
#10 has been created for the Jekyll update. Closing this thread. |
Currently, we are managing team pages as
team-<YYYY>.html
files.The next logical step is to use static data files to generate the pages instead.
Possible solutions:
In our use case, Angular may be overkill for now since we cannot guarantee that every new web dev team will know Angular, nor can we expect them to learn it due to its steep learning curve. In contrast, Jekyll has a much simpler structure and easier to learn.
If there are other ideas, do put them forward. For now, a complete restructuring for this website with Jekyll seems to be the best way to proceed.
Edit: We are currently simply using HTML/CSS(Sass) with Bootstrap 4.1.1 which means for any future update, we need to deal with HTML tags. Jekyll or Angular use data files to generate the file (in Jekyll's case) or dynamically update the file (in Angular's case).
The text was updated successfully, but these errors were encountered: