Rails-Designer/perron

AI Summary: This issue proposes changing the default file extension for newly generated Atom feeds from `.xml` to `.atom`. The change aims to improve semantic clarity and prevent potential conflicts when both RSS and Atom feeds are enabled without a specified path.

AI Summary: This GitHub issue proposes adding an `--inline` flag to the content generator. This flag would leverage an existing 'inline rendering' feature to skip generating the `show` view template and instead generate a `show` action that directly renders the resource using `@resource.inline`. The goal is to reduce boilerplate and make the inline rendering feature more discoverable.

AI Summary: This issue proposes removing the syntax highlighting processor from the library because it's not plug-and-play as intended. It requires external dependencies and specific markup, making it difficult to use. The plan is to deprecate it and potentially replace it with a custom markdown parser or a community snippet.

AI Summary: This issue proposes adding an `inline` method to `Perron::Resource` to enable inline rendering of content directly from controller actions. This would eliminate the need for separate, often redundant, view files that simply render resource content, streamlining the development process.

AI Summary: The user is requesting to simplify the production build command in their Rails application. Currently, it requires explicitly setting `RAILS_ENV=production`, and they propose making this implicit so the command can be just `bin/rails perron:build`, while still allowing explicit overrides.

AI Summary: This issue proposes exploring the addition of a `@resource` annotation to HTML processors. This could enhance functionality, particularly for processors like the `ref` parameter processor, by allowing resource references to be defined in metadata or frontmatter.