News for hackers. Stuff that matters.

ivome

> How do you use native css features with Stylemapper if it's just for utility classes?

The applied classes don't have to be utility classes. You can use it with any other CSS solution like CSS modules, global stylesheets, passing inline styles via the styles prop, etc.

> Except for a utility css framework...

This is not a requirement. This works the same with other custom styling solutions, like CSS modules, SASS, SCSS, etc.

Show HN: Stylemapper – A better way to style React components

https://slicknode.com/blog/stylemapper-style-react-components/

I have never been 100% happy with the way React applications were styled, and I tried lots of options. Recently I started using TailwindCSS, which is great, but there were still a few things I didn't like: - It's ugly with CSS classnames all over your component code - There is lots of boilerplate for custom components, especially if you are using Typescript and variants So I wrote a little...

( Read More... | 4 comments | 6 points | on HN )
Hi Hackernews, I have been working on this for quite some time and I’m excited to share this with the open-source community: Slicknode, a GraphQL based backend builder and Headless CMS for web developers that automates the repetitive work, but can also be customized where needed.

I often found myself limited by CMS software. If you want to add anything custom like business logic or 3rd party APIs, you have to have enormous amounts of knowledge about the CMS architecture to make even a simple change. Adding business logic is oftentimes difficult or impossible. If you want to combine this with 3rd party APIs, you either have to do it in the frontend by hand or build a custom backend, with all the integration effort that comes with that.

You can build a custom backend, but that’s a lot of work and gets complex, especially if you need content management with modular page builders, localization, version history, publishing workflows etc.

With Slicknode, you get composable building blocks based around the GraphQL specification that you can mix and match and extend where needed to make them work with your own custom requirements. A lot of the functionality like CRUD logic, Admin UI and API generation can be derived from the data model, and for the rest you can add basically anything with simple JS functions (custom resolvers, mutations, web hooks, etc). I found this to be extremely fun, flexible and fast to build digital solutions. Now I’m sharing this with everyone and would love to hear your thoughts! Ivo

Re:On GraphQL-to-SQL on Friday May 22, 2020 @12:24PM (#23273771)
Have you looked at Slicknode? Slicknode allows you to declaratively define your application with schema etc. in your local code and then just sync with a CLI. It then does database migrations and updates/provisions a serverless API on AWS (with Lambda, Aurora Serverless).

That way you can leverage proper version control, merge feature branches, do copy paste of parts of models, reuse entire modules across projects, etc.

Slicknode: https://slicknode.com Github: https://github.com/slicknode/slicknode

(I'm from Slicknode)

Not sure if this is related, but when I enter my GraphQL endpoint and click "Create my App" I am redirected to a weirdly escaped URL with an invalid hostname.
Thanks for the report! The link that linked to the non existent page is now fixed...