Mobile app version of vmapp.org
Login or Join

Login to follow query

More posts by @Gretchen104

1 Comments

Sorted by latest first Latest Oldest Best

 

@Ann8826881

This is a good URL design.


The URLs are can be persistent (they contain no parts that are likely to change; name changes are rare).
The URLs are descriptive (users can read the URL and they’ll get an idea what the page is about).
The URLs are browsable (users can remove path segments from right to left, and they’ll get no 404).


It’s also good that they don’t contain any "unnecessary" parts (like, for example, cryptic IDs for person/gallery names). Which, of course, means that you have to take care of edge cases like duplicate person names (maybe append an integer) or same person’s duplicate gallery names (maybe forbid these).

I assume that users get some kind of list of all teachers/students when visiting /teacher resp. /student. In this case, I’d probably use the plural forms /teachers* and /students*:

/teachers
/teachers/john-doe
/teachers/john-doe/biography



But this is only personal taste; singular is fine, too.



Note: In your example, you have written:

/student/student-name/
/teacher/teacher-name


I assume that it’s a mistake and you intend to stick to one variant: with our without trailing slash. Personally, I’d prefer the variant without trailing slash, but again, this is personal taste.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme