Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    RehanK
    @revdfdev
    one question here
    can I add custom iframe / view into page builder
    if yes is there anything documentend about it
    ?
    Alexander Zaslonov
    @azaslonov
    Hi Rehan
    basically iframe could be a part of custom widget or represent a widget. There is an example widget "click-counter" in demo repository, it has react version as well.
    Kathy Church
    @kathychurch
    Is it possible to control access to parts of the generated sites to only authenticated users? I am thinking to have a login/signup button and once a user is authenticated, additional menu items become visible. Thanks!
    Alexander Zaslonov
    @azaslonov
    Hi Kathy, yes, there is a concept for that, you can even try it out on demo.paperbits.io.
    The only thing here, on demo site it is purely client side implementation, which means it only hides it with JS, so depending on your requirements, you may need to filter content on the fly on the backend
    Eric Lacroix
    @EricLacroix
    Interesting framework concept, is there some already pre-build widget to integrate with some Headless CMS platform?
    Alexander Zaslonov
    @azaslonov
    There is an integration with Google Firebase
    Are you looking for specific headless CMS?
    Eric Lacroix
    @EricLacroix
    Not a specific one I was just looking to understand how to wired up an external CMS.
    Alexander Zaslonov
    @azaslonov
    I see. I guess Firebase should do then for starter. Basically there are just two interfaces that need to be implementated: IObjectStorage and IBlobStorage.
    jimmydevine
    @jimmydevine
    I have a local instance of the demo going, is there any documentation on creating new blocks?
    jimmydevine
    @jimmydevine
    I see there is a block-snippets.json file that defines them but I don't see any documentation about the format of this file
    Alexander Zaslonov
    @azaslonov
    Hi Jimmy, right there is no documentation. What I would recommend is to create required blocks in the designer, add them to the library and just copy the result "blocks" node of the JSON to the block-snippets.json
    I added a task for myself to create the respective docs
    jimmydevine
    @jimmydevine
    ok thanks Alexander
    Alexander Zaslonov
    @azaslonov
    sure thing
    jimmydevine
    @jimmydevine
    hmm does save still work with the latest code base? I just recloned and reinstalled demo and if I make a change and save it, the saved content doesn't reflect my change
    Alexander Zaslonov
    @azaslonov
    There is an issue saving demo content that was reported recently. So, if you use just static data, then yes, it won't work. We'll fix that soon.
    jimmydevine
    @jimmydevine
    seems like there were changes in core/src/ko/bindingHandlers/bindingHandlers.widget.ts that broke height stretching
    Alexander Zaslonov
    @azaslonov
    of a widget?
    jimmydevine
    @jimmydevine
    yeah with the demo if you go to a page which doesn't span the full height, navigation and copyright are tied to the bottom, but if I pull in the latest core they're no longer tied to the bottom
    seems to be related to "block": binding.flow !== "inline" && binding.flow !== "none", "inline-block": binding.flow === "inline"
    jimmydevine
    @jimmydevine
    I set flow to none in both contentViewModelBinder.ts and sectionViewModelBinder.ts and that seems to have fixed it, I don't know if that is inline with intention
    Alexander Zaslonov
    @azaslonov
    got it, thanks Jimmy
    Alexander Zaslonov
    @azaslonov
    Fixed. Will publish a bit later today.
    jimmydevine
    @jimmydevine
    good deal, thanks
    jimmydevine
    @jimmydevine
    what do you think about adding some sort of theme and color standardization layer so that layouts can be created with colors against standard element types and then the color scheme set later via themes?
    Alexander Zaslonov
    @azaslonov
    you mean to be able to switch colors (and other elements) through some pre-sets?
    like selecting in drop down?
    if yes, this is planned feature, we've heard this request many times
    jimmydevine
    @jimmydevine
    ok cool, yeah basically.. feature requests are tracked through github?
    Alexander Zaslonov
    @azaslonov
    public ones yes, let me check if we have it there
    looks like we don't, let me add one
    jimmydevine
    @jimmydevine
    awesome thanks
    Pulkit Garg
    @wittycodes
    Hi
    can we use nextjs with paperbits
    Alexander Zaslonov
    @azaslonov
    Hi, technically you can, we just don't have any examples or documentation around it. So, you can either explore React integrations yourself, or check back later this year.
    Pulkit Garg
    @wittycodes
    thanks @azaslonov
    actually, I am having a sample nextjs app of eCommerce, I wanted the sellers to be able to add thier related promotion content to product pages with dnd via paperbits. It just feels very handy.
    so, I constructed a lerna monorepo with all paperbits repositories - core, common, styles, firebase. gone through interfaces and knockoutjs.
    Pulkit Garg
    @wittycodes
    what i feel is that the wrapper around a "react component" is quite big in codebase, if converted to a paperbits widget say a simple custom input button.
    Pulkit Garg
    @wittycodes
    are we planning to make the widget creation further concise/ automated and, other part, mainly for nextjs integration with paperbits, it is mostly the ability to use nextjs routing, directory based pages and SSR. Working on it, hope to clear my doubts here if stuck
    Alexander Zaslonov
    @azaslonov

    In fact, yes, we are working on unification/simplification for the contract for plugging-in components in different frameworks (with some customers using React and Vue), eventually it should be literally a matter of filling a few fields to register one.

    I think that what you call "big wrapper" is not accurately describes it, because there are only 3 UI components: editor, widget in design-time), widget in run-time. All the rest is around data flow (from data store to render).
    I guess, you need to take a look at this the click-counter example (in experimental branch: https://github.com/paperbits/paperbits-demo/tree/az/react/src/components/click-counter/react), implemented purely in React (design-/publish-/run-time), that should look a bit simpler from that prospective.

    In any case, we're open for collaboration in this area, so please feel free to come with feedback/suggestions.