[Mailman-Developers] Making Hyperkitty more friendly to Search Engines

[Stephen J. Turnbull]

Дилян Палаузов writes:

 > it would be good, if Hyperkitty integrates better with search
 > engines for public archives.

Patches welcome!

There are only about 3 core developers at the moment, and we are
mostly focused on fixing bugs and implementing Mailman 2 features that
are not yet in Mailman 3.  It is very likely that your suggestion will
not get action in the near future.  To keep it from getting lost,
please create (an) issue(s) on the tracker at
gitlab.com/mailman/hyperkitty/issues.

Since you have a bunch of ideas which can be implemented more or less
independently, I suggest that the most effective way to organize them
is to create a "task" issue for each enhancement, and a "checklist"
issue that gives a link to each task issue and a brief description.

Steve


___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

[Mailman-Developers] Making Hyperkitty more friendly to Search Engines

[Дилян Палаузов]

cross posting, since I sent this to mailman-users@, but wanted to distribute 
over mailman-developers@

Hello,

it would be good, if Hyperkitty integrates better with search engines for 
public archives.  In particular:

• generates sitemap files, containing information about each archive page, 
created by Hyperkitty, when was it last modified, how often is the webpage
expected to changes (never) — 
https://gitlab.com/mailman/hyperkitty/-/issues/467 ) . This way, when search 
engines index Hyperkitty archives, they
will crawl just what changes since the previous crawl, and not everything.  
Crawling everything repeatedly generates a lot of server load.

• include metadata about when the hyperkitty archive (article) was published — 
https://gitlab.com/mailman/hyperkitty/-/issues/466 .  Then search
results will show (sometimes) the date of the publication

• tell search engines immediately, whenever new public archive weppage is 
generated — https://gitlab.com/mailman/hyperkitty/-/issues/468 , so that
they can in theory index that webpage immediately.

I have experience on integrating webpages with search engines on the above 
bullets.  If somebody is willing to implement these features in Hyperkitty,
I can answer any questions related to the search engines, not related to the 
code in Hyperkitty itself.


The biggest friends of search engines are fast loading webpages.  Removing the 
dependencies on jQuery in django-mailman3, Hyperkitty and Postorius
would result somehow faster loading pages.

I can assume that some administrators (=me) refrain for letting search engines 
index the archives, because the servers have not enough capacities to
handle the huge webcrawling periodic traffic.  Implementing the above 
suggestions shall remove the obstacle letting search engines index public
archives. 

Greetings
  Дилян
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9