Installation guide
A feed with a place to call home.
Design in FeedLuma. Install on your website. This guide describes the development workflow; public onboarding is not open yet.
Currently in development. Explore the design with sample content. Public signup, live Instagram connections and payments are not available yet.
Before you install
- Create a feed in an existing workspace and save its design.
- Add the destination hostname under Websites, without a path or port.
- Add the supplied DNS TXT record at
_feedluma.your-domain.com, then verify it in FeedLuma. - Publish the saved draft to that verified website. Publishing in production requires an active plan; public plan purchase is not yet enabled.
WordPress
Use the companion plugin.
- Install and activate the FeedLuma development plugin.
- Generate a read-only plugin token in FeedLuma Settings.
- Save the token under WordPress Settings → FeedLuma and select a feed.
- Insert the FeedLuma block or copy the shortcode provided by the app.
The token stays on the WordPress server. Editing happens in FeedLuma. The plugin is still awaiting WordPress runtime validation.
Other websites
Paste the embed.
Open Install in the feed editor and copy the generated code into a custom HTML section on the verified website.
<div data-feedluma="YOUR_FEED_ID"></div>
<script async src="https://feedluma.com/embed.js"></script>Example only. Replace YOUR_FEED_ID with the identifier from your published feed. Your website builder must allow custom scripts.
When something needs attention.
The feed says it is unavailable.
Check that the draft was published, the subscription is active, and the website hostname exactly matches the verified domain. The www and non-www hostnames are different.
My saved edits are not showing.
Save draft and Publish are separate actions. Publish the saved revision to update the website.
DNS verification has not completed.
Check the TXT record name and value against the app, then allow time for DNS propagation before trying again.
The WordPress feed list will not load.
Check the app URL and token. Creating a replacement token revokes the previous token, so update every installation that used it.