-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reaction-layout #148
Comments
Yep, that's basically the same as I was thinking. 👍 I would add that this could probably be generalized to be a Meteor pkg that doesn't have any reaction dependencies and could be used in other projects. (Would be interested in using it myself.) What I'm thinking is that on the flip side of everything you already mentioned, the layout pkg could have an API providing the ability to add a component zone to any page, and to customize the appearance of that component zone, and to add custom filter functions. So one might do: <div class="row">
<div class="col-md-4">{{> pagePartZone "left"}}</div>
<div class="col-md-4">{{> pagePartZone "middle"}}</div>
<div class="col-md-4">{{> pagePartZone "right"}}</div>
</div> Which sets up each area to accept configurable page parts (components). The app can provide a The app can also configure its own display logic functions, and a few could be built into the Meteor pkg, like isLoggedIn. Some of the generic types could also be part of the package: static text, static HTML. |
I know there has been some work by others to create Meteor CMS, but I don't know the status of those projects. Azimuth, which seems to be maybe a bit neglected these days, has a concept of "blocks" which is similar to what we're talking about, but not as powerful or nifty. |
As I mentioned to @spencern I think this could now just reside in |
I just found Orion.js. It looks like nice CMS solution 😄 |
Does anybody heard about Universe CMS? It appears in latest blog post from Meteor and looks awesome! Also I found very nice post about React plugins and Flux pattern ( Building Plugins for React Apps ) and it seems that Reaction uses similar approach for its extensions. So maybe in near future we can use this kind of cutting edge stuff 😄 |
I've just found nice package react-grid-layout. It will be the best option for layout editor maybe with this npm module as well react-ui-builder |
@KEFIRCHIK that's really interesting, thanks! @mikemurray take a look.. |
@aaronjudd I've just found another interesting project - landing-page-builder 😄 |
Changes that refactor the `ReactionCore.registerPackage` implementation to a more flexible, and structured template registry. `ReactionCore.registerPackage` moves to server. package.registry is published to client. These are not backwards compatible changes. Updated documentation at docs/packages.md Initial commit for issue #314 Strategic updates for Issue #273 Strategic updates for Issue #306 Strategic updates for Issue #305 Strategic updates for Issue #246 Strategic updates for Issue #183 Strategic updates for Issue #155 Strategic updates for Issue #16 Strategic updates for Issue #148 Resolves #53 Resolves #308 Resolves #178 *Remaining tasks* solve undefined error convert the rest of the payment packages context sensitive widgets (context?) update with detailed docs (document all the existing "provides")
##package-registry-refactor Changes that refactor the `ReactionCore.registerPackage` implementation to a more flexible, and structured template registry. `ReactionCore.registerPackage` moves to server. package.registry is published to client. cycle = Core, Stable, Testing (todo: => correlates package semver) container = combine multiple registry entries These are not backwards compatible changes. Updated documentation at docs/packages.md Initial commit for issue #314 Strategic updates for Issue #273 Strategic updates for Issue #306 Strategic updates for Issue #305 Strategic updates for Issue #246 Strategic updates for Issue #183 Strategic updates for Issue #155 Strategic updates for Issue #16 Strategic updates for Issue #148 Strategic updates for Issue #146 Resolves #53 Resolves #308 Resolves #178
replace bunyan-pretty with bunyan-prettystream, fixes #363
Here's some rough thoughts on a possible new layout approach:
Create a new "component" collection:
Components types are UI helpers, that dynamically load templates, perhaps setting data
This could allow for extending, customizing template (component) by cloning, changing the values of the components
You can have multiple templates for components
You add to any grid page by:
For example:
Add a product
Add a hero -> inline hero manager
The "productGrid" doesn't exist anymore, instead it's a generic layout grid, that injects the dynamic component templates into the grid
You wouldn't create a "productGrid" template, but you would loop through the applicable collection data and render each individual product grid item template and insert into a layout. You should be able to mix and match different components this way.
Is still a drag and drop interface, storing position or other layout in the component collection level.
I'm thinking that potentially the rendered layout would be a client layout collection + template
The text was updated successfully, but these errors were encountered: