Remy Perona

Thanks, I’ll add it quickly to the plugin

Great ! Thank you for using my plugin ??

Do you have any white space, or new line, after progrès ?

Can’t seem to reproduce this, did you perhaps added an extra new line in the address field, in the widget settings ?

I released 1.3.1 a couple hours ago, please test it and tell me if it’s ok

This is a contact widget with as little styling as possible, so it’s quite independent of the layout.

I guess you could add as many of this widget as you want in a custom template to recreate the layout you want, but I’m not sure it’s the most efficient way.

Hi,

I’ll fix your point 1 in the next release.

For the point 2, it might be related to your CSS, styling the ‘‘ html markup in black.

I’ll look into it. I need to take the schema.org markup in account before changing anything

Hi,

This is a widget, so to add it on your website, you have to go to appearence->widgets, then drag and drop it in your sidebar. Then You’ll have the settings available right there.

Few options for now, I’ll add more in future releases ??

The company name should be in the company name field anyway, but for your point 2, I’ll try to fix it in the next release.

Hi,

you can do this with CSS with for example :

.vcard { list-style : none; }

No it’s not, it’s to optimize your contact data for local search. Showing your picture next to the google search results is provided by some other plugins (WordPress SEO for example) and requires a G+ account.

I’m not sure I understand what is your problem ?

It’s not really something I can add, because I would have to remove the nested list completely and use another type of (not really clean and semantic) markup, only for IE.

I won’t add twitter and linkedIn fields by default either, because the primary goal of the plugin is to add contact data with microdata/microformats, and there is no existing structured markup for this kind of element.

But if you want to add them for your project, we can discuss it.

I don’t know if you have any skill in CSS, but the workaround might be to add some specific IE styling for nested

inside
• , because it’s really a bug only in this browser.