Cockpit VS stylelint

Hmm...I just tried https://getcockpit.com/, which looks like a super lightweight CMS and PHP doesn't seem to work.

I am struggling with my instance of cockpit Cockpit (getcockpit.com) that all contact forms on my website keeps going to spam. The SPF record is correct.

https://getcockpit.com/ Recommend using V1, since V2 is a bit new and lags documentation and plugins.

Might be a long shot, and I haven't checked in on the project in years, but maybe cockpit https://getcockpit.com/ ?

Cockpit

Cockpit CMS is a straightforward framework for managing complicated and organized information. Additionally, it makes it possible to control the content adaptably and with few limits. This Open Source Headless CMS also supports a variety of devices on a single platform. It is very simple to install, and it takes little time to finish. As a result, you can begin your job without any problem or difficulty.

I've been using Cockpit (https://getcockpit.com/) for a few internal and personal projects now.

It's lightweight and easy to use. Just upload the folder to your webspace (minimal PHP requirements!) and you are good to go.

Create some collections for you data, link them if needed, and you can immediately use them via the API endpoints AND also via a GUI for CRUD operations.

This is really great because my colleagues are non-technical and I don't need to write some frontend for them to update data and so on and can concentrate on the "real task".

Documentation on the other hand is awful, to the point where you better refer to the "inofficial documentation" (for the interested: https://zeraton.gitlab.io/cockpit-docs/) with no way to improve the official one.

So, while I LOVE the ease of use, I wondered if somebody has a recommendation for a similar solution which might be somewhat more "mature" in regards to the documentation.

Link

Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:

Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase.

The “cost of loading modules” diagram shows non-linear behaviour (though you should largely ignore the curve visible in the diagram because the x axis is way off linear):

• 0.15s ÷ 500 = 0.3ms

• 0.31s ÷ 1000 = 0.31ms

• 3.12s ÷ 10000 = 0.312ms

• 16.81s ÷ 25000 = 0.6724ms

• 48.44s ÷ 50000 = 0.9688ms

My own observation on a Surface Book six years ago was that in Node.js under Windows, each module had about 1ms of overhead when there was warm file system cache—that is, simply bundling with Rollup saved 1ms per file. If this sort of thing interests you, quite a lot of useful stuff came out of https://github.com/stylelint/stylelint/issues/2454 which I filed because I was unhappy with stylelint taking over a second to import. And that must have been only in the order of one or two thousand modules, when the behaviour is still close enough to linear.

As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards.

Document your build process in a blog, use eslint, stylelint and jsx-a11y lint. Run a lighthouse performance test, follow the optimisation reccomendations.

Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities

Stylelint

I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint

The complete code for this project is in the Rodney Lab GitHub repo. I do hope the post has either helped you with an existing project or provided some inspiration for a new one. As an extension, you can add all your favourite future CSS rules to the PostCSS config. Beyond PostCSS for linting your input CSS, consider trying stylelint.