And this is configurable, so if you need strict rules because you need to be accessible, you can use it. If you need to be much more easy with it, you can just take it out or just configure the part that you need. And this is quite valuable because you have got this system out of the box without installing new plugins or whatever,

or understanding how to use it, because it's actually quite easy. This also is easy, the visual coherence of the pages, because if you let the user just take care of the body content in a way that they can put there, whatever, or they follow the style guidelines of the site perfectly,

otherwise it will be like a nightmare for who's taking care of the style of the site. You've got warning on the lesson of contents, and this is quite important too, because a lot of times when you are taking out a big, huge set of images that you are already using,

or you are moving an old section to a new version of that section, sometimes the editors are not able to take care of all the cross-links that they are putting into the pages remaining in the site. Plone is taking care of this out of the box, without you having to install anything else.

And this is also good for SEO, again, because of course the broken links that you are creating are much less. You have a system since many years that takes care of scaling automatically the images that you are putting in the system.

That's why we have got both the content type of a file and the content type of an image. The difference is mainly that. So that your editors automatically get their resized scales of the images they use. And this is also good, for example, for the bandwidth.

I don't know how many times you have been called by one of your customers asking for, hey, I'm looking for this page, but it takes forever to finish the charge of this little image. And then you look at the image and actually the image is big like that. With Plone this is quite avoidable, very easily, and without any more plugins you have to add.

There is also the spelling and grammar checker that you can activate if it's available in your language, which is using an outside service called After the Deadline. Any of you is already using this in their Plone sites?

Yeah? No? Hey, you should have a look at that. Probably could be easy for the editors to check their grammar and spell directly into TinyMC, instead of using some external tool. So, my point is that all this is already there.

So we have, okay, a lot of big problems, but still, that is already there. You can use it, you can offer it to your customers, clients, colleagues, and they should be happy with all those features, without asking you to solve their problems every now and then.

So, one nice thing is that I would love to understand how to improve from this point. The point is that we've got a lot of different options to pick from. I've put that research on PyPy, and I discovered more than 3,000 packages.

If you ask for Plone, if you ask for Collective, which is the standard name that usually we use for external packages, the ones that are outside of the core of Plone, you have more than 1,500. So how can you pick the right one for just taking care of contents?

Usually a lot of those packages are the ones that are important for the technical level. But what I discovered is that the ones taking care of the final user are all final applications, Plone board, for instance, or packages for developers.

So this could be also a nice point to discover why it's like that. Probably many more users could be happy with Plone if it could take care more of these kinds of packages, in a way. And I'm sure that a lot of you are developing these kinds of packages. Oh, again.

That's why I hate not to know them all, but I also know that the interesting packages are not more than a few. So, do you recognize from that screenshot what packages I'm talking about here? How many of you?

Okay, the Belgian guys, but no one else. So this is called Collective Jekyll. Someone more? No. So this is an interesting package that Godefroy Chabelle, who knows him, put there like two years ago, probably, or three, and it was under the radar for ages.

And it was also the reason why, after giving this shorter talk at Flock this year, I decided to present this kind of matter also at the conference, because almost no one there was aware of this package. This is so useful. You install the package, and you immediately give your users the hate that a menu like that can give them.

So, for instance, how many times you went online, or some of your internal customers went online with copy off in front of the ID in the URLs? I mean, it's something like, can you believe it?

It would be so easy just to remind them, hey, have a look at the URL, because probably you want to change it, right? All the same, if you need to take care of, say, a CEO, it could be so easy to just make them aware of the fact that, hey, more or less than this number of terms, and no more than that number of terms.

And just a little reminder like this could solve their problem. So, this is specifically one add-on that I would add to the standard set of add-ons within the problem installer from day one.

This is very interesting because it suggests good practices, for instance, both for links, it can check out of the box the correctness of image size, and it is configurable and extensible specifically. So, you can also configure a bit of what you get out of the box from the registry,

and you can also extend quite easily what it can do for you. So, have a look at it if you need to help your users improving the quality of the contents they take care of. Another thing that many people just told me,

yeah, but we don't know this kind of features, let's say. So, you've got a big site, thousands of pages. Of course, along the years, those pages are creating broken links, not just internal, but also towards external services. Any time a final user of those pages is reaching one of those broken links,

it's like you are not fulfilling the promise of a good quality content delivery. So, all you have got, I mean, advanced users that can use this kind of tools on their own, or it's much better if you use something like collected link check or gossip link checker

included in the system to let them be aware of which pages contain broken links. How many of you use this kind of packages in your systems? What about your users? Are they happy? Or are they saying, hey, so many broken links?

Both. At least they are aware, right? At least they are aware. I mean, this is, of course, passive. A passive strategy, but still, it's quite important, according to me. And it can also improve, again, your SEO performance.

Another thing that I wasn't aware of. I mean, you know that in Plone, when you move a content from one position to another, Plone takes care of the old position, so the old URL.

If you are somewhere in the internet, the link towards the old URL, Plone is able to automatically redirect to the new one, and that's good. What I didn't know is that if you install product redirection tool, you've got this also visually in the user interface of Plone.

You can control the aliases you are putting on each page if you need. Please. This tool, if you have a site that's already years old, it continues to track all old URLs. We have the impression that it slows it down a little bit.

With this tool, you can clear those. Out of the box, you've got, when you install the tool that I showed you,

product redirection tool, a control panel where you got all the aliases, right? Yeah, so probably what you could put there is a new user interface where you can filter those, okay, and then select all the filtered ones

and erase them all together from a, let's say, webmaster point of view. That could work, probably, I don't know. Or you could, and that's harder, put the limitation on the number of the aliases you want on each page. I mean, most probably I don't know about that.

But this is already a valuable add-on for the standard Plone, and I don't know why it's not in the core set of add-ons ready to install when it's installed the first time. But this is also giving you an interesting import feature

where you can import a CSV file, and you've got, for instance, a migration going on from a different system, and you can immediately track all the old URL you have into the new ones, and it's quite easy to grasp it. Imagine that something different is like using a Python script,

which I put in the second page I suggest you to have a look at, which is from Mikko, or Toma, if you know him. And it's quite powerful, but still, it's very dangerous too. So that is for developers, right?

There was a question, yeah. The redirection tool is also useful if you get Google search results, and they are pointing, for example, someone used WordPress before, and you switch to Plone, and the people Google for the old WordPress site, and they get URLs which cannot be delivered by Plone,

and you can put the list of those things. That's what I call a migration, yeah, exactly that case. And it's not that, I mean, it happens quite often to migrate a different technology site into Plone, right? At least to us here at a Plone conference. And yeah, if you don't know them, have a look at them.

Probably the second one is for developers, and could save your life still. The first one is for everybody, and it's also useful for having there something like short links, right? So if you have big URLs, it's quite easy for the editor to put their analysis, which is short, really short,

and then later to take it out if they don't need it anymore. It happened to me, so, I mean, better images. It's not a feature that you need all the time, but sometimes it's very nice to give the editors the power feature

of a web editor there in the system, in your CMS. So those are two products that are quite in my mind. Also, if I use the first, I didn't use the second because all the times that I show it, oh, it's too much. I see perhaps someone will need that too much.

So look for Plone app image cropping for take care of your crops instead of the automatic scale that you already have. Or use product image editor. If you are aware of the namespace products, it's coming from, I mean, some time ago. Probably it's the time to renew that with some JavaScript-fancy library

for editing images, perhaps, or not, I don't know. Or some of you know about some better products, and then for you I've got the last slide in the talk. Or, yeah, CEO to the rescue,

in the sense that if you're building a public site and you need good CEO, probably what Plone is giving you out of the box is not enough. One of the things they are asking us, at least, is the fact that they want to have their Google Analytics reports directly on the pages,

and not to have all these two Windows modes where, okay, I'm here, where are my figures in Analytics, and they need to check whatever. So, with the first one collective, Google Analytics just gets that. And you get another nice thing, which is to also track e-mail, comments,

download external links, which usually are not there if you don't activate at the JavaScript level what's needed to Google Analytics to work. With that product, that is a configurable option. Yeah, and there is also this second one,

which is QuintaGroups Optimizer, which gives the editor much more control over the properties that are used by CEO experts. So, it's not my case, but probably you would want to have a look at that, too. Attack them more.

A lot of people are seeing this in Plone because of its flexibility when it comes to classification. So, one nice product which, to me, the same should be in the first set of add-ons already there in Plone Basic Installation. It's the first one, the Plone Keyword Manager.

What about giving the possibility to attacks to your editors when the editors are more than two? In two weeks, probably, the attacks are duplicated, triplicated, quadruplicated, whatever. I mean, with this tool, you just have a configlet in the control panel where you can just pick,

okay, I've got this, lowercase, I've got this, uppercase, I've got this. The same, but with the dash in the middle, let's put them all together. The problem is that if you want to do it with the basic features, you need to find them in all the contents that are pointing to those tags, right? Those subjects, actually.

So, with this tool, it will be really a matter of seconds. And it's quite important to take control of what you are publishing, too. The second one, I need to actually have a really good look at that. No, it's better not. I wrote it, it's, uh, no, um...

No, I'm... It has something that I wrote. You mean the EEA Acme? EEA Acme. No, no, just the tag album. Okay, let's say it later. I mean, the second one. So, that's coming from the group taking care of the European Environmental Agency. Most of you probably already know for the multi-language feature

they've got on that site. But they proposed this package a few months ago, and it's using an external service which is called Acme API. And it promises a lot of good features, and actually, that is the reason why I wanted to have a look at that.

Because, okay, if it's an external service, probably they deliver good quality on what they are promising. And sometimes when you've got a big amount of content that you need to take care of, having something like auto-tagging using natural language processing services, it's a good thing to have. Or, yeah, another thing is the one that he was saying,

which is Collective Tag Helper, but apparently it's better you don't use it. No, no, it's outdated, and it happens. There's a new product which takes over from there, which uses natural language processing in your own site.

We've talked about this at the last slide. Another one, if you need to take care of classification, but from a different angle, is the one called Collective Taxonomy, which gives you a nice feature

to use hierarchical taxonomies on your contents. There are actually many more packages talking about this. What I did at the time was something like a few hours to test them all and understanding the technical details, because then, when you need this kind of solution, you also need to take care about technicalities.

Of course, this is good both for classification, but also for findability. And this leads me to something which is quite related. Relations, and automatic relations on contents when you've got a big base of content to take care.

And the same package from WA is also promising to use those features to create, or actually suggest, references when you are editing a new page, or an old page, whatever, using the set of contents already published on the site.

And there is also the other one, collective sim service, yours, right? And you will suggest it? Ah, yeah. Especially if you are looking at tactile collective sim service, it's very much better. Right now it does related items.

In the GitHub master, there's also now a feature that suggests keywords for you. And that works much, much better than tactile. The main difference, if I can understand it right, is the fact that while the first package is using an external service where you don't get the control,

with the second one you are creating your own service to discover these references, tagging, and the rest. So you are much more autonomous, and you can train the system the way you need. What else? Oops, again.

Okay, QA is also for webmasters, but this is something like a force a bit. In a sense that if someone comes to you and asks, hey, what about your contents base? How many of them are still pending because you don't have the stuff to take care of them? How many are still private?

How many are coming from this user or that other user? With this package from Quinton, you can understand better what's going on in your site. Of course it's important if the site is bigger instead of legal. But still, how many of you already know collective purge by IAD?

This is for, I mean, the backend, right? It's not for the users, but the users are using the caches, also if they don't know. So when you've got something like a listing where a lot of different contents are listed,

how do you know when, for instance, one of those contents is taken into private state? Which is the way to let the Varnish server, for instance, knows about this. One technique that Plone is using at the moment is having Plone up caching, it's told,

and then they use, will use a counter, which is improved anytime you edit any content in the site. But when the site is big, I mean, it's like ever-changing, right? So you cannot cache actually anything. With these products on, which is coming from our friends

at the University of Bologna, Mar-a-Mico, he had the idea of putting all the UIDs of the contents involved in a page into the headers in a way that whenever one of those content is changed, the Varnish server can go and check for the pages containing that UID.

So it's really powerful. Have a look at that. And probably also the quality you are delivering will improve because no more something like, hey, I changed my picture, but why the scaled version is not changed? Hey, I take this new, sorry, new,

I take out of publication this content while still on the listing. Or use cases like that. Catalog quality. This is something like I wouldn't love to say, but still probably some of you experienced this.

Sometimes the mechanism you form are not that good. And for one reason or another, you end with dead brains in the catalog. How many of you don't get what I'm saying? Can you raise your hand? Okay. So, have you ever experienced the fact that,

hey, what's happening in Prune? I've got this listing, I click on the URL there, but then the system is telling me, hey, there is some problem because I don't have this content. What's going on there is the fact that for any reason, the catalog, which is responsible for building all the listing you have there,

is not up to date with the real content published in your site. So, one side effect of this is that it's very hard for the webmaster to take care of these cases. And one thing the webmaster knows is, okay, go there in the ZMI, so in the backend of ZOOP,

go to the portal catalog to go and clean and rebuild the whole catalog. But sometimes it's not enough. So, with this package, catalog cleanup, you get the chance to have the system have a look at all the brains and when it collects a brain which is no more linked to a real object,

it will take care of that and take it out of the catalog. So, if you don't know this, please have a look at it because probably it will solve some of your headaches. But unfortunately, it's a great product and we really...

Good enough. We'll move forward to it, but maybe we have too resourceful, too creative content providers, but they managed to break that. The level of inconsistencies we have will not clean up, but just broke the tool and didn't work.

Oh, sorry. So, did you try to, I mean, talk with the developer of this? On the real data, there are more unique cases that cannot clean up. Oh, for sure, for sure, for sure. Extended consequences.

Yeah, yeah, for sure. So, one point could be reaching the last part of the talk. The idea is great, though. Yeah, the idea is good. I mean, it's solved for us a lot of different questions. Sometimes the customer are just calling us when they are in trouble, right? And the first thing you do is like the basic one,

and this is one of the basics. So, do you have more options? I just have a question. Please. How many of those bridges or the dons would work with Plume 5? With Plume 5? It depends on Plume 5 if it's what we have got in our minds at the moment

or whenever it came out. So, most of them are using basic, most, not all of them, but most of them are using basic features of Plume and Soap as they are now. So, most probably they should continue to work. Some of them are quite old. For instance, the editor for the images, right?

So, we should have a look at something new, let's say. Or the system taking care of the tags, the subjects. I don't know about it, but it shouldn't change at the moment. But just by any chance, you haven't tried it with Plume 5?

Just the one? No, I didn't try it, but what I've got here is... First, whatever you have in mind, do contribute. This is another reason why this tool was for newbies, right? But probably to remind you about you can contribute if you are not already doing it,

this could be a delight for you. How? So, one thing is go and document your cases in docs.plume.org. Okay, so if the cases you have are not already there and you've got better ideas how to improve what the community is suggesting, please go there and tell them,

hey, you know what, this product is not working for us and this is the way we solved it. What about using this best practices instead of what you are suggesting? The seventh one is paragon.plume.org. How many of you already went to the site? paragon.plume.org? Just one, two, three, four?

How many of you don't know what is that? A lot. So communication is not working at the community level. Well, there is a new site or sub-site of Plume where, yeah, let's say the community is asking to the community, please, can you suggest what packages are useful for you?

Whatever package. Not just the one for comments quality. And there is a community, let's say, which will change, of course, every now and then, that will take care of, first, check the product suggested. So are they respectful towards this criterion?

For instance, are they documented, are they tested, are they translatable if they are coming to the user interface, whatever. Second, probably, that will be the basic for something like a distribution in Plume.

A distribution could be something like, whatever, a set of products you can install quite easily into Plume, which are, I don't know, linked together by the fact that they are taking care of comments quality, taking care of multi-language sites, taking care of, I don't know,

sites with a lot of contents inside. So, one thing that you are asking is, will they be ready for Plume 5? Probably, that will be one of the criterion there for letting the product into paragon.plume.org. And of course, that's important.

Any other consideration about this? Are you, some of you I know, of course, and I know that are really good contributors. I don't know all of you, please. The most basic contributions, please find an issue, find a bug report, use another book or something.

We develop this sometimes, we don't know that something is going wrong. Yeah, yeah, actually, the fact that she was suggesting of, okay, the product is not working, for us it was working enough, so we wasn't in a position of contributing an issue,

but they are already contributing it, but I wasn't aware about it, for instance. So, that could be something more spread around as information, also to take care about. For a package like that, for a package like that,

probably the first thing would be to go to the maintainer and ask about it. It's not that easy, but usually there is a mail, so just drop in the mail, hey, I've discovered this, where do you want me to file an issue? Usually, if the package is quite new, on GitHub there is the issue trigger on the package, so it's quite easy.

Still, it's for developers, right? If it's final users that have to be complaining about these facts, it's hard for them, and we should also try to solve that aspect.

How many of you have already filed any issue around Plone? So, most of you. How many of you would have done it, but they didn't know how to do it? So, it's not the right people here. Probably there are people that don't get the community,

they don't know how to get into the community. I mean, it's quite usual if you talk with the final user of Plone. They've got the problems, but they don't know where to file them, because it's just a developer-driven community at the moment. And that's an issue. And that was also quite visible, if you were, in this room half an hour ago.

I mean, we are talking at a technical level about the issues of Plone. It's a Plone conference, so I would expect it, but it's not enough. I don't know your ideas, if you want. I'll back to the issues.

If you really don't know where to file it, put it on the Plone user basis, or on community.plone.org. Somebody will pick it up or say, look, this program has an issue tracker, go there. Yeah, channel's out there, of course.

I think, like you, that it's quite enough, but still it's not really enough if you want to go over all the people using Plone around the globe. For a lot of them, it's just too hidden, right? I mean, the front page of Plone.org should have something much more easy to use and to find when you need it. Hey, I've got a problem. Where should I go?

I don't know, yeah. We need to ask some usability experts, but still, I mean, probably it's not that hard. Yeah, most probably. Do you have an idea around this topic? Are you already satisfied with the thing

that your users are doing with Plone? They are satisfied, I mean, how many trouble they have with broken links, with strange URLs they've got, when they need to open a new section or change what they already have. You never have this kind of troubles.

So I'm unlucky. We have a lot of troubles. It's lost and the way it's implemented. Okay, and how do you plan to solve them, those problems? We're trying, but it's a difficult discussion. They cannot drop acquisition.

It's something you cannot live without. Yeah, acquisition, yeah. I thought about putting there the package they are trying to implement, which is talking about no acquisition there, but it's not ready, yeah. It's not ready and I don't know if it ever will be.

I mean, taking out the acquisition from Plone is like taking out ZOP2, almost, which is one quite big issue we have at the moment because, yeah, a lot of mechanisms are based on that, explicitly or implicitly.

So taking it out will mean that you don't have already a lot of the tools that you are using, so probably it will be for Plone 6, at least from my perspective. I don't know if you are... Whatever the name is going to be. Sorry, whatever the name is going to be, yeah. Could be much easier to have some of the ways

that Andreas was suggesting of using a completely different framework, but then you need to change the name and not just for marketing reason. I mean, it's just something different. So, who knows? Have a new name, Stone CMS.

Any question? Otherwise? Okay, thank you.