Op wo 29 mrt 2023 om 16:57 schreef sebb <seb...@gmail.com>: > On Wed, 29 Mar 2023 at 15:42, Roy Lenferink <rlenfer...@apache.org> wrote: > > > > I just noticed a broken link in the following blog post: > > > https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023 > > > > The link "Students: read this!" refers to > > > > https://community.apache.org/gsoc.html#students-read-this > > > > instead of > > > > https://community.apache.org/gsoc/#students-read-this > > > > This probably has to do with refactoring the GSoC sections. > > I think it is more likely due to the __index.md renames. > > In this case it was the re-ordering of the gsoc content.
> > Does anyone know who wrote that blog post and how to correct the broken > > link? > > There should be no need to correct the blog post. > > Indeed unless that link never worked, I don't think that is the > correct way to fix a broken link, as it will only fix that instance of > the link. > There may be many others. > > It should be possible to redirect to the updated page using .htaccess > (I'll try and fix that shortly). > I just learned about the existence of Hugo aliases [1] and that seems to work for me locally. See [2] on how this applies to the refactored GSoC content. Do we have a preference on .htaccess (single file with all redirects) vs Hugo aliases (old urls close to the new files) ? [1] https://gohugo.io/content-management/urls/#aliases [2] https://github.com/apache/comdev-site/pull/98 > > Sebb > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
