<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
		>
	<channel>
		<title>WordPress Ideas &#187; Topic: Shortcodes alternative</title>
		<link>https://wordpress.org/ideas/topic/shortcodes-alternative</link>
		<description>WordPress Ideas &#187; Topic: Shortcodes alternative</description>
		<language>en-US</language>
		<pubDate>Mon, 12 Jun 2017 01:13:17 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="https://wordpress.org/ideas/rss/topic/shortcodes-alternative" rel="self" type="application/rss+xml" />

		<item>
			<title>Bob Foster on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30983</link>
			<pubDate>Sat, 12 Nov 2016 18:02:16 +0000</pubDate>
			<dc:creator>Bob Foster</dc:creator>
			<guid isPermaLink="false">30983@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Cool idea but not for me. Very very sad...
</p>]]></description>
					</item>
		<item>
			<title>saftausbeute on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30674</link>
			<pubDate>Tue, 23 Aug 2016 18:38:20 +0000</pubDate>
			<dc:creator>saftausbeute</dc:creator>
			<guid isPermaLink="false">30674@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Great idea. Shortcodes being editable within the post editor would be extremely helpful and much more user-friendly than how it's being handled at the moment.<br />
Thank you!
</p>]]></description>
					</item>
		<item>
			<title>Baikare Sandip on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30400</link>
			<pubDate>Fri, 27 May 2016 13:22:22 +0000</pubDate>
			<dc:creator>Baikare Sandip</dc:creator>
			<guid isPermaLink="false">30400@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Yes, that is great idea for shortcodes, so it'll be more easily for end user.
</p>]]></description>
					</item>
		<item>
			<title>ika007 on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30399</link>
			<pubDate>Fri, 27 May 2016 12:41:04 +0000</pubDate>
			<dc:creator>ika007</dc:creator>
			<guid isPermaLink="false">30399@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>totally agree on this input
</p>]]></description>
					</item>
		<item>
			<title>ib4s on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30167</link>
			<pubDate>Sat, 07 May 2016 22:31:35 +0000</pubDate>
			<dc:creator>ib4s</dc:creator>
			<guid isPermaLink="false">30167@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Sir Trevor is an new approach to WYSIWYG that seems a bit like what you are thinking about:<br />
<a href="http://madebymany.github.io/sir-trevor-js/" rel="nofollow">http://madebymany.github.io/sir-trevor-js/</a></p>
<p>You add content blocks to a page.<br />
Each content block type has specific ways to configurate.</p>
<p>An Image has a src, align etc.<br />
A map would have a center, zoom index etc.<br />
A content listing would have ...</p>
<p>Maybe a virtual editor for shortcodes would be the next step - and maybe there are already plugins for that.
</p>]]></description>
					</item>
		<item>
			<title>rasenmaehertest on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30072</link>
			<pubDate>Tue, 19 Apr 2016 00:26:59 +0000</pubDate>
			<dc:creator>rasenmaehertest</dc:creator>
			<guid isPermaLink="false">30072@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Thats a great Idea!
</p>]]></description>
					</item>
		<item>
			<title>forinnov on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-30061</link>
			<pubDate>Sat, 16 Apr 2016 20:58:44 +0000</pubDate>
			<dc:creator>forinnov</dc:creator>
			<guid isPermaLink="false">30061@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Agreed, especially with points (1) and (4)
</p>]]></description>
					</item>
		<item>
			<title>Giorgos Sarigiannidis on "Shortcodes alternative"</title>
			<link>https://wordpress.org/ideas/topic/shortcodes-alternative#post-29948</link>
			<pubDate>Wed, 30 Mar 2016 15:47:59 +0000</pubDate>
			<dc:creator>Giorgos Sarigiannidis</dc:creator>
			<guid isPermaLink="false">29948@https://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>I believe that the shortcodes functionality is something like a necessary evil for both developers and users. After reading the "Shortcode Roadmap Draft one" and all the discussion that it followed, I was wondering if we could push aside shortcodes completely in favor of a different way of inserting custom content in posts. </p>
<p>What I suggest considering is creating a new type of content (named "Content objects", "Content blocks" or whatever). On the image below I made a quick and rough mock-up (not a design proposal, of course - not even a complete wireframe which would cover all possible scenarios) to demonstrate the main idea:<br />
<a href="https://dl.dropboxusercontent.com/u/38634/Various/fireframe.png" rel="nofollow">https://dl.dropboxusercontent.com/u/38634/Various/fireframe.png</a></p>
<p>Such an approach could have the following benefits:<br />
1. End-user wouldn't have to memorize shortcodes and their parameters.<br />
2. Content objects would be editable in the editor like any other object such as images or galleries, by clicking the pencil icon.<br />
3. Developers could set what should appear if their plugin is uninstalled (keep the shortcode's content even if it's unformatted, declare some decent plugin-agnostic fallback or remove it completely).<br />
4. Depending on the object, the user could see the actual content in the editor, the same way that they can see an embeded object or a gallery (even if the formatting isn't the same as the frontend's end result).
</p>]]></description>
					</item>

	</channel>
</rss>
