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 9 years ago.
Improve this question
And with old web look I mean something like this: http://info.cern.ch/hypertext/WWW/TheProject.html
Now, that's the oldest website. But it doesn't have a lot of content so it doesn't show off that much. I mean like, before good looking CSS. Before you had to worry that much about looks, compared to today. Before CSS if there was that. I am aware that before you styled it with HTML attributes, and not CSS.
So how do I achieve that look? I'm pretty sure different browsers have different default styles, that may vary. So I'm asking for a .css file that makes it all look like back then. Is there such a thing?
BTW, in case you haven't noticed at this point. I love the look the old web had. It's so primitive yet you could make such readable websites, I'm always impressed by it.
So how do I do this? Of course I would be using HTML5 for the structure and CSS for the styling, but I want to achieve that look.
Use pixelated images, ugly animated GIFs, hyperlinks everywhere, poor structure, no CSS, MIDI tracks, and done!
You want UGLY? Ok, I know something ugly. Its called Geo for Bootstrap
Check it out
And I also give you something beautiful
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 2 years ago.
Improve this question
I am new to CSS and I wanted to know what is the best practice Internal Style or External Style or Inline Style as a beginner. Please tell me the basic difference also.
Here, you can find the differences between the three: https://www.w3schools.com/css/css_howto.asp
The most common one on regular websites are external stylesheets. It's the cleanest way because you separate your structure (HTML) from your styles (CSS). Internal CSS is not used a lot when hard coding a website, but it can be legit in some module based architectures. Inline CSS is also used a lot when you work with JavaScript to add styles to elements programmatically.
Edit: as cooskun wrote, the specificity is different between internal/external and inline. Inline get parsed at the end, so it is more specific. With internal and external it depends on which you declare last.
[Please try to Google your question before you post it, I am sure this has been asked before. I am not yet allowed to comment questions]
The first thing is the specificity. I could explain this detailed but it's better to have a look on this fancy website which explains the specificity perfectly.
CSS Specificity
The second reason is the code organization. If you prefer inline-style then you can't reuse your code and it makes the code hard to read, hard to maintain, hard to ...
My recommendation, go with external styles. When you have more experience in CSS, you will know where is the best place to use inline styles.
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
So basically my website works fine, I want to keep all the colors,fonts, etc just the way they are. So what I just want is to make my website responsive for mobile and tablet. I've been looking at Base and Gumby, not sure if those are good choices because I've never worked on them. So basically do I just install the grid system when I want to do something like this ? What's the best framework to use for something like that's not gonna mess with my padding and other stuff that I already have on my website. Thanks in advance!
The non-opinion-based, objective bit
Installing most grid systems on top of your website will likely break some aspects of it. You can't really just plop one in and just use it when you need it, you need to start the design with it and carry it all the way through.
If you want to make it responsive without having to rewrite from scratch, look into media queries, because that's the magic of it.
A CSS framework uses a lot of media queries for the responsive design bit, then bundles lots of stuff on top of it. If you just want the responsive side of things, you can implement your own media queries (common breakpoints are 0-640px for mobile, 641-1024px for tablet and 1025px+ for desktop.
The bit that can get opinion-based if you're not careful (but hopefully isn't, here)
There are a lot of popular frameworks for responsive design (and the whole mcguffins that goes along with them), with two of the most popular ones being Twitter Bootstrap and Zurb Foundation. I'm not promoting discussion of them here, because SO isn't for opinions, I'm just saying that they exist and are widely considered "robust enough" for production work if you want to go look at them. There are many others which are also robust enough.
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
How many lines can a css file have (practically) for good maintainability? I am dealing with a css file which has 15K plus lines. I want a recommendation on this.
The size of an .css file is unlimited.
Like most files, CSS files can obviously be as long as you want. For improved loading times, and like you mention, for ease of maintainability, the shorter the CSS file the better.
15K lines sounds excessive. Where possible, whenever coding, you want to try and follow the general rule of 'never repeat yourself'. There are probably styles in that file that are very similar to one another or just not necessary. I'd recommend (a slightly arduous task) attempting to compress the file as much as possible, and combine or remove styles.
I don't think there is any definitive good practice limit to CSS file sizes. I've never needed one that is longer that 3000 lines, but a very complex site might require a file larger than that. The basic rule is try to make the CSS file as short as possible to achieve what you need to achieve.
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 9 years ago.
Improve this question
A codebase includes Twitter Bootstrap, I can achieve a design for a component without using Twitter Bootstrap classes & elements. I can also achieve the design using Twitter Bootstrap classes & elements, overriding styles that are not applicable (but come with the built-in classes from Twitter Bootstrap). Which approach should I favor?
If the project already includes Bootstrap, it would probably be best to stick to the conventions of the project and use Bootstrap. If you have full control of the project you might want to remove Bootstrap, but either way it would be good to keep things consistent throughout.
Ask other coders you work with. If you're going to rewrite in your own way all the stuff that others are using and getting for free from Bootstrap, you will not make anyones life any easier.
This is probably going to result in very subjective answers, but I'll try to answer as well as I can.
I think it depends on the goals for your project, as well as the target design you have in mind.
If your priority is quick and low effort, maybe you want to use Bootstrap. That's where it seems to slot into development - when you don't want to, or can't, spend the time to do a custom job.
If you're hoping to end up with a project that looks like effort has gone into it, avoiding the cookie cutter feel you get from a popular visual framework is probably worth the effort.
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 9 years ago.
Improve this question
I have a website, and its separated between sections, my question is:
Is it a good pratice to separate the css files for each section?
Ps.: I have a 'global' css stylesheet.
What is it you mean by sections?
General practice (as far as I know) is to have one global style sheet to style the entire look of the site.
From there you can use combinations of minimal inline styling if needed and perhaps other style sheets for specific "plugin" like objects or sections.
In the end it's your call. There are pros and cons to any way you approach it.
With one giant containing style sheet, maintainability can become difficult. Searching through thousands of line of code 3 months later when you need to make a minor tweak is a bit tough.
On the other side, many smaller style sheet means more external file calls from the website, which can slow load times (minimally).
My personal recommendation for using style sheets, use whatever method makes maintainability easiest. Use lots of comments and logical ordering.
For development I would say it is a good practice as it is easier to find what you are looking for faster or to point other developers to where they need to change some code. You can then bring in CSS preprocessors such as LESS and SASS to "build" your CSS for deployment only.
It depends...
If you feel that people may only visit one section of the site, you could avoid overhead by only serving the stylesheet for that section.
If a user will bounce around between the sections, they will need both stylesheets and it makes sense to merge them.
As far as best practices are concerned, there aren't any one size fits all for segmenting CSS. It is generally accepted to just try and minimize HTTP requests and file size as well as reusing code as often as possible. Other than that, you can use your best judgement.