-
Notifications
You must be signed in to change notification settings - Fork 43
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
Big changes to the 3 layouts (KOSS documentation, website and Blog) #177
Comments
The website's code is a mess. Our batch worked on it as it was a team
activity assigned to us. But as a result of too many contributors, the
codebase turned out pretty ugly. I suggest we use a simple custom template.
This would help us in -
1. Having a readable code base
2. Way less effort to set things up and moving.
We can pick up something from
https://onepagelove.com/templates/free-templates or similar websites
…On Sat, Feb 2, 2019 at 6:28 PM Himanshu Mishra ***@***.***> wrote:
The current website structure needs change. We are not using HTML
templating and thus it is hard to update. Here is an email I wrote long
time ago
<https://groups.google.com/d/msg/kossiitkgp/IhajjJPnmYk/bvZwBihqAAAJ>
1. Gruesome task of updating kossiitkgp.in, a statically hosted website.
The website receives a lot of traction, and it is expected from us to update it regularly with upcoming events, documenting previous events, documenting about our current executives and former members, and many many things. The repository is not frequently updated (except for bot pushing our contribution charts). Even if I want to add a new page for our recent most event or add it into the page of events, I can not dare to it, considering my most of time will be spent on finding the appropriate div elements and copying template HTML file to create a new one.
So, we need to design HTML templating structure for all the three (one
single/similar layout):
- KOSS Documentation (docs.kossiitkgp.org or kossiitkgp.org/docs)
- Blog (blog.kossiitkgp.org)
- The new website (kossiitkgp.org)
We can use the previous design for the website, but the code needs to be
updated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#177>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEMt93BkZuOVuigbJgl0UB90KQKGncFeks5vJYthgaJpZM4aflFn>
.
--
Dhiraj Kumar
Pre Final Year Undergraduate Student
Department of Industrial and Systems Engineering
IIT Kharagpur
|
Why don't we use jekyll templates for hosting static pages? It is easy to add and change the content, instead of using html templates. |
@yashrsharma44 We need to use templates, yes. The current website was developed way in the past (when we didn't know how to create websites) :D We can use any static site generator, which suits our purpose. People are rooting for hugo (https://groups.google.com/forum/#!searchin/kossiitkgp/hugo%7Csort:date/kossiitkgp/bDo_O2RApiM/s9IU5Zm4DgAJ) |
The current website structure needs change. We are not using HTML templating and thus it is hard to update. Here is an email I wrote long time ago
So, we need to design HTML templating structure for all the three (one single/similar layout):
We can use the previous design for the website, but the code needs to be updated.
The text was updated successfully, but these errors were encountered: