- Disable duplicated slugs, even for different languages, one slug only can exists one time across the content: (ContentBaseModel::generateSlug) -> If a slug already exists, change the way it´s auto generated for this new one: `{defined-slug}-{language-key}`, if it also exists, append the content id: `{defined-slug}-{language-key}-{id}`. If it still exists, append the counter as currently: `{defined-slug}-{language-key}-{id}-{counter}`
- When quering for slugs, ignore the current app language, just query to find the corresponding content and show it in the current defined language
- `created_at` will remain, but a new field `publish_at` will take the responnsability of being shown / do the sort / filter, so user cannot edit `created_at` but `publish_at`. If a content is in a future date, it won´t appear in the web view filter.
- Sticky content: Selector Called "Sticky" that contains: No, Only first page, Always. By default is No. Content will first be sort by sticky desc and later the corresponding order, later we will have pagination (do not create this, ignore pagination part), when that happens, sticky = Always will be ALWAYS fetch without taking in mind the page, so it must be separated in the sql query