257
results for "microformats wordpress theme"
-
Just trying to get the facts here of this number-as-title-for-notes bug. Is this a matter of a theme setting a p-name in microformats when it shouldn’t be doing that? Is there an issue filed on said theme? Is there something blocking a minor mf2 change to the theme?
Zegnat
at
2018-10-04 15:27
-
↩️ That depends on which platform you use. Known, for example, has a lot of it built in. WordPress requires plugins and a theme supporting microformats 2. Perch, Drupal, Jeckill support to varrying degrees.
Loqi
at
2018-09-02 16:46
-
wordpress xml export from the live site, copied theme, restored onto brand new wordpress version
aaronpk
at
2018-08-25 02:16
-
wordpress was surprisingly easy, the theme only needed one change
aaronpk
at
2018-08-25 02:15
-
I will say one thing about wordpress that is nice is their dedication to backwards compatibility. I was able to use the existing microformats theme (2008) on a current version of wordpress.
aaronpk
at
2018-08-24 21:36
-
if you select the microformats filter in the theme area, you get only 375 of 3.443 themes
[pfefferle]
at
2018-08-19 20:52
-
I was wondering if your #indieweb #microformats2 #wordpress mf2_s theme repo is still under active development? It has not been updated for a year. https://github.com/dshanske/mf2_s
Loqi
at
2018-08-07 18:52
-
Hi all, I followed some discussion over the last few days here about use of microformats in wordpress, I am working on something to help me find these uses. By way of a test, I have this report on use of microformats in the twentyseventeen theme. https://gist.github.com/cjwillcock/34e03470bde9df82831a5b573e3691f5
[cjwillcock]
at
2018-08-01 04:02
-
RE: WordPress microformats: I doubt it is a good idea, but definitely more possible in the wp ecosystem would be to have a plugin output hidden `data` tags with all the required markup. It's dirty, but it would work with every theme
[grantcodes]
at
2018-07-30 17:33
-
two things I reguarly see as problematic when pouring over markup on WP sites: a) h-entry on body, so every dodgy class in a sidebar element, menu etc leaks (e.g. the problem above: if the menu were outside the h-entry, nothing would care that there's a u-url where there shouldn't be one) b) plugins adding stuff to the post body, and unless the theme catches it(?) it gets appended to the microformats content, so you get "see
sknebel
at
2018-07-29 20:47