Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I see that most 404 pages (in Html5BoilerPlate for instance) have their CSS included in the page's Html code inside a <style> tag instead of being linked from an external sheet. I'm pretty sure people do this on purpose and has some good reasons behind it but I can't get to figure out why they did this.
It's probably so you don't end up with another 404 trying to fetch an external stylesheet — which would be pretty ironic — and thus have an unstyled 404 page.
On a more serious note, you generally don't want any error pages incurring any additional HTTP requests, since they would be essentially a waste of server resources as well as bandwidth. Error pages are places you don't want users ending up, so you want to make sure they have as little impact on your server (and possibly others!) as possible.
This page is being served because something is missing or broken and the risk of the same issue not allowing the 404 page to load it's external css necessitates the inclusion of the styles in the page itself.
Not a required practice, but definitely a good idea.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
While Single-Page application approach is rising as a web development choice, I still don't understand, practically, how would losing the ability to go back/forward in the browser be an O.K sacrifice? Imagine Facebook without direct page navigation! Is there an essential/direct purpose for SPA I can't get my hands on?
You wont have to give up back button functionality to develop a single page application. HTML5 has a history api (and there's polyfills for older browsers) which allows your to keep back button functioning properly.
The main reason (in my opinion) to go for a single page approach is the more app-like feel it gives you. For example gmail feels more like an app than a web page, and given its purpose, I think that's way it should be too. Another example might be the pixlr online image editor.
Single page approach indeed doesn't suit every purpose, but when you want a webapp to feel just that, instead of a website, then single page might be the way to go.
You mentioned direct navigation in comments, and that's totally doable if it's something that makes sense in your context. Angularjs can do that, and I'm sure pretty much every modern single page framework has a way of implementing this.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I sell a theme for a well known php web script. The theme that I sell is only CSS, I wrote this CSS code and it's about 700 lines of code.
I'm starting to get the suspicion that people are illegally using my theme so my question is, is there a website where I can paste my CSS code and it will check other websites for the same CSS code?
For example, the website CopyScape.com will check websites for matching content, but not CSS.
If anyone can help, it would be great. Thanks!
The ability to search multiple websites for matching or similar code, is a little slow and can be faulted easily.. Say for example, if the css file is generated using PHP and is only visible on a valid / active session..
This would mask the use and ability for someone like google to index it anyway..
Generally people use callback type methods, Say for example... Some where hidden or hard to find... you would have a simple 1 pixel image that is actually a direct/absolute URL to your webserver.
When the image is requested, you have a server side language like PHP grab the requesting URL and log that while still returning the correct 1 pixel image so to them it does not seem obvious what is happening.
As long as somewhere in your template you have a link/script/image/iframe or some other means of requesting a file.. You can catch a few of these people easily..
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am a beginner programmer. I am currently building my third site, but really my first relatively large one. I have a simple question about best practices. I find it much easier to have multiple styles sheets each for a separate section of the site rather than a large single one thats crammed with everything. Is this considered acceptable in terms of best practices?
That depends, there is no clear cut answer.
There are best practices, but they don't exactly translate to something as simple as having only one style sheet, or having several style sheets.
Some things to consider:
Number of requests. If you have more style sheets you also have more requests to the server, which makes the page slower.
Combining rules that are used on several pages in one style sheet can reduce the overall load time, eventhough it means that some pages will load and parse rules that are not used on that page.
Cacheability vs. initial load time. Having few style sheets with a lot of rules means a longer first load time, but once the style sheet is loaded subsequent pages will load faster because the style sheet is in the cache.
Maintainability. If having more style sheets makes the site easier to maintain, it means a smaler risk for having old unused rules bloating the style sheets.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
For a few days now i am looking for a webdesigners who can make my page look nice. All i can find is people that are making .psd files of websites so i can cut out elements and put them on my page. I don't need that. I want someone, who will visit my page, look through my .css file, remake it, and maybe add few graphic elements on site - like logo and/or some icons.
I would do it by myself, but i am very bad at selecting/coupling colors, so i need someone to do it for me.
So, reasuming: how do i search through google to actually find people that can make my page look good by remaking my .css files?
People still go by the umbrella term Web Designers : http://www.hanselman.com/blog/HireAndPayADesignerAndBeHappy.aspx
I generally search css web designers to narrow it down.
Altho this area may seem gray there are a few professionals involved on different aspects of what you want.
The reason behind the confusion is that the same professional might occupy more than one role.
A Web Designer should be be able to do that. And it is required of one the basic knowledge of CSS/HTML alongside with your description.
A Web Ui Engenier is the specialist on CSS/HTML/JavaScript he wont design the interface per say He is the guy who implements it.
And a Web UX Designer is the person who will design the user interface and experience. How it should behave and the UI engenier will implement it.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How to make maintenance document for a website? I've created a site using XHTML ,CSS, jQuery etc. it's big site.
Now i have to write a maintenance document for a site for if any changes comes in future related to design, content and functionality then those things will be handled by someone else.
How and what should i keep in maintenance document.
Your maintenance document should contain a high-level design of what each file contains and the general code structure of the project.
For example, if you wrote some javascript to handle certain events, document those and how they interact with the page.
You should also document any logical groupings you've made. If a folder contains all the XHTML for a certain topic, write those down.
Also give a brief explanation of how you used CSS to layout the page. Which classes are where on the page, and which classes or ids are important.
As for the how, I like to set up a Wiki in such cases, for example DokuWiki. They're easy to understand, and in case of DokuWiki there's no database involved, just plain text files.
As to what, (in addition to what Ben S nicely outlines in his answer) I'd cover
The basic technologies used
Any client-side libraries used and their versions
A rundown on the directory structure
The hosting environment, what is configured where, control panel URLs and the like (never actual passwords)
Names and contact data of contacts (Tech support, etc.) plus any experiences with them (how best to reach them, phone, mail, etc.)