Do we still need /lw prefix? What does it cost to remove it?

[astappiev]

Reasons to remove it:

• Better links autocomplete. An IDE doesn't know about base tag.
• Shorter links

[astappiev]

In GitLab by @PhilippKemkes on Apr 4, 2020, 14:24

I plan to use 2 letter language codes, at least on public pages, instead of lw, to make Google aware of our translations. Then the existing prefix and base path are useful. But it has been in a separate branch for a while and I didn't test it in detail. I do not plan to finish it before V3 is published.

What are other problems besides the IDE?

[astappiev]

Google is only indexing a few pages.

We can leave English unprefixed.

What are other problems besides the IDE?

Can't specify, removed.

[astappiev]

In GitLab by @PhilippKemkes on Apr 4, 2020, 18:00

If you are very keen to remove it then go ahead. We can also use filename.de.jsf or something like that on the public pages.

But we will still need a redirect from /lw/* to /* to keep all old links working.

[astappiev]

In GitLab by @PhilippKemkes on Apr 5, 2020, 10:55

But if it shall be done. Then it should be done before we do the final test round of version3. The rewrite rule should not yet be activated so that we can recognize wrong links.

[astappiev]

One more benefit of having /lw prefix is that we have all pages in a subfolder of WebContent.

[astappiev]

In GitLab by @PhilippKemkes on Apr 20, 2020, 15:30

removed milestone