Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Suppose I have some sort of proprietary web framework. Should I include a <meta generator="My framework"> tag in the generated files?
I noticed that StackExchange 0.9 applications do that, and wondered what are the pros/cons of doing it. Does it have any effect, or is it just useful for people looking at the source to see?
I’ve never seen a tag formatted like that before, with an attribute called
generatorand the generating software as its value. Usually you’ll see it presented asname="generator"and the generating software as its corresponding content, for example:Previously I was unaware of any standard for this, however it looks like HTML5 has gone ahead and standardized the use of “generator” as a metadata name. It describes it thus:
In the past when dynamic web apps weren’t that prevalent, certain web site editors, like FrontPage (there, I said it), would automatically insert generator tags when you create new HTML documents or publish sites using them. This was taken to mean “This page was created using FrontPage”. I don’t think any modern editors or IDEs do this anymore, but I could be wrong. It’s definitely commonly used in dynamic web apps today, however.