Tag Info

New answers tagged

1

I don't have any resource to suggest you but planning this kind of work should be similar to planning an app or a dynamic website. From what I understand, you'd like to know how you can show to your superior a nice "proof" or first draft of your interface to give them a feel of the process and how it will work. The plan First step will be to make a plan ...


-1

A way to get a "resource" for the design is just looking at other examples (movies, designers, video games, etc...) then you can try to sketch it on paper and see how it looks,try to use max 3 colors since it's a HUD, in my experience it's the best way to get something done. First: analyze all the elements that a HUD requires Second: find the idea see ...


2

Coming from a solutions architect perspective, I have never seen a guideline. But there is a good technical reason for making your site at runtime use "www.", and it's all about DNS (avoiding collision with SOA and NS records). So while you might want to share content that says "go to http://mysite.us" the actual hosting should be on "www.mysite.us". ...


3

To add more technical background to the existing answers: Why would there be differences in DNS between www.example.com and example.comin the first place? There are many cases when one does not enter an A (or AAAA) record, but instead a CNAME record pointing to something like www42.provider.example.net. This way, a migration of www42.provider.example.net to ...


0

www.foo.com is not strictly speaking a URL. It's a relative domain name. It means this: start with your local domains, falling back to the root if you can't find anything there and traverse through com and foo to get to www. It doesn't say what records to grab from that domain though or what you would do with those records if you did retrieve them. Most ...


0

To explain what the differences are. example.com is the domain name. www in this case (www.example.com) is the subdomain www. in the configuration people actually have to direct both www and subdomain-less to the same resources (web files) Also keeping SEO in mind it's important only one of these is leading and the other should direct to the leading one. ...


40

www.example.com and example.com are two different addresses. It is only a common convention for web servers to be configured such that both variants work the same. This convention is not universal, and some web sites will be set up only to respond to one or the other. You need to confirm with whoever is in charge of the web site, which is acceptable to ...


14

www. may have valid technical reasons for being used. When a server is configured it must be set up to use http://www.example.com and http://example.com. It is completely possible that www.example.com loads the site and example.com does not. They are two, different, separate, addresses. This is all controlled by the server. Both addresses may work, or one ...


0

Yes, according to the description you made of your use of the design, it would be easy to see some infringement there... especially if you also make reference to the book. To give you a guideline, the court logic would be: "Would your design look the same if you removed the elements that were copied?" and "If the copied elements were removed from the ...



Top 50 recent answers are included