make meta cache redundant

1 files changed, 0 insertions, 4 deletions

diff --git a/README.md b/README.md
index d7c3709..80a302e 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,6 @@ You will notice soon that all site content is located in `../foo.zone-content/`
 ../foo.zone-content/gemtext
 ../foo.zone-content/html
 ../foo.zone-content/md
-../foo.zone-content/meta
 ```
 
 ### Alternative config file path
@@ -63,7 +62,6 @@ Whereas you only want to edit the content in the `gemtext` folder directly. The
 * `gemtext`: The Gemini Gemtext markup files of the internet site.
 * `html`: The XHTML version of it.
 * `md`: The Markdown version of it. 
-* `meta`: Some metadata of all Gemtext blog posts. It's used by `gemtexter` internally for Atom feed generation.
 * `cache`: Some volatile cache data for speeding up Atom feed generation.
 
 ### Special HTML configuration
@@ -90,8 +88,6 @@ A subsequent `./gemtexter --generate` will then detect the new post and link it
 
 Once all of that is done, the `gemtexter` script will convert the new post (plus all the indices and the Atom feed) to the other formats, too (e.g. HTML, Markdown).
 
-You can also have a look at `$BASE_CONTENT_DIR/meta/gemfeed`. There is a metafile for each blog post stored. These metafiles are required for the generation of the Atom feed. You can edit these metafiles manually and run `./gemtexter --generate` or `./gemtexter --feed` again if you want to change some of the Atom feed content.
-
 ## Drafting a blog post before publishing it
 
 If you don't want to publish your article yet (e.g. don't advertise it on the Gemfeed and Atom feed yet), you can draft your article in `./gemtext/gemfeed/DRAFT-article-title-dash-separated.gmi` and when invoke `./gemtexter --draft` to generate the outputs. Once you want to publish your draft just rename `DRAFT` with the publishing date `YYYY-MM-DD` and from there everything works normally.