Riad Benguella

Thanks for reporting this issue. GitHub is probably a better place.
This issue is fixed in 1.1.0

see https://github.com/youknowriad/gcf/issues/3

Hey, thanks for trying to create custom blocks 👍

> But most of the guides are for EXNext, and I can’t make that work

While the gutenberg code is written in ES5, we try to provide documentation in both ESNext and ES5.
In the tutorial here, you can switch between ES5 and ESnext in all the code examples.

We also have an examples repository with examples in both https://github.com/WordPress/gutenberg-examples

> As mentioned above, I need to create a custom block that can create <li> IN the text, like the “Classic text” editor

Unfortunately, the “classic text” is not meant to be reusable. We encourage the use of the Editable component for any block needed html content like the “content” part of your block.
That said, if you want <li>, your options are:

– Use multiple Editable components, one for each <li> (maybe with a button to add rows)
– Use your own custom editor (you can look for any React Wysiwyg component, it should just work)

Should we make the “Classic text” editor reusable? I feel like we’re trying to avoid this, but we may reconsider if we see a lot of requests for it.

Does this answer your questions?

• This reply was modified 8 years, 9 months ago by Riad Benguella.

Hi there!

right now it’s not possible to add ng-href or any custom attribute to blocks, we’re exploring an extensibility API to allow third party developpers to modify exisiting compoenents. For example by adding ng-href to all links…

But in the meantime, can I suggest an alternative for your for you angular theme, wrap your post in a directive and catch all a clicks inside this directive, prevent default and navigate using Angular APIs instead?

Whilst you’re here, is ESNext with babel etc the recommended way forward? If so perhaps this (and some instructions on setting up) could be included in the docs also.

I don’t think ESNext is the recommended way forward. It is the recommended way for Core development but we do not want to enforce this on theme/plugin authors.

That said, I agree we should add a page in the docs with setup instructions for those who want to use ESNext. The Examples repo serves this purpose too because it has all the setup already in place, but lacks some explanations for now. Raising Docs PRs would be awesome 👍

• This reply was modified 8 years, 10 months ago by Riad Benguella.

Hi, The built-in blocks are built using ESNext code, but there’s the Gutenberg Examples repo showing several blocks in ES5 and ESNext.