Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd Block: Meta #13335
Comments
melchoyce
added
New Block
Needs Design Feedback
labels
Jan 15, 2019
This comment has been minimized.
This comment has been minimized.
Should this actually be TWO blocks then?
|
This comment has been minimized.
This comment has been minimized.
StaggerLeee
commented
Jan 17, 2019
It is indeed stupid widget (block). Regardless of it I think any serious CMS should have Login, Register, Forgot password widget (block). |
This comment has been minimized.
This comment has been minimized.
Unless there's some sort of backwards compatibility concern, I'm not sure it makes sense to include this. If anything, I think many of these options could just be added as options in a navigation block. For instance, letting people insert "Login/Logout" or "RSS Feed", etc. into their menus. |
melchoyce
added this to Backlog
in Porting widgets to blocks
Feb 4, 2019
This comment has been minimized.
This comment has been minimized.
@mapk @youknowriad What do you think about @kjellr's suggestion above? |
This comment has been minimized.
This comment has been minimized.
@kjellr's suggestion makes sense. Let's move forward without the Meta block. I'll close the issue based on this decision. |
melchoyce commentedJan 15, 2019
As part of the effort to convert all widgets into blocks for Gutenberg phase 2, I took a look at the Meta widget.
The Meta widget has been around, as far as I can tell, since WordPress 2.2 or WordPress 2.3, released in 2007. It has barely changed in the last twelve years. Creating a comparable block seems trivial:
Should we, though?
From speaking with folks and seeing support tickets, the biggest use-case for the meta widget is providing people a quick and easy way to log in to their sites. We removed it from WordPress.com in 2016, and figuring out how to log in seemed to be the only reason people contacted us about it. If anything, maybe we could consider creating a "log in" block, or include a log in link in the footer by default: