I'm managing the implementation of Single Sign-On functionality into a suite of websites and want to create the best possible solution for our users.
I would prefer that each user get a Profile Page that has the URL format:
http://website/<username>
But I also need to deliver content from that location, for example:
http://website/news
I can't see how to distinguish usernames from content pages without white-listing every possible content location or placing content in a sub-directory, as in:
http://website/content/news
But this creates unusable URLs for marketing and memorizing, which is why I also want to avoid sub-domains.
I can see that Twitter and Facebook implement this format, ie:
http://twitter.com/help
http://twitter.com/helper
One is a content page, the other an user.
How could this be done without hitting the issues I've mentioned?
Many thanks,
Kevin