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 5 years ago.
Improve this question
I'm building a small social networking website for a university project and this question is purely a cosmetic thing.
Basically, my tutors are really anti-table and are very strict on the fact you may only use them for tabular data, but I am not really sure what is and what isn't considered tabular data. Would an inbox be considered tabular data? I would quite like to use zebra striping in displaying this and as the data is rendered dynamically in a loop it would be a pain to do this with CSS and divs.
When, if ever, would you use tables?
Tables are for grids of logically-associated data.
Zebra-striping works the same way - add a class name to every other row.
I would agree you want to use tables when display tabular data so yes an inbox would be an ok time to use tables. The big concern I think people have with tables is when you use them for layout of the entire site. Use div's to layout the site and then tables to display tabular data.
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 4 years ago.
Improve this question
AFAIK people create their own table-like-components and the use of the good old HTML tables is kind of "outdated". Now I'm at the point where I would need a table for my vuejs application. I'm using bulma and the doc states this:
Table
The inevitable HTML table, with special case cells
The "support" badges below that title state that there isn't much support for it (only variables) and the text itself sounds like "well... since so many not-up-to-date-people want it, here, take it".
Should I rather go the "unordered list" way or something else? Like creating a component to represent a row and a component holding the table together? I'm not asking for vue specifically, but for a rather "modern approach" and how to do something like that properly.
The table element is still the correct way to provide tabular data in a semantically correct way in HTML. So if you use it semantically correct it is fine and not outdated per se.
However having that in mind, it might be a valid decision for you to go with new approaches like CSS Grid if that helps you to faster and more user friendly accomplish the creation of new Elements on your website, as the end-user should always benefit from your decisions.
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 5 years ago.
Improve this question
I'm trying to build a HTML email using foundation for emails which seems to have worked well however, I have discovered that outlook 2007+ doesn't like floats, does anybody know of a good alternative?
At the moment my elements are full width instead of floating to the left/right as they should!
Many thanks
I have done a few email marketings in the past months and I can say to you that the best way to build an email marketing is by having some notion of tables and spacers.
Here is a link for a basic tutorial about what I'm saying: Simple Steps For Email Marketing
An email marketing is basically a sequence of table inside tables with a few blank tds usually by the class of spacer.
So here goes some tips that will make it work across all email clients having the tutorial I sent in mind, although I will state that I have never used foundation:
You will need to structure every part of your email inside tables.
Work with all your CSS inline.
Get used to creating spacer (blank tables) to simulate margins that you may then hide in mobile versions.
You need a service that lets you simulate how your email will look in every platform.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I designed a nice resumé template in Sketch and now I want to make it available to use it for the users of a site.
The data will be stored in MySql database and the design should be modular depending on the information.
What is the best way of doing it? I though of replicating the design in CSS3 and then converting it with some of this scripts fpdf or mpdf but I don't thing that it's the easiest way of doing it.
What do you think?
Thanks!
An example of the resumé is the following:
If it's a set template/pattern I'd approach it like each segment as an object with a varying number of attributes based on data it returns from the mysql call.
IE when you pull the data from your table and start looping through a person's skills you can add that to the SKILLS object. Same for the Experience, etc etc.
Since this would essentially be like Parent Child nodes you could also do it with XML but the approach is really up to you.
You could then easily output the constructed resume as HTML (so your users on the site can see it live and may make changes, and then use a converter to convert to PDF (alots of languages have libraries to do just that). Most modern browsers can also already convert HTML pages to PDF too nowadays so you could also give them instructions on how to do that.
Just my two cents,
Hope it helps!
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
So this has been a topic of debate between me and another coder. We are using foundation for a project and he really likes following the system they provide. I like to venture out when it doesn't fit exactly.
An example was this was when I was doing the login form and I wanted a singular sized view that looks the same on every view. I created a login form with a solid width and centered with margins. He comes back to the code and puts it in foundation with large/medium/small columns. The justification was that they know how to handle responsiveness better than us. I just wanted stack overflow's opinion on this one.
When is it right to use a css framework and when should you go outside of it?
I guess on big projects, where you'd like to use each an every feature that a css framework provides, you should go for it. Whereas in small websites, using Bootstrap/Foundation would be a slow-down factor.
Otherwise if you are confident with building a responsive framework yourself, you should go ahead. But, if you feel you aren't take help from others in the form of css frameworks.
This question is way too broad and there can be many possible answers. The above is just my point of view.
First of all if you already have experience with one framework, unless you're doing it for research stick with it.
Otherwise you could check this comparison.
Also if you're using a web framework like Rails, Spring MVC, etc, check the integration status between the both frameworks.
Another point you should care is the community, and in my humble opinion bootstrap wins (as my personal perception).
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I use CSS to stylize my pages. I use % style instead of using px values. However, since I need to add several elements of different sizes in different positions, I end up spending more time in designing the layout than the coding.
I tried using a WYSIWYG editor but it uses px style coding. Can someone help me with a solution so that I can design the layout quickly and proceed to real part? I use WordPad right now.
The best thing to do is practice more. Get better at coding them, and reuse parts from prior projects where it makes sense.
There is no WYSIWYG tool that will save you time, for most projects. They all write garbage code, because editing with such a tool is a bit ambiguous. It is up to you as a web developer to write your markup and styles in a way that will be interpreted correctly across many user agents.