diff --git a/docs/getting_started.rst b/docs/getting_started.rst index c7f2e257..7155efce 100644 --- a/docs/getting_started.rst +++ b/docs/getting_started.rst @@ -202,23 +202,17 @@ of ``meta`` tags, the title out of the ``title`` tag, and the body out of the + This is the content of my super blog post. - - Content continues down here. -With HTML, there are two simple exceptions to the standard metadata. First, +With HTML, there is one simple exception to the standard metadata. ``tags`` can be specified either with the ``tags`` metadata, as is standard in Pelican, or with the ``keywords`` metadata, as is standard in HTML. The two can -be used interchangeably. The second note is that summaries are done differently -in HTML posts. Either a ``summary`` metadata tag can be supplied, or, as seen -above, you can place an HTML comment, ````, that -Pelican will recognize. Everything before the comment will be treated as a -summary. The content of the post will contain everything in the body tag, with -the special comment stripped out. +be used interchangeably. Note that, aside from the title, none of this metadata is mandatory: if the date is not specified, Pelican will rely on the file's "mtime" timestamp, and the diff --git a/pelican/readers.py b/pelican/readers.py index 8667a299..ecb49f9c 100644 --- a/pelican/readers.py +++ b/pelican/readers.py @@ -226,9 +226,6 @@ class HTMLReader(Reader): self._data_buffer += self.build_tag(tag, attrs, True) def handle_comment(self, data): - # if self._in_body and data.strip() == 'PELICAN_END_SUMMARY': - # self.metadata['summary'] = self._data_buffer - # else: self._data_buffer += ''.format(data) def handle_data(self, data):