Queries regarding the project "Migrate Floe and fluid project website to Hugo"

[Ned Zimmerman]

Hi Sachin!

One other static site generator you might want to explore is Eleventy (https://eleventy.dev). It’s very fast (like Hugo) and very flexible, and one other advantage it has is that it’s written in JavaScript and is very extensible, so if you can write JavaScript you can write your own plugins and data processing tools. Simon Bates and myself have both used it and quite like it.

Cheers,
Ned Zimmerman
—
Ned Zimmerman (he/him)
Senior Inclusive Developer
Inclusive Design Research Centre, OCAD University
https://idrc.ocadu.ca

From: fluid-work <fluid-work-bounces at lists.idrc.ocad.ca> on behalf of Justin Obara <obara.justin at gmail.com>
Date: Monday, February 24, 2020 at 12:24 PM
To: SACHIN CHOPRA <schopra at mt.iitr.ac.in>
Cc: "fluid-work at lists.idrc.ocad.ca" <fluid-work at lists.idrc.ocad.ca>
Subject: Re: Queries regarding the project "Migrate Floe and fluid project website to Hugo"

Hi Sachin,

If you’re going to look beyond Hugo, I might suggest also looking beyond Jekyll to see what else is available out there. You can see more options from https://www.staticgen.com and other places on the web.

Thanks
Justin


On Feb 24, 2020, at 1:39 PM, Jonathan Hung <jhung at ocadu.ca<mailto:jhung at ocadu.ca>> wrote:

Hi Sachin,

Apologies for this duplicate email. I had replied to your previous email, and I am now replying to the mailing list.

Thanks for your interest in this project! I hope I can answer your questions:


  1.  The major goal is to make the website easier to maintain and update. Speed of building isn’t a concern as these websites are relatively low traffic. Docpad is no longer meeting our needs because Docpad is no longer maintained by the creator, and lacks support for more modern technology (for example, Docpad is not compatible with current versions of node.js). Also Hugo is easier to work with, which is desirable when working with people with different technical backgrounds.
  2.  For now we aim to keep the same design with some minor fixes and tweaks. The work of this project is primarily focused on the backend of the sites. If there is time, moving to a more modern CSS framework would be desirable but not a requirement.
  3.  You are correct. Floeproject is made using hand-written HTML and CSS which is hard to maintain (hopefully moving to Hugo can help). Both websites are hosting on our own servers and deployed automatically using webhooks. For this project, we will need to set up development site so the any work can be done without affecting the website that is currently in production.
  4.  We are using Hugo because it is a platform our organization has used in the past for other websites. However, we would be open to using Jekyll if there is a good reason. Perhaps part of your project proposal can include research into both these platforms and report on the advantages and disadvantages of both choices.

I hope this answers your questions.

Sincerely,
-Jon.

---
Jonathan Hung, Inclusive Design Collaborator / Researcher
Email: jhung at ocadu.ca<mailto:jhung at ocadu.ca>
OCAD University
Inclusive Design Research Centre



From: fluid-work <fluid-work-bounces at lists.idrc.ocad.ca<mailto:fluid-work-bounces at lists.idrc.ocad.ca>> On Behalf Of SACHIN CHOPRA
Sent: February 24, 2020 11:41 AM
To: fluid-work at lists.idrc.ocad.ca<mailto:fluid-work at lists.idrc.ocad.ca>
Subject: Queries regarding the project "Migrate Floe and fluid project website to Hugo"

Hello fluid community,
I am Sachin Chopra and I have few doubts/queries regarding the project "Migrate Floe and fluid project website to Hugo" . I posted these on IRC channel too but couldn't get the answers. I'd be really thankful if someone from the community could answer these.

   1) What's the major goal behind this project? Are we trying to migrate to Hugo so as to achieve faster build times? What are the major issues with present format or Docpad that we have to rectify which Hugo can solve?
   2) While migrating to Hugo, do we need a complete new design and look for the website or do we have to stick to the present design/UI?
   3) Currently, floeproject is not using any static site generator and fluidproject uses docpad. Are they both being hosted on gh-pages or do we use third party services like AWS or Azure for hosting them?
    4) Is there a restriction on using Hugo only as the alternate static site generator? Or can we discuss using Jekyll as an alternative to Docpad?

I believe that everyone interested in this project would have these questions in mind and if one of the mentors could answer them, it would really point us in the right direction to move ahead with the project.
Sorry if this mail causes any inconvenience.

Thanks and Regards
Sachin Chopra
@sachin10101998 on Github

_______________________________________________________
fluid-work mailing list - fluid-work at lists.idrc.ocad.ca<mailto:fluid-work at lists.idrc.ocad.ca>
To unsubscribe, change settings or access archives,
see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20200224/7414031e/attachment.html>