Skip to content
This repository has been archived by the owner on Sep 5, 2019. It is now read-only.

Person URL #251

Open
freinhard opened this issue Nov 25, 2016 · 3 comments
Open

Person URL #251

freinhard opened this issue Nov 25, 2016 · 3 comments

Comments

@freinhard
Copy link
Member

freinhard commented Nov 25, 2016

A person should have a speaking URL: e.g. /firstname-lastname instead of a UID

e.g. https://www.duerrenaesch.ch/person/3192d39b1c0c4f658eb769cec8613ae0

@href
Copy link
Contributor

href commented Nov 25, 2016

There's a reason why this isn't the case, as there is going to be a /peter-muster and a /peter-muster-2. Who is going to be peter-muster-2? Not the Gemeindspräsident that's for sure. But what if he was added after Peter Muster the janitor?

Hence, no speaking urls.

@href href closed this as completed Nov 25, 2016
@freinhard
Copy link
Member Author

Nicht einverstanden. So könntest du gegen jegliche Email-Adressen nach dem Schema [email protected] argumentieren. Wenn seantis genügend Mitarbeiter hat, gibt es nun mal einen zweiten Fabian.

Wenn die speaking URLs noch wichtig sind für SEO (offene Frage), sollten wir über eine Umsetzung nachdenken.

@freinhard freinhard reopened this Nov 25, 2016
@href
Copy link
Contributor

href commented Nov 25, 2016

So our second Fabian Reinhard get's the address "[email protected]"? ;)

But sure, I'm not against it. Just saying there's a reason why this wasn't done in the first place.
So I'm okay if we go ahead!

Questions:

Should the id change if the name changes?
Should we include the title of the person?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants