如何向非技术客户端提供在 CMS 的 WYSIWYG 内容生成器/编辑器中向内容添加 css 类/ID 的选项？
- 如何提供添加 css 的选项 CMS 中内容的类/ID 内容所见即所得构建器/编辑器 不知道的技术客户 html、css，但了解 MS Word。
有些时候根据 XHTML 标签设计内容是不够的。需要使用CSS类。
- 我们应该只给 css .classes 也可以给出 user 或 #Id 吗？
- 以及我们应该如何写类名 为了方便客户？
以语义方式还是像 border4px、浅色文本和漂亮背景？哪种方法有利于非技术客户选择并记住合适的课程？
- CMS 提供此选项的受欢迎程度 客户 ？什么是最好的方法 根据可用性？
- How to give option to add css
classes/IDs to content to in CMS's
content WYSIWYG builder/editor to non-
technical client who doesn't know
html, css but knows MS Word.
some time to make content according to design XHTML tags not enough. use of css classes needed.
- Should we give only css .classes to
user or #Id can be given also? - and how we should write classes name
for ease of client?
In semantic way or like border4px, light-text and pretty-background ? Which method will be good for non-technical client to choose and remember appropriate classes?
- How popular CMS given this option to
client ? What is best method
according usability?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
大多数 Rich HTML 在线编辑器都会提供“样式”下拉菜单，允许用户选择样式。请参阅此处了解 FCKEditor 中的解决方法。
至于要放什么样式，这完全取决于您的客户（我认为）。如果他们有设计指南，您将需要在其中放置与公司字体/颜色/设计相匹配的样式。您还可以由用户进行自定义，周围有几个在线 CSS 编辑器 - 但它们并不真正适合非技术人员。
至于用ID还是类：绝对是类。在所见即所得编辑器中很难阻止 ID 被多次分配，这是绝对不允许的。
类的命名确实取决于你。我喜欢人类可读的格式，同时也是类名：
HeadingSmall
ProductCategory
ProductDeclaration
Quote< /p>
这些类名在选择类时显然会显示给用户，因此不需要保留单独的、人类可读的类名。
Most Rich HTML online editors bring a "styles" drop down that allows the user to pick styles. See e.g. here for how it's solved in FCKEditor.
As for what styles to put in there, that depends totally on your client IMO. If they have design guidelines, you will want to put styles there that match the corporate font / colouring / design. You could also make this customizable by the user, there are several online CSS Editors around - they're not really for non-technical people, though.
As for whether to use IDs or classes: Absolutely and definitely classes. It's hard to prevent IDs from being assigned multiple times in a WYSIWYG editor, which is a total no-no.
The naming of classes is up to you, really. I like human-readable formats that at the same time are a class name:
HeadingSmall
ProductCategory
ProductDeclaration
Quote
those class names are obviously displayed to the user when selecting the class, so there is no need to keep separate, human-readable class names.