Problems, need help? Have a tip or advice? Post it here.
4 posts Page 1 of 1
Basically there are times when I'm using a CMS that has a WYSIWYG editor like CKEditor or TinyMCE and I'll be moving stuff over from someones old site to the new site and adding the old content into the website using the CMS editor.

Sometimes I'll have to apply some inline styling in the source view of the WYSIWYG editor to make sure things are positioned right, but this makes it so if the client wants to do something like change the alignment on a particular element, it will mess things up.

Or there may be times when I have to stick some things in a table so that the layout will work and at the same time have it make sense and make it easy for the client to edit.

There are times when we're going over the final parts of the site after the client has had a chance to play around with the CMS, and they're like, "I was having trouble moving this over here" and I have to figure out the best way to get it to make sense to them using the CMS tools. It's very tempting for me to be like, "Oh I'll fix that real quick" jump into the source view, apply an inline style and call it fixed. But that's not practical and kind of defeats the purpose of the CMS.

I may have a staff page that has peoples profile image, name and title all wrapped up in named divs and spans, but in the CMS, if the client needs to add or edit a profile, it maybe difficult to make changes because they can't see where one div stops and one ends and it's easy for them to break it. Or if they successfully copy/paste a profile and use the CMS image upload abilities to put someones picture in, they may end up uploading an image that's 2000px by 1500px and has the wrong proportions and doesn't match any of the other profiles.

Anyway, does anyone else run into these types of issues and how do you handle them?
@rajputhitesh

Hota hai bahoot baar.

Sometimes I'll have to apply some inline styling in the source view of the WYSIWYG editor to make sure things are positioned right, but this makes it so if the client wants to do something like change the alignment on a particular element, it will mess things up.

Or there may be times when I have to stick some things in a table so that the layout will work and at the same time have it make sense and make it easy for the client to edit.

There are times when we're going over the final parts of the site after the client has had a chance to play around with the CMS, and they're like, "I was having trouble moving this over here" and I have to figure out the best way to get it to make sense to them using the CMS tools. It's very tempting for me to be like, "Oh I'll fix that real quick" jump into the source view, apply an inline style and call it fixed. But that's not practical and kind of defeats the purpose of the CMS.


i usually copy the content to a notepad to remove all classes/styles implemented and then copy from notepad and paste in the couch back end.

while for:
I may have a staff page that has peoples profile image, name and title all wrapped up in named divs and spans, but in the CMS, if the client needs to add or edit a profile, it maybe difficult to make changes because they can't see where one div stops and one ends and it's easy for them to break it. Or if they successfully copy/paste a profile and use the CMS image upload abilities to put someones picture in, they may end up uploading an image that's 2000px by 1500px and has the wrong proportions and doesn't match any of the other profiles.

CouchCMS really helps us to edit exactly what we want.

For example:
Code: Select all
<div class="staff-container">
     <img src="image.jpeg" class="staff-image" />
</div>

with couchcms you do not need to worry about the "staff-container" and "staff-image" definition.
You can create an editable region for the image and call it. for the above example i would do:

Code: Select all
<cms:template>
     <cms:editable name='staff_image' label="Staff - Image" type='image' show_preview='1' preview_width='100' />
</cms:template>
<html>
     <head>
          ...
     </head>
     <body>
          ...
          <div class="staff-container">
               <img src="<cms:show staff_image />" class="staff-image" />
          </div>
          ...
     </body>
</html>


and the output will be perfectly what you are expecting. This is why CouchCMS is also called a retro-fitting CMS.

Please feel free to try the CMS once. To get started go through the tutorial here. And you will be good to go. The tutorial will take hardly a few hours to go through.

Regards,
GenXCoders
Image
where innovation meets technology
Yeah. Clients are responsible for the content. Why do you even make them think about rest?
Hi,

Did you try MOSAIC feature of Couch?

Very powerful stuff for creating manageable content easily. I almost don't use richtext field.

For content, I usually make tiles for couple variation of text boxes, quotes, images, videos, charts etc.

User can easily manage content and you can later add new tiles for her/him or change layout. You can easily add options for styles to tiles so user can manage that too himself.

Sorry if I misunderstood your question/problem.
4 posts Page 1 of 1