Content Management System for front page? #23
Comments
|
We tried Drupal. ( go to https://openwebwork.org) to see the site. Djun Kim set it up ( he is an expert) but then no-one stepped up to do the back-end maintenance and the front page got hacked. (There is still useful info on that site -- in particular the bibliography -- which I have downloaded and saved off line. ) I found Hugo to not be too bad -- it took me a full day to get the templates set up, even using an example, and even now I'd like to return and make some changes. Posting items within the template structure is quite easy -- and you can use markdown which makes it quicker. The fact that you have to grab a copy of the site from github (https://github.com/mgage/demo-home-site), make changes and then issue a pull request to post the changes is a little time consuming but dealing with github should I hope become a common skill among webwork users as we start trying to maintain versions of everything. The version on webwork.maa.org has not been updated in 8 years -- so it's not like we make changes frequently :-) If we go with Hugo I would move the current repository on my site to github.com/openwebwork and set up an automatic rendering so if a pull request is approved the changes appear on the website. I think we could serve the website from github as well, so it's not tied to a U of R server. |
|
The front page looks like it hasn't been updated in 8 years, which doesn't present a great first impression for WeBWorK. I believe that if it were easier to edit the website then we could find people that were willing to keep it up to date. We have had several people without strong technical skills express interest in getting more involved. I think that this would be a good place to get them to help out, and I suspect that learning git, html and markdown will be too much of a barrier. Choosing the right CMS would provide a WYSIWYG editor, which provides essentially no learning curve to updating the website. I'd also like to use something with a news tool where we could post updates of things going on in the WeBWorK world. One thing of which I am certain is that the current raw html pages need to go. There is a lot of duplication of code, and updating them is a nightmare. |
|
Hi Danny,
I’m open to suggestions. The drupal code base (viewed at opensource.com <http://opensource.com/> is also on the machine webwork.maa.org <http://webwork.maa.org/>. I had decided it wasn’t worth
saving except for the bibliography but if you think drupal is a reasonable choice I can back it up and we can set it up on test1.webwork.maa.org <http://test1.webwork.maa.org/>
Take care,
Mike
… On Feb 19, 2020, at 12:08 PM, Danny Glin ***@***.***> wrote:
The front page looks like it hasn't been updated in 8 years, which doesn't present a great first impression for WeBWorK. I believe that if it were easier to edit the website then we could find people that were willing to keep it up to date. We have had several people without strong technical skills express interest in getting more involved. I think that this would be a good place to get them to help out, and I suspect that learning git, html and markdown will be too much of a barrier.
Choosing the right CMS would provide a WYSIWYG editor, which provides essentially no learning curve to updating the website. I'd also like to use something with a news tool where we could post updates of things going on in the WeBWorK world.
One thing of which I am certain is that the current raw html pages need to go. There is a lot of duplication of code, and updating them is a nightmare.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openwebwork_webwork.maa.org_issues_23-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAAJF27BFJL2XT55AC2JGER3RDVRPPA5CNFSM4KXJVMMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMITVCI-23issuecomment-2D588331657&d=DwMCaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=C6Pt5AGtImanmAdcooarL-JZO8M5dSFPfs3VweYXYkE&m=d3YWPUARQfkD5uaekh_6rmGz8_ME74Vtx51ivN9RJKw&s=n4vz9Q6JirrNaWfYUjqV9HG-UueutjKB7-WCi5_V2cA&e=>, or unsubscribe <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAJF27FJLSIQKTGZSKZN4SDRDVRPPANCNFSM4KXJVMMA&d=DwMCaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=C6Pt5AGtImanmAdcooarL-JZO8M5dSFPfs3VweYXYkE&m=d3YWPUARQfkD5uaekh_6rmGz8_ME74Vtx51ivN9RJKw&s=frTYcaeBRMJXWNnh1FpEQFWi0pQXHeeFn6o3Z-a8KA4&e=>.
|
|
I did a quick google search for Content Management Systems. It looks like Wordpress is by far the most common, but it has a bit too much of a blog feel for me. My only direct experience is with Drupal because that's what UCalgary uses for their websites. Drupal 8 (the latest version) is a bit more involved than previous versions when it comes to creating content, so I'd be happy with something more user-friendly, particularly if someone knows of something they like. My priorities are really:
|
Currently the front page of webwork.maa.org is static html, which means editing the source to make any changes.
We should move to some sort of Content Management System to make maintenance easier.
Hugo
@mgage has set up a sample site using Hugo at https://demo.webwork.rochester.edu/public/. The benefit of something like Hugo is that the entire website code can be stored on GitHub. The downside is that there is a significant learning curve to using Hugo, which could easily discourage people from joining the web maintenance team.
Traditional CMS
I'd like to look at using a traditional CMS like Drupal or Wordpress. The largest benefit is the ease of editing the site using the web tools. This would make it much easier to bring new collaborators on board without requiring technical skills.
The biggest downside I see is the back-end maintenance. It is yet another service that would need to be maintained and updated.
The text was updated successfully, but these errors were encountered: