4 ms·

I’m working on a simple website generator for developers and content creators. I’ve already included everything a user would want for a complete website, inclu

I’m working on a simple website generator for developers and content creators. I’ve already included everything a user would want for a complete website, including a robots.txt, sitemaps, perfect Lighthouse seo score, rich snippets, and a ton of other stuff. Should I consider adding an auto generated security.txt file along side the robots.txt file for users? Do you’all think a security.txt file is something users would want in 2023? Or would it look stupid and confusing? https://github.com/elegantframework/elegant-cli https://github.com/elegantframework/elegant-cli

hoofhearted 3y ago
I got a few upvotes so far, but no comments! Lol I may put out a few feelers, and put this topic up for a RFC and discussion on GitHub. It seems like an interesting new little web thing, and is super easy to implement. I just share the same concerns as others have mentioned with bots and spammers misusing this file.
cuttysnark 3y ago
IMO, including those generated .txt files is a small[ish] feat that's important to those that are looking for it, and benign to those that don't need it or know what it is. I suspect most users who use a site generator would be happy with more "automagic"—especially if it were 1. easy to config or turn off and 2. addressing important things like security-related contact info, or how a web-scraping bot should respect your domain. Also: "simple" generators often veer into "complicated" territory by adding crap features. Elegant appears to lack crap features; IMO, adding *.txt would not complicate or confuse.
- hoofhearted 3y ago
  Hey thank you for the kind words!! No crap features here :) We have started with a basic clean foundation, and are now in the process of building up all the essential features an app owner would want, and none of the crap they wouldn't lol. I appreciate your feedback! I have opened an RFC and will be pushing this idea through the feature pipeline ASAP: https://github.com/orgs/elegantframework/discussions/55 https://github.com/orgs/elegantframework/discussions/55

hoofhearted 3y ago

I got a few upvotes so far, but no comments! Lol I may put out a few feelers, and put this topic up for a RFC and discussion on GitHub. It seems like an interesting new little web thing, and is super easy to implement. I just share the same concerns as others have mentioned with bots and spammers misusing this file.

cuttysnark 3y ago

IMO, including those generated .txt files is a small[ish] feat that's important to those that are looking for it, and benign to those that don't need it or know what it is. I suspect most users who use a site generator would be happy with more "automagic"—especially if it were 1. easy to config or turn off and 2. addressing important things like security-related contact info, or how a web-scraping bot should respect your domain. Also: "simple" generators often veer into "complicated" territory by adding crap features. Elegant appears to lack crap features; IMO, adding *.txt would not complicate or confuse.

hoofhearted 3y ago
Hey thank you for the kind words!! No crap features here :) We have started with a basic clean foundation, and are now in the process of building up all the essential features an app owner would want, and none of the crap they wouldn't lol. I appreciate your feedback! I have opened an RFC and will be pushing this idea through the feature pipeline ASAP: https://github.com/orgs/elegantframework/discussions/55 https://github.com/orgs/elegantframework/discussions/55