[postgis-devel] Website Redo change to Hugo

[Regina Obe]

Kristian,

 

Thanks for the suggestion.

 

FWIW I do see the theme I have  has a slot for Plausible. Everyone hates the theme I picked so that might not be relevant.

 

I also see that Plausible uses PostgreSQL as a backend, which is +1 over matomo.

As far as the other pieces in the mix of plausible ClickHouse and Elixir I’m not too familiar with.

 

As far as paying for hosting.  We do have an osgeo budget for these kinds of things. So I don’t think we should rule out tools that have cloud hosting options that cost money as long as they are open source projects.  We should be investing toward open source tools anyway.  I’d just rather put my money against a PostgreSQL backed product than a MariaDb/MySQL one :).  Being able to host on OSGeo infra would be a + especially if we can easily share with other OSGeo projects that would be interested in the service.

 

 

Thanks,

Regina

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Kristian Thy
Sent: Sunday, March 6, 2022 7:09 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Website Redo change to Hugo

 

I've switched to using Plausible (plausible.io) for my website analytics. OSS, self-host or use their cheap hosted plan, GDPR-compliant, no cookies (!), and simple to use.

/K

On 2022-03-04 20:33, Regina Obe wrote:

Yah if we can find a free-for-OSS plan that would be great or go back to good old log processing using something like awstats, grafana, or munin. 

 

I do wonder though how misleading the below stats are aside from the documentation stats.

The documentations stats tell us what people are mostly using., but the ones that come up at the top are predictable. I can tell that just by looking at past days of logs.

 

The 2019 uptick I think was an infrastructure change so not a true reflection of traffic changing.

 

There is just so much that is drowned out now by other sources, it is really hard to get a clear picture looking at stats of our website or popularity.

 

e.g Most people get their PostGIS from package maintainers, docker, or DbaaS. On top of that DbaaS have largely forked our docs, so I suspect people don’t even come to our site for docs as much as they used to. 

 

The desktop / mobile difference I am surprised.  I would have expected more mobile, but then again if I’m a new user looking at postgis, it’s probably to look at the manual or when I’m at work and so I wouldn’t be using my phone for that. It’s not like twitter / facebook where I just want to blow away an hour of time while I’m waiting on some line.

 

Thanks,

Regina

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Friday, March 4, 2022 12:45 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> >
Subject: Re: [postgis-devel] Website Redo change to Hugo

 

Losing analytics just means losing another data point on project popularity. Not that we're making good use of the data points we have now...

 

About 100,000 sessions per month.

A large amount of Chinese traffic, our second biggest language and second biggest country too.

About 3500 active users per day.

About 10000 pages views per day.

Most popular 2nd level page: /install

90% of users still on desktop, 9% mobile, 1% tablet

 

On the one hand... I never look and never share these stats. On the other... they are kind of useful in thinking about what to work on in the web presence, and without analytics we wouldn't have them. Maybe there's a non-google analytics SaaS with a free-for-OSS plan we can plug into so that, even if we are gathering web stats we are at least not doing it into the maw of a huge cross-linker and leverager.

 

P.

 

 

 



 

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220307/465aa24f/attachment.html>