HugoGresse
Make urls prettier using a slug instead of ids
It would be nice to have pretty urls:
For an exemple:
https://openfeedback.io/fraug/meetup-de-mars
instead of:
https://openfeedback.io/fraug1/2020-03-18/T8TKoqFcsVo0ugLVgSXl
That would make it easier to remember and link the urls.
I believe changing an event id shouldn't be complicated, some logic as already been done for the "project/event" id.
Quick update as of today:
- Event custom id is possible when creating a new event below the event name (and only when creating it)
- If all talks don't have startTime, the talk url will look like
openfeedback.io/eventid/0/talkId
The only missing part is the custom talk id though it is possible to achieve that using the JSON or Hoverboard event type where the id is given by the external db.
It seems weird to have a choosable talk id, do you think having just an incremental number starting from 1 as the id is ok?
Ideally, it would be great to have another level of indirection. A table that maps from a slug to the talkId and remembers when the slug changes so that it can redirect:
https://openfeedback.io/fraug1/2020-03-18/le-point-sur-les-applis-covid => talkId0
https://openfeedback.io/fraug1/2020-03-18/lancement-android-11 => talkId1
// Now we decide to change the title of talkId1
https://openfeedback.io/fraug1/2020-03-18/android-11-all-the-things => still uses talkId1 behind the scenes.
// Extra points for making https://openfeedback.io/fraug1/2020-03-18/lancement-android-11 redirect to the new slug
It might not be easy to do though 😁