Editor.js VS Sass

I am supporting a project where lawyers, advisors can publish articles or news, to get more attention and clients. Initially it was made through TinyMCE, but they wanted not just HTML, but also a way of showing many pictures with interactions. I was seeking UI editor like Medium, and I guess best what I found was EditorJS and during checking its Awesome List there were several carousel plugins and I stopped on this.

We call it EmailBuilder.js – a powerful block-based email builder that takes the best parts of other open source libraries like Editor.js and email component libraries and puts them into an easy to use no-code builder.

I tried the "Doc", "Sheet" and "Slide" feature and each of them are incomplete and lacks most of the popular features. It would be better if the author uses existing solutions instead of implement them from ground up.

editor.js [0] for documents and Grist [1] for spreadsheet are some good examples.

[0]: https://editorjs.io/

Editorjs [https://editorjs.io/]

Use Gutenberg or a block editor like this (https://github.com/codex-team/editor.js) for a CMS. The WYSIWYG days are over.

Has anyone had any luck adding editor.js to your app? I've got a plain rails/stimulus/turbo/activeStorage app which needs a dynamic page builder and editor.js looks like it has promise. However it's a pretty specialized workflow and Im not sure if it jives well with the plain Rails ecosystem.

try this: https://editorjs.io/ might come handy, it's a very nice library and it's well maintained.

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.