[Wecount] Process for reporting Web Site Issues? & CMS woes

Fri Jun 26 15:39:47 UTC 2020

Excellent, thank you Cindy!

One note: I don’t really want a sandbox—I more so want to see what a page/post will look like in the editor or preview before I publish it but it’s good to know I can play there if I want/need to😊

I’ll make sure I add any new issues to Github and will add further documentation to existing issues where I can.

Regards,
Vera

________________________________
Vera Roberts, Ph.D.
Senior Manager, Research, Consulting & Projects
Inclusive Design Research Centre
OCAD  University
205 Richmond Street West, 2nd Floor
Toronto, ON   M5V 1V3

T 416.977.6000 x 3954
F 416.977.9844
E vroberts at ocadu.ca<mailto:vroberts at ocadu.ca>

http://facebook.com/ocaduniversity
http://twitter.com/OCAD
https://www.instagram.com/ocaduniversity/

[cid:image001.png at 01D64BAE.7D168970]<http://www.ocadu.ca/ignite>

OUR MANDATE IS NOT SIMPLY TO IMAGINE THE FUTURE,
BUT TO HELP CREATE IT.

From: Cindy Li <cli at ocadu.ca>
Sent: June 26, 2020 11:34 AM
To: Vera Roberts <vroberts at ocadu.ca>
Cc: wecount at lists.inclusivedesign.ca
Subject: Re: [Wecount] Process for reporting Web Site Issues? & CMS woes

Hi Vera,

I’d like to know the preferred process for sharing web site issues. Would you like me to add them to the table

We use GitHub issue tracker to track website issues. I include steps of how to create an issue below. If they are unclear, we can have a meeting with anyone who is interested in this process to walk through it together.

1. Go to Github website<https://github.com/> to create an account;
2. Go to WeCount website issue tracker<https://github.com/inclusive-design/wecount.inclusivedesign.ca/issues>;
3. Make sure you’ve logged into Github;
4. Click “New issue” button at the top right corner to create a new issue, see the screenshot below;

[cid:image002.png at 01D64BAE.7D168970]

5. In the line of “Bug report”, click “Get started” button;

[cid:image003.png at 01D64BAE.7D168970]

6. Fill in the issue title, follow the bug report template to describe the bug and steps to reproduce.

7. Click “Submit new issue” button.

[cid:image004.png at 01D64BAE.7D168970]

I really don’t want to have to use the live site as my sandbox and this problem is exacerbated by the length of time it takes to get to a final version.

WeCount website has a development environment for people to play with:

The dev WordPress URL: https://wecount-dev.inclusivedesign.ca/wp-admin/
The dev WordPress contents will be deployed to a dev weCount website: https://dev--wecount.netlify.app/

Vera, you already have an account on the dev WordPress site. You should be able to use your ocadu email to login. Let me know if you cannot.

Adding a single image took almost 30 minutes today on the We Count site and about 30 seconds on the DEEP web site. Part of the problem is that images don’t seem to play nice on the We Count web site so I had to try many different things to get something that didn’t look completely terrible.

I’m sorry that it gives you so much trouble to add content images. There is an open issue<https://github.com/inclusive-design/wecount.inclusivedesign.ca/issues/137> for supporting content images. We’ll now address it sooner. :) If you have WordPress posts that content images are not displayed as expected, please add comments to this open ticket with post URL(s), Ted and I will have a look.

Whenever you found something doesn’t work as expected, feel free to file a issue ticket or ping Ted or I.

If anything is unclear, let me know. We can also have a meeting to walk through things together if that helps.

Thanks.

Cindy

On Jun 26, 2020, at 9:47 AM, Vera Roberts <vroberts at ocadu.ca<mailto:vroberts at ocadu.ca>> wrote:

Hi Team,
I’d like to know the preferred process for sharing web site issues. Would you like me to add them to the table athttps://wiki.fluidproject.org/display/fluid/Floe+Iteration+Plan#FloeIterationPlan-WeCountWebsite

Or should I make a list and send it to a particular person or come to one of the tech meetings?

Aside from some issues with the web site, I’m also finding the CMS interface we are using problematic and extremely inefficient. A lot of the challenge stems from the fact that I have to publish to the live web site to see how the page will actually render (neither the editor nor the preview provide an accurate version) and it usually takes several minutes for the change to deploy. I really don’t want to have to use the live site as my sandbox and this problem is exacerbated by the length of time it takes to get to a final version.  Adding a single image took almost 30 minutes today on the We Count site and about 30 seconds on the DEEP web site. Part of the problem is that images don’t seem to play nice on the We Count web site so I had to try many different things to get something that didn’t look completely terrible.

Please let me know the preferred process for reporting issues and also let me know if I can help with resolving the CMS issues.

Regards,
Vera

________________________________
Vera Roberts, Ph.D.
Senior Manager, Research, Consulting & Projects
Inclusive Design Research Centre
OCAD  University
205 Richmond Street West, 2nd Floor
Toronto, ON   M5V 1V3

T 416.977.6000 x 3954
F 416.977.9844
E vroberts at ocadu.ca<mailto:vroberts at ocadu.ca>

http://facebook.com/ocaduniversity
http://twitter.com/OCAD
https://www.instagram.com/ocaduniversity/

<image003.png><http://www.ocadu.ca/ignite>

OUR MANDATE IS NOT SIMPLY TO IMAGINE THE FUTURE,
BUT TO HELP CREATE IT.

_______________________________________________
Wecount mailing list
Wecount at lists.inclusivedesign.ca<mailto:Wecount at lists.inclusivedesign.ca>
https://lists.inclusivedesign.ca/mailman/listinfo/wecount

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inclusivedesign.ca/pipermail/wecount/attachments/20200626/678e6087/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5336 bytes
Desc: image001.png
URL: <http://lists.inclusivedesign.ca/pipermail/wecount/attachments/20200626/678e6087/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 73511 bytes
Desc: image002.png
URL: <http://lists.inclusivedesign.ca/pipermail/wecount/attachments/20200626/678e6087/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 48800 bytes
Desc: image003.png
URL: <http://lists.inclusivedesign.ca/pipermail/wecount/attachments/20200626/678e6087/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 95155 bytes
Desc: image004.png
URL: <http://lists.inclusivedesign.ca/pipermail/wecount/attachments/20200626/678e6087/attachment-0007.png>