1 Correct answer
if Dreamweaver has a setting whereby you can enter all of the text for a file in Design View and make multiple changes to properties like you might do in a word processing application. And then switch to Code View to copy the inline HTML and paste it into a CMS code block
By @JohnnyAir
Yes, @JohnnyAir it's exactly as you describe it, you work in Design view mode, you select your text, or the portions of it that need to be modified, and from the property inspector, Ctrl F3, CSS and/or HTML t
...
14
Replies
if Dreamweaver has a setting whereby you can enter all of the text for a file in Design View and make multiple changes to properties like you might do in a word processing application. And then switch to Code View to copy the inline HTML and paste it into a CMS code block
By @JohnnyAir
Yes, @JohnnyAir it's exactly as you describe it, you work in Design view mode, you select your text, or the portions of it that need to be modified, and from the property inspector, Ctrl F3, CSS and/or HTML tabs, you apply the desired changes, depending on whether it's visual or structural... then you just have to copy the generated code to paste it into WP for example.
What you want is an onboard style editor in your CMS site. Ask your developer to create one for you.
By @Nancy OShea
It's not really necessary, as far as WP is concerned, everything will depend on the template you use... but natively WP already comes with a fairly complete text editor, but many templates offer a version better adapted to the internal styles proposed by the visual identity.
That's why it's sometimes simpler to use a DW-type tool to generate in-line code, even if this is counterproductive to the template's visual identity.
That's why it's sometimes simpler to use a DW-type tool to generate in-line code, even if this is counterproductive to the template's visual identity.
By @L e n a
==========
Exactly why smart admins set their CMS sites to ignore code input from non-admins. It preserves continuity of site styles and prevents rogue CMS users from possibly destabilizing the site with spurious code input.
What you do now has consequences later. Modern web design preaches keeping content separate from styles for performance reasons. Inline styles are messy, verbose and can adversely impact page performance because inline styles are not cached as stylesheets are. It creates more overhead for users to load.
I think you should learn to properly use WordPress Child Themes. You're not doing youreself or anyone any favors with inline code. Adding custom CSS from the dashboard is preferred over adding it to HTML.
I use Child Themes (usually Enfold) if I'm building in WP. I use their Quick CSS if I think that the style needs to go into the stylesheet. If I want to make a simple change to a property within a Page that is unlikely to be used anywhere else I use inline. If I subsequently discover that I will use this elsewhere I create a class and add it to a stylesheet. Do you never use inline styling?
If I want to make a simple change to a property within a Page that is unlikely to be used anywhere else I use inline. If I subsequently discover that I will use this elsewhere I create a class and add it to a stylesheet.
By @JohnnyAir
I completely understand your approach, and it's true that here at the studio, I confess, we sometimes do the same.
In the rare cases where we add style on the fly, we add the following comment to the style
/*PEM*/
PEM stands for Puce et Média, our non lucrative's association 😉
In this way, if necessary, it's much easier to retrieve from an SQL query directly in the POST table
...LIKE '%PEM%'
AdChoices