1: A few little updates and pondering the Next Thing
Posted by Joe Oldak on 17/03/26 16:50

Hi all,

What Now?

Today I put live a few small improvements:

  • You can now delete non-live revisions of pages in the CMS. This can be handy, for example, if you've been experimenting with a new revision of a page but want to throw it away and try again based on the current live revision. You will find the Delete buttons in the Revisions tab.
  • I've improved the print view of pages considerably - you can try this from a print preview of any page and hopefully it looks good. Though please do point me to any URLs where it messes up and I'll take a look.
  • Fixed the bug with some layout slots not showing up for some people. (see other thread on the forums)
  • Tweaked the HTML template for sites to get rid of an Accessibility error/warning that had been newly flagged.
  • Added a help page about cookies and analytics into the documentation.

What Next?

I went down a bit of a rabbit hole with the cookies/analytics. My first thought was that I should provide an option to add a cookie consent widget to Voice sites for those sites wanting to use Google Analytics or similar.

But then I thought - maybe it'd be better to just make the Voice built-in stats work much better, and provide more useful data, while still not requiring cookies.

So this is sort of where I'm heading at the moment - a revamp of the site stats so that they:

  • Ignore spam bots completely (track using Javascript not the web server logs) to get more accurate page stats.
  • Collect useful info about visitors (country, browser, screen size, referrer) - but not the myriad of complex options that Google Analytics and others provide.
  • Have a nice intuitive and accessible interface to view the stats.
  • Not require an extra login (as you do for third party services)

To that end I have been having a hunt around for possible packages and came across the curiously named GoatCounter. This could fit the bill really well and could be wrapped by e-voice without requiring extra logins. There's a demo of how the stats might look here, should anyone want a look.

 

I would appreciate feedback on this. Is an improvements to the stats something people would like? Or are there other more pressing things you would rather see worked on?

Other things worth considering:

  • Improved default privacy policies and accessibility statements so groups don't need to write their own.
  • Documentation improvements and updates (new screenshots for a start, now that the admin pages are updated!)
  • Anything on the big To Do List!

 

Thanks!

Joe

2: Re: A few little updates and pondering the Next Thing (response to 1)
Posted by Alan-Parry (Euphonix Admin). on 17/03/26 23:56

Hi Joe,

Thanks for the update.

1. I never realised that there was an actual published "To-Do List", so seeing that was great.  Thanks for putting it together.

2. In the Discussion Forum there are 3 threads: Bug Reports, General Support, and New Features & Announcements.  Is there a way for you to indicate that where a system bug has been identified that it has been closed down - or its removal from the list so that only live reported bugs are shown?  Can I also suggest a fourth thread: Suggested enhancements - that could link into your To-Do-List if you think that the proposed enhancement is worthy of consideration.

3. In terms of stats it would be nice to know how many hits a website gets.  But this may be distorted where it has a Members' Area.  With members accessing the website on a regular basis to log into their area, how easy would it be to filter out non-member from member activity on a site?  Personally, I think that there are other areas from your To-Do-List that probably warrant your consideration, although there will be other site admins that would probably be thrilled at having better stats for reporting purposes.  I'm not fussed either way, if the GoatCounter software is relatively easy to incorporate into Voice then perhaps you should go for it.

4.  Following recent issues regarding page layouts I was wondering whether we go about creating new pages without first considering their layout.  When I am creating a new page the first question for me is how do I want my page to look: single column or multiple columns.  At the moment, it is only after the content has been created and saved that I turn my attention onto the layout.  If the layout and the position of the content page were the first question asked then the logical step would be to swop the edit and layout tabs around.  I don't know how feasible this would be, but it would be the logical approach.

Regards

Alan