webcrate VS Sass

Tool you linked is open source apparently (https://github.com/WebCrateApp/webcrate) so you should be able to self-host it on your own. They have no specific docs for it though...

Hey fellow internet users! I always got frustrated with existing bookmarking tools as they were either too clunky to use or had way too many features I didn't need. Until I decided to just build my own!

WebCrate allows you to organize links, articles and more from around the web into collections called crates. You can share the crates with anyone and since each user gets their own instance of WebCrate in their own 'personal cloud' thanks to Deta Space, you can subscribe to other users crates and view their links right from your dashboard.

Learn more at http://webcrate.app or install it directly on Deta Space (https://deta.space/discovery/webcrate)! Let me know what you think (WebCrate is OSS, so you can also contribute) and I hope you find it useful!

👨‍💻 WebCrate is also open source, report any issues you find, suggest features, or contribute directly with code on GitHub!

WebCrate helps you organize and share links, articles and more from around the web in a central place. It's open source & can be easily self-hosted thanks to your own personal cloud in Deta Space.

WebCrate is completely separate from the browser. You can learn more on the homepage: webcrate.app.

https://webcrate.app - OSS bookmarking tool to help you organize your web

- Vue / Nuxt / Plain CSS

- TypeScript / Node / Express

- Hosted in your own personal cloud thanks to Deta Space (https://deta.space/discovery/webcrate)

Nuxt made the frontend super simple and fast to build, it takes care of a lot of things for you! Deta is also awesome for devs

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.