I'm building a very niche link shortener. The objectives of the project are 3 fold.
I currently run a site called at http://atmssg.com which shares content so digital marketers can learn how to use messaging channels for marketing.
The link shortener allows people to build deep links into SMS conversations. The target market is people that run SMS marketing campaigns. (links don't have to be short btw)
I was thinking about using a different domain for the link shortener, but just attended a really good pitch about digital marketing and one important point was that everything should go on a single domain.
So my plan is:
atmssg.com - is the blog and content site where I am driving newsletter signups
m.atmssg.com (or maybe a pun like f.atmssg.com) is the application homepage and the web app itself.
Links will shorten to m.atmssg.com/l/slug - and these are the links that people will create and post.
Does this make sense? Am I making an error? Am I overthinking this?
Thanks, for the help.
I have seen something like this where domain.com is the landing page and the main service is running on something like subdomain.domain.com.
And just curious u mentioned the word slug, are u using Django Framework ? XD
Hey, sorry, I didn't get a ping about this comment and didn't check. Thanks for commenting . This subdomain route is what I chose.
I'm using rails and definitely a n00b. I thought slug was a common term for a string that's a unique identifier on a record. Guessing it's a slug because it just sticks at the end of a URL.
Well, that makes more sense.
All the best. Cheers !!
I’m building a link shortener T.LY and the short links are “t.ly/****”. IMO having sub domain and “l” in the route will make it harder for people to type