surface
ProcessWire
surface | ProcessWire | |
---|---|---|
11 | 11 | |
1,994 | 892 | |
0.6% | 1.0% | |
7.9 | 8.3 | |
5 days ago | 16 days ago | |
Elixir | PHP | |
MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
surface
-
htmlgui.nvim - Create html + css + lua apps with neovim as 'browser'. ( proof of concept )
I should have been more clear that my intent was to create/use a compiler for some kind of component syntax. There are lots of them, from Surface (Elixir), Blade (PHP/Laravel), and JSX (React, Vue, Etc)
- Would you still choose Elixir/Phoenix/LiveView if scaling and performance weren’t an issue to solve for?
-
Why I selected Elixir and Phoenix as my main stack
There I learned more deeply about LiveView and Surface UI.
-
Something similar to Vuetify for Phoenix LiveView?
I think Surface is the ideal candidate for this. But it doesn’t have the components you are looking for but you can build anything with it. Hopefully, in future we can have set of headless components built using Surface 🤞
-
Single source of truth with Phoenix LiveView
I have worked with Phoenix LiveView and Surface-UI for about a year; I would like to share some of the things I learned the hard way.
-
Course/Extensive tutorials for Phoenix 1.6?
This is just an idea, but what about implementing using Phoenix.View(via use MyAppWeb, :view in your module)? Then assign I think has access to @conn. Then maybe work some magic to still allow Phoenix.Component syntax - but at this point, this is something I believe is a flow that might be in development. Try investigating / asking in Surface, because that is a lot more similar to React in its approach. In fact, I think Surface is where more aggressive features are pushed out, and ironed-out features get included into Phoenix. This was the case for Phoenix.Component, and HEEX.
-
Porting files generated by phoenix to surface
This post is intended to get you started with surface provided components. I provided the original code and surface versions so you can compare the differences yourself without installing anything. After installing surface following the installation guide https://surface-ui.org/getting_started add surface_bulma in your mix.exs, this will allow you to use the table component.
-
We Got to LiveView
I totally get the "Am I doing this the right way?" feeling, especially coming from Rails where everything was so opinionated and wanting to stay idiomatic.
Phoenix, while it does have opinions, is far less opinionated in the sense that it doesn't do it darndest to force you into certain conventions (for example, if your module name doesn't match your file name, Phoenix won't complain). Its generators do try and push you toward using good DDD practices (which is my opinion is a GREAT thing), but of course the generators are completely optional.
I don't have experience writing large LiveView apps but I would say that if you are familiar with any component-based frameworks (like React), I would take a look at SurfaceUI[1]. It simplifies a few "gotchas" in LiveView (though I would say they are very minor gotchas and worth learning about at some point) and gives you a component-rendering syntax more like React. Once you get going, you'll learn that LiveView doesn't have all the headaches that come with bigger React apps (like having to memoize functions or comparing props to avoid a re-render and whatnot). The recent release candidate for Phoenix 1.6 has made strides for a cleaner component syntax, but if you're having trouble with LiveView, Surface might bring some familiarity.
[1] https://github.com/surface-ui/surface
-
Phoenix 1.6.0-RC.0 Released
Have you seen Surface UI? Pretty cool. Collection of LiveView components. https://surface-ui.org/
- Surface UI – A server-side rendering component library for Phoenix
ProcessWire
-
Need help choosing a logo! (& advice) CONTEXT IN COMMENTS
Bottom one looks better. First one reminds me of ProcessWire.
-
Beginner needs help: Looking for an easy-to-use/learn headless CMS + Frontend + CSS website solution? Overwhelmed.
ProcessWireProcessWire is a fantastic CMS/CMF (content management framework) and I think it is a good fit for your skills. Works with any front end CSS although my personal preference is UIkitUIkit.
-
Why I selected Elixir and Phoenix as my main stack
Over the years I have tried different frameworks, mostly in PHP, like Code Igniter (2010), ProcessWire (2014) and Laravel (2015).
-
WordPress Sites Under Attack from Newly Found Linux Trojan
The idea of tons of 3rd-party plugins, with WordPress and also Drupal, is just disastrous for security.
Anyone with any ability to write a little PHP would be far far better off building their site in a CMS like ProcessWire [1], which has a very small core, but a extremely powerful content (PHP) API [2], which means you can replicate pretty much everything you have in Wordpress and Drupal with a few API calls in your templates.
This means you build your listing and presentation-logic custom made with the minimal amount of code needed, and the attack vector shrinks to pretty much nothing, as long as you don't voluntarily do something stupid.
[1] https://processwire.com/
[2] https://cheatsheet.processwire.com/
-
What CMS to use in 2022
It is incredibly rare that I see anyone mention ProcessWire. I used to use it years ago and still subscribe to regular emails. It is indeed a great CMS/CMF. https://processwire.com/
-
Code Website vs Buy Website Builder
ProcessWire is one option.
- Best CMS for frontend dev
-
Would my site run faster if I abandoned Wordpress and 'rewrote it from scratch'?
Regardless of that, I'd like to throw in ProcessWire as an option. You basically define all your fields and templates you want to have in the admin, and then you create your templates. You can also use Page Classes to extend functions for a specific template. Your application sits in the "sites" folder and is separated from core. I'm running two websites with that one.
-
Cms for costum html & css
If you're a PHP user, check out ProcessWire.
-
What is the best headless CMS which supports content blocks?
I'm looking for a headless CMS solution that offers a good content editing strategy. I'm used to working with Statamic and Processwire, both of which allow you to create your own "Content blocks", which can be re-used by the editor / user and are set up in ways which allow you to define them.
What are some alternatives?
react_phoenix - Make rendering React.js components in Phoenix easy
Grav - Modern, Crazy Fast, Ridiculously Easy and Amazingly Powerful Flat-File CMS powered by PHP, Markdown, Twig, and Symfony
torch - A rapid admin generator for Elixir & Phoenix
Bolt - Bolt is a simple CMS written in PHP. It is based on Silex and Symfony components, uses Twig and either SQLite, MySQL or PostgreSQL.
phx_component_helpers - Extensible Phoenix liveview components, without boilerplate
TYPO3 - The TYPO3 Core - Enterprise Content Management System. Synchronized mirror of https://review.typo3.org/q/project:Packages/TYPO3.CMS
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
MODX - MODX Revolution - Content Management Framework
Raxx - Interface for HTTP webservers, frameworks and clients
Kirby - Kirby's core application folder
plug - Compose web applications with functions
SilverStripe - The installer for Silverstripe CMS and Framework. Check out this repository to start working with Silverstripe!