<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Support of AMP in future Liferay version</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=117980532" />
  <subtitle>Support of AMP in future Liferay version</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=117980532</id>
  <updated>2026-04-04T23:12:33Z</updated>
  <dc:date>2026-04-04T23:12:33Z</dc:date>
  <entry>
    <title>RE: Support of AMP in future Liferay version</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=119536200" />
    <author>
      <name>Eric DARIEL</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=119536200</id>
    <updated>2025-10-21T05:12:37Z</updated>
    <published>2020-07-04T08:56:44Z</published>
    <summary type="html">I reply to myself.It seems AMP is aligned with roadmap :&lt;br /&gt;https://issues.liferay.com/plugins/servlet/mobile#issu/LPS-10963&lt;br /&gt;&lt;br /&gt;How can we know if it is for this year and 7.3 or for latter?&lt;br /&gt; It is possible to know the roadmap for 7. 3? &lt;br /&gt;&lt;br /&gt;Eric. </summary>
    <dc:creator>Eric DARIEL</dc:creator>
    <dc:date>2020-07-04T08:56:44Z</dc:date>
  </entry>
  <entry>
    <title>RE: Support of AMP in future Liferay version</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=117985563" />
    <author>
      <name>David H Nebinger</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=117985563</id>
    <updated>2019-12-04T22:01:07Z</updated>
    <published>2019-12-04T22:01:07Z</published>
    <summary type="html">The problem, of course, is consensus. While AMP might be important to you, better React integration is important to someone else. With so many pulls in so many different directions, it&amp;#39;s hard for any one direction to become a priority.&lt;br /&gt;&lt;br /&gt;And honestly, there&amp;#39;s a lot of credible high-profile web developers who suggest avoiding AMP at all costs, such as this article suggests: &lt;a href="https://www.theregister.co.uk/2017/05/19/open_source_insider_google_amp_bad_bad_bad/"&gt;https://www.theregister.co.uk/2017/05/19/open_source_insider_google_amp_bad_bad_bad/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you read that and other articles, there seems to be a lot of good sense behind avoiding AMP.</summary>
    <dc:creator>David H Nebinger</dc:creator>
    <dc:date>2019-12-04T22:01:07Z</dc:date>
  </entry>
  <entry>
    <title>Support of AMP in future Liferay version</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=117980531" />
    <author>
      <name>Eric DARIEL</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=117980531</id>
    <updated>2025-10-21T05:12:37Z</updated>
    <published>2019-12-04T20:59:16Z</published>
    <summary type="html">It would be great if Liferay can support AMP. &lt;br /&gt;I think we can make AMP pages with a new dedicated theme but it will great to have it included in OOTB. </summary>
    <dc:creator>Eric DARIEL</dc:creator>
    <dc:date>2019-12-04T20:59:16Z</dc:date>
  </entry>
</feed>
