What happens if I delete index.html?

I’m using Micro.blog only for its social part, not the blogging part. I’d like to disable RSS feeds on my blog and the sitemap.xml should not show entries either. Does deleting the index.html page achieve this or does it have other unintended side effects?

@sod Do you know?

No, deleting the homepage template (index.html) won’t affect other parts of your site, like RSS feeds or sitemap.xml. Those are handled by other templates.

Also, you can’t completely delete certain templates. If Micro.blog doesn’t find them in your theme, it just falls back to the default blank theme. So instead of deleting templates, you might want to modify them to output blank pages. Depending on what you’re trying to do, you could also consider using redirects or other tactics.

I’m guessing you don’t want to actually delete the blog from the Account page, since you’re using Micro.blog’s ActivityPub features linked to your custom domain?

Thanks for the response, That’s correct. I don’t want to delete the blog itself but be able to redirect parts of it to elsewhere. I tried redirecting the RSS feed but that did not work.

Okay, you probably have to disable RSS generation for the redirect to work. No gurantees, but this custom config.json worked for my test blog.

{
  "disableKinds": ["RSS"],
  "outputs": {
    "home": [ "HTML", "RSD", "ArchiveJSON", "PhotosJSON", "PodcastXML", "PodcastJSON" ],
    "page": [ "HTML" ],
    "section": [ "HTML" ],
    "taxonomy": [ "HTML", "JSON" ],
    "term": [ "HTML", "JSON" ]
  }
}

The above example stops Hugo from generating RSS files completely, and redirects should start working after that. You might have to perform a full rebuild to see the changes.

Thanks. It seems like I can’t do that because I’m on Micro.one, which doesn‘t include Custom Themes.

Oops, my bad, I didn’t check which plan you’re on. That’s right, custom themes aren’t included in the $1/month plan. I’ll let this dilemma simmer in the back of my head for a bit, but I’m afraid there’s no obvious workaround here, other than simply accepting the empty RSS feed.