SUIT CSS Reviews

Gitea Reviews

SUIT CSS mentions (4)

• Past Informs the Present: Begin’s Approach to CSS

  As style sheets became the responsibility of larger and larger teams, CSS’ global scope and specificity were often at odds with team dynamics. Style collisions became increasingly common, where changes introduced by one developer would inadvertently affect styles elsewhere on the website. As the old joke goes: two CSS properties walk into a bar; a bar stool in a completely different bar falls over. As these issues... - Source: dev.to / over 1 year ago

• Front-end Guide

  CSS (Cascading Style Sheets) are rules to describe how your HTML elements look. Writing good CSS is hard. It usually takes many years of experience and frustration of shooting yourself in the foot before one is able to write maintainable and scalable CSS. CSS, having a global namespace, is fundamentally designed for web documents, and not really for web apps that favor a components architecture. Hence, experienced... - Source: dev.to / over 1 year ago

• Bootstrap VS Tachyons

  Tachyons developer, Adam Morse in this talk at DevShop London 2016, talks about motivation behind Tachyons. He discusses the problem of continuous over-riding your own written CSS code, writing tons of CSS code, struggle to keep all this info in your head and the need to refactor 200Kb CSS file. His answer to the problem is Tachyons. SUIT CSS (Style Tools for UI Components). Was the initial inspiration that lead... - Source: dev.to / about 3 years ago

• How I'm forcing myself to write CSS following certain rules

  This component syntax is mainly taken from Suit CSS with minor modifications. - Source: dev.to / about 3 years ago

Gitea mentions (60)

• Beware Offers of “Help” with Your Projects

  This reminds me of Gogs [0], where the original author refused a lot of good ideas and improvements, eventually leading to a fork [1] that's now a lot more popular and active than the original. [0] https://gogs.io/ [1] https://gitea.io/en-us/. - Source: Hacker News / about 1 year ago

• Incident with Issues and Pull Requests

  Yes, we do this using https://gitea.io/en-us/ on a private server. Firewall, backups and a replica running for most projects. Github is only used when it's required by a stakeholder. - Source: Hacker News / about 1 year ago

• Let's Make Sure GitHub Doesn't Become the Only Option

  There's a number of places out there, some of which also support alternatives to Git itself. By no means a complete list and in no particular order: GitLab - https://about.gitlab.com/ Sourcehut - https://sourcehut.org/ Codeberg - https://codeberg.org/ Launchpad - https://launchpad.net/ Debian Salsa - https://salsa.debian.org/public Pagure - https://pagure.io/pagure For self hsoted options, there's these below... - Source: Hacker News / about 1 year ago

• If you're on DSM 6 and still waiting for an update on the GitLab package, don't bother

  And if you need GitLab (for runner, etc...) then it's not too bad to run in Docker. But if anyone is looking for a somewhat simpler git solution, gitea is pretty great. Source: about 1 year ago

• OpenBSD Upgrade 7.2 to 7.3

  Check: Configuration and syntax changes and Special packages. The latter includes changes on PostgreSQL, Python and Gitea. - Source: dev.to / about 1 year ago