Right, we also need redirects or better to leave it as it is.
Sorry, I'm not familiar with Hugo.

On Wed, Jun 3, 2020 at 10:35 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Please don't change the URLs of existing, published blog posts, this
> will lead to broken links from all our announcements and from any
> site/social media/search engine that has linked to them . If for some
> reason you think this really needs to be done, then you also need to
> add redirects to static/.htaccess to make sure user agents redirect
> from the old URLs to the new ones.
>
> These kinds of changes also need to be introduced in a way that future
> blog posts are also done accordingly: we need updated readme, and a
> corresponding configuration change in Hugo[1] to make this consistent.
>
> zoran
>
> [1] 
> https://gohugo.io/content-management/urls/#permalinks-configuration-example
>
> On Wed, Jun 3, 2020 at 6:52 PM Federico Valeri <fedeval...@gmail.com> wrote:
> >
> > Good idea, fixed all the other posts
> > https://github.com/apache/camel-website/pull/382
> >
> > On Tue, Jun 2, 2020 at 9:58 PM Peter Palaga <ppal...@redhat.com> wrote:
> > >
> > > OK, I have changed https://github.com/apache/camel-website/pull/381 to
> > > yyyy/mm. -- P
> > >
> > > On 02/06/2020 17:33, Claus Ibsen wrote:
> > > > Hi
> > > >
> > > > Yeah that is nice to structure as that.
> > > > Maybe YYYY/MM is just enough.
> > > >
> > > >
> > > > On Tue, Jun 2, 2020 at 3:16 PM Peter Palaga <ppal...@redhat.com> wrote:
> > > >>
> > > >> Hi,
> > > >>
> > > >> the number of subdirectories in
> > > >> https://github.com/apache/camel-website/tree/master/content/blog is
> > > >> getting longer and longer. How about switching to yyyy/mm/dd directory
> > > >> scheme as usual in other blogging systems? I primarily mean to start
> > > >> doing this for new posts from now on.
> > > >>
> > > >> We can discuss later whether it is worth to restructure the existing
> > > >> blog posts somehow (and set redirects of course).
> > > >>
> > > >> Thanks,
> > > >>
> > > >> -- P
> > > >>
> > > >
> > > >
> > >
>
>
>
> --
> Zoran Regvart

Reply via email to