Hi @evotec ,
Thanks for the details and page links.
Could you please add this CSS on your stylesheet and let me know how it goes:
#betterdocs-single-content .markdown-body ul ul {
display: table-column;
}
.betterdocs-content ul li {
display: -webkit-box;
}
As per very different HTML structure(generated from Documents from Git plugin), this is the highest possible way to fix this on your BetterDocs page. The only problem I see with this CSS is not appearing in the bullet point. I would recommend you add bullet points directly from the content.
NOTE: You can simply add custom CSS by navigating to your WordPress Dashboard -> Appearance -> Customize.
After you are on the Customizer page, search for the “Additional CSS” option. You can then go ahead and insert CSS Code.
I hope it helps!
Thank you!
Thread Starter
Evotec
(@evotec)
Hi @abidhasan112,
Thank you for your response.
It seems to fix the inline code blocks, but at the same time bullet points are missing, but also nested bullet points are completely annihilated. Compare 0.0.8 from one page to another and you can notice things going bonkers.
I can’t really really go and change markdown pages and their structure, so the “display” has to work properly – or it simply won’t work.
Przemek
Hi @evotec ,
Actually I’m not sure about this since the structure is very different in that plugin.
However, I will talk to our dev team lead tomorrow regarding this and check if it is possible to fix with some custom CSS. I can confirm you tomorrow.
For the time being, I would recommend you remove the CSS that I gave you above, so that we can check and try with the different CSS.
Thank you!
Thread Starter
Evotec
(@evotec)
Removed additional CSS. Thank you.
Hi @evotec ,
Sorry for the delay.
Please add this CSS on your stylesheet:
.betterdocs-entry-content .markdown-body code {
display: initial;
}
This will solve your issue completely I believe.
Let me know how it goes.
Cheers!
Thread Starter
Evotec
(@evotec)
Yes, works great. Will you be updating your plugin with this code as a way to support it for others?
Hi @evotec ,
This CSS class is actually based on your Git plugin.
So I would recommend you add CSS in your case.
Thank you!
Thread Starter
Evotec
(@evotec)
I understand it’s based on my plugin – but this plugin is available in WordPress Gallery. Anyone can install it. Once installed, and used with your plugin – things go bad. So i wonder who should be the one delivering compatibility between 2 plugins – you or git guy 😉
Of course you may left it always to the users – but at the end of the day it will just trigger more issues like this.
Hi @evotec ,
Thanks for your suggestion regarding this.
Who should be the one delivering compatibility between 2 plugins – you or git guy
– Anyone. But it’s not a good practice to add CSS for a specific plugin. Suppose this(Git plugin) plugin’s HTML structure is different and other plugins have different structures as well. It’s always good practice to make a general CSS which is compatible with most of the popular themes and plugins in WordPress reprositary.
It will just trigger more issues like this
– If this happens, we will differently change our CSS codes. But currently, all popular themes and plugins structure is compatible with BetterDocs CSS.
I hope you understand.
Thank you!
