4 Comments

  1. James Koster

    Templates are generally a sort of wrapper or design layout. Content is a separate thing that typically lives independently.

    You may be interested in this PR which explores ways we might improve content editing interactions in the template editor.

    Report

  2. Anne McCarthy

    Whew! You made yet another beautiful design for this latest call for testing. Thanks as always for digging in so deeply and highlighting the Outreach Program’s efforts.

    From a user viewpoint, I feel like my custom-created templates belong to me rather than the theme. I can see a user switching themes after a couple of years and building a dozen or so templates having a poor experience in this situation.

    This is an excellent point and I opened an issue here to document the feedback:

    https://github.com/WordPress/gutenberg/issues/31954

    I welcome anyone to chime in further on the solutions they’d like to see as I can definitely see that leading to a frustrating experience.

    One of the more frustrating aspects of the template editor is the lack of space at the bottom of the frame.

    I nearly opened an issue for this but stopped upon realizing that this is likely intentional to preserve the WYSIWYG experience, particularly when editing a template vs writing content. I’m not sure what a good solution is here but I’ll note this in the summary post for now as a point of frustration. My mind goes straight to this might be necessary frustration in order to preserve the one to one view.

    When adding a horizontal Buttons block, there is no space between individual buttons.

    Reported in the theme experiments repo: https://github.com/WordPress/theme-experiments/issues/262 Count me in as a big plus 1 to have more control over the buttons block :D

    Because neither the Columns nor the inner Column blocks currently have padding controls, the only way for users to “fix” this is to add a background color.

    Nice snag. I opened an issue in the theme experiments repo once more but might need to open other issues in the Gutenberg repo depending: https://github.com/WordPress/theme-experiments/issues/263 Work is underway to add more spacing controls to blocks so I imagine this scenario is covered in the long run but will be double checking to make sure.

    However, I would have preferred a flow where the content portion of the template was a part of the post and output via the Post Content block.

    I mentioned this in the comments of the post but, originally when mapping this out, that was the plan! However, I ended up running into a wild error with the post content block: https://github.com/WordPress/gutenberg/issues/31798 I just replicated it on a brand new test site as well. Generally speaking, I try to be mindful of not sending people in the direction of obvious errors that are well documented with these calls for testing (massive waste of everyone’s time). Needless to say, the ultimate call for testing wasn’t the original approach I wanted to take.

    That sort of moving back and forth between post and template editors may have opened up some more usability hangups that would be worth exploring.

    As James mentions above, there’s work underway to add in some friction/structure to the experience to make it more intuitive to use. It’s unclear if the “click to edit” experience will make it into 5.8 though.

    Report

    • Justin Tadlock

      Thanks for the followup, Anne, and making tickets. I’m starting to get better at opening them, but I need to work on doing more.

      I’m checking out the template/content-related ticket. In my own experiments since this post, I’ve been thinking a lot about how independent these things should be. I’ve done some hybrid-type of templates where some of the structure made sense as part of the template and some as part of the content and vice versa. In short, it’s going to be interesting to see what users do with it.

      Coupling this with the idea that templates are tied to the theme, I wouldn’t want anyone to “lose” anything they considered content on theme switch.

      I nearly opened an issue for this but stopped upon realizing that this is likely intentional to preserve the WYSIWYG experience, particularly when editing a template vs writing content. I’m not sure what a good solution is here but I’ll note this in the summary post for now as a point of frustration. My mind goes straight to this might be necessary frustration in order to preserve the one to one view.

      “A necessary frustration” — I am kind of thinking the same thing. Putting my dev/design hat on, I’m not sure if there is a good solution. Putting my user hat on, I might just work from the bottom of the page up. :)

      Report

  3. Karla

    Thank you for this exercise. I will try it out.

    Independently, before finding this post, I was playing with the TT1 block theme and the latest Gutenberg plugin. A Site Templates section appeared in the dashboard sidebar and I manually added some templates there. I also modified the header and footer templates via full site editing and the code for the modified templates appeared in that section, while the originals remained in the theme directory.

    Will all those database stored templates go away if I change the theme to another block based theme? Or will they remain like custom field groups do when using ACF? It would be great if they could persist, since losing structure aka widgets is always an occasion for teeth gnashing and regret when changing themes.

    Also, since the templates are not in code and can’t be managed via git, will there be a way to export them so that they can be carted from a development site to a live site without a lot of copying and pasting?

    I did like using the templates and the template idea of page building. It is very different from existing WordPress interactions however. It is as if WordPress is becoming a new product.

    Report

Comments are closed.

%d bloggers like this: