I have not forgotten it, its on my roadmap, but its not done yet. You could remove the default meta description from site settings, as this is whats used on pages like login or register. To me login and register should have the main site description and keywords. What do you think should be on those pages for meta? and why?

Best,

Joe

I've thought through features like the blog and making it possible to add keywords and description from within different features. I have a plan for that.

Pages like Register and Login are a different animal. I could add site settings for those, but I'm interested to know what is considered best practice for those pages in terms of giving them key words or description. They are not content pages, so it seems to me this should be minimal data there just indicating the main keywords and description for the site (as it does now) or even less info,  maybe just something indicating the site name and the purpose of the page.

Before I put my time into making those pages customizable I want to hear the business rationale of why that should be customizable and an example story of how you would use it and why.

Best,

Joe

Perhaps I'm the only one who sees the advantage of this

all I'm asking you to do is explain it, whats the benefit? make me see it too.

Best,

Joe

For best security its better not to have much on the login or register page. Those pages should be separate from content and should use SSL if possible. In my opinion these are best practices.

So for example if it were possible for users to put content on those pages they could put images with src=http://someimage.png and now the user trying to login or register gets a browser warning about the page has some insecure items because the page enforces ssl but there is content that is not using ssl.

In my opinion its best to keep the login page and the register page focused on their purpose.

If you want to make a custom registration module or login module that can be put on pages you can do that, but it then it becomes difficult to ensure the data is submitted using SSL. One solution that comes to mind is maybe making a Silverlight login control, because inside the silverlight control you are independent of the main page form and can easily force an ssl submission even if the container page is not under ssl. I'm going to be experimenting with Silverlight myself and may implement this. So then if customers want their login page all decorated they can just put the silverlight login module on a content page.

Best,

Joe

FYI, I've completed the work to have meta description and keywords in the blog. Its in svn trunk now so it will be in the next release.

I also added the ability to create an html Excerpt in the blog. If you enable Excerpts and you don't specify the Excerpt, it will autogenerate a plain text one as it did before, but if you edit the Excerpt in the editor, then it will use whatever you put there,it won't truncate it to the excerpt length setting.

Best,

Joe

I will be making a new release soon. If you can't wait for me, then the steps I follow to produce the releases is here, nothing stops developers from making their own releases. I make releases to update mojoportal.com more frequently than I make official releases, so I can make sure there aren't any major problems in official releases. This site is currently running a build from yesterday.

Best,

Joe