flynt
acf-builder
flynt | acf-builder | |
---|---|---|
3 | 5 | |
684 | 778 | |
2.0% | 0.3% | |
9.6 | 0.0 | |
9 days ago | 6 months ago | |
PHP | PHP | |
MIT License | GNU General Public License v3.0 only |
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.
flynt
-
Coming to Terms with Tailwind
The underlying problem I see that Tailwind solves is component-izing a single idea. It does that pretty well. You can point to a single stack of code and say "this one thing is a navbar" and it's easy to know where to make changes. No searching, no stress.
What I haven't seen Tailwind do well on my projects is respond to change in the same way other methods would. I'm not saying it isn't possible, just that the several projects I've seen, it was a big pain.
A method I've been quite fond of to accomplish the same task, but remove the difficulties this author's other posts articulate, is to recreate the concept of a component in a single folder. Much like you would a Vue single-file component. If you read the "Components" heading here you'll get a good feel for it by looking at the folder/file structure:
* https://github.com/flyntwp/flynt#components
That same idea I've enabled in a framework/language-agnostic way with an NPM module I created (not public). It watches the folder, namespaces everything like a single-file Vue component (using a manifest name or defaults to the folder name), and with a bit of config you can even do intelligent vendor/tree-shaking across all components and themes. You can even have components inherit theme sass/js files.
This solution is nice because devs get the "one source of editing" in a single folder, it's performant, and it's agnostic to language/frameworks. Point to a folder of components, specify a dist folder, and you're done unless you want to modify config. Parallel execution of all components being built, it's also fast!
I'm only saying all of this because I'm curious if there are Tailwind users out there that could teach me if Tailwind solves other problems I'm not seeing. Oor if this type of solution would be something I should open source. It ends up being a pretty simple Webpack file under the hood.
-
How does script.js work on Flynt WP components?
I've just started using Flynt WP for Wordpress custom themes and I really love it. However, I don't have much experience with how building js files (such as this for example https://github.com/flyntwp/flynt/blob/master/Components/NavigationBurger/script.js) work so I was wondering if anybody would be so kind to give me some quick advice on them.
-
How to add jQuery to the Flynt WP Starter Theme
I was wondering if it was possible to add pure jQuery to the Flynt WP Starter Theme, which is component-based. I'm not very comfortable using JS as they are writing it, but I just might have to learn it. I was wondering if there were other options. Here you can find their overall theme repository https://github.com/flyntwp/flynt and here an example of script.js https://github.com/flyntwp/flynt/blob/master/Components/NavigationBurger/script.js
acf-builder
-
Tell me about your favorite tools, plugins, etc that are NOT in the Wordpress.org directory
This one is great. For Advance Custom Field users. https://github.com/StoutLogic/acf-builder
- ACF: What's more performant for field definitions; Json or PHP?
-
About Wordpress...
I've used Stoutlogics builder for a while now and it makes the whole process a breeze - https://github.com/StoutLogic/acf-builder
- Should my ACF presentation logic go into the theme or a custom plugin?
-
Custom WordPress Theme Development
https://roots.io/sage/ https://github.com/StoutLogic/acf-builder https://github.com/MWDelaney/sage-acf-wp-blocks https://www.gatsbyjs.com/
What are some alternatives?
bricks - A modular WordPress starter theme powered by Bootstrap 5 and Gulp
sage-acf-wp-blocks - Composer library for generating ACF Gutenberg blocks from templates. Intended for use with Roots/Sage (http://roots.io)
bricks - Open-source natural language enrichments at your fingertips.
bedrock - WordPress boilerplate with Composer, easier configuration, and an improved folder structure
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
sage - WordPress starter theme with Laravel Blade components and templates, Tailwind CSS, and a modern development workflow
starter-theme - The "_s" for Timber: a dead-simple theme that you can build anything from
acf-composer - Compose ACF Fields, Blocks, Widgets, and Option Pages with ACF Builder on Sage 10.
theme - Tonik is a WordPress Starter Theme which aims to modernize, organize and enhance some aspects of WordPress theme development.
wordplate - WordPlate is a boilerplate for WordPress, built with Composer and designed with sensible defaults.
minimum-viable-wordpress - A single-file WordPress theme.
acf-country - ACF Country field - Display a select field of all countries, in any language.