If you could add something to Kentico, what would it be and why?

Ability to modify page head section and html tag

Add ability to modify page head section and html tag from UI without need to modify PortalTemplate.aspx file.

133 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Radek Matěj shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

10 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • specac commented  ·   ·  Flag as inappropriate

    Would definitely like this ability to edit the HTML tag so we can easily add a HREFLANG attribute to our HTTP header for localisation.

  • Sasha Shevelev commented  ·   ·  Flag as inappropriate

    1. Open Graph, Twitter cards, Dublin Core tags.
    2. this should be just an extension of the current meta tag editing functionality. Why would we want to do this in code?
    3. Content admins and marketers should be able to add as many tags as they like. Viewing markup should be an extra option more for script injection code but simple tags should be easily added through a form type interface. Adding Google Analytics / mapping code should be manageable by the client. It exists in 100% of projects so why is it up to devs to implement?
    4. Content editors. Why would you want devs anywhere near this? It's content.
    5. As long as the tag values can be unique per page

    To sum up. Copy the metatag editing functionality from WordPress. Once a client has used the WP one they ask why they cant do the same in Kentico - Not a good look.

  • Ralph Spandl commented  ·   ·  Flag as inappropriate

    In our case, the only thing that was requested by SEO is inserting the lang attribute into the html tag. I usually prefer to set head content in Master page of if required in templates. Rarely use web parts for this scenario.

  • Ilesh Mistry commented  ·   ·  Flag as inappropriate

    Hello

    For me the HTML tag is really important to amend for Accessibility reasons when using the Portal Engine approach.

    We need to be able to set the HTML Language, which we can't set without amending the PortalTemplate.aspx file.

    Thanks

    Ilesh

  • Sasha Shevelev commented  ·   ·  Flag as inappropriate

    I'd like to add to this. I just started using version 8 and have the following improvements.
    1. Increase the size of the text fields to enter the metadata.
    2. Have a grid view where you can see all pages and enter all metadata without hing to jump from page to page.
    3. Provide more help to basic users as in recommended lengths for metadata fields for Google optimisation.
    4. Ability to add your own custom tags

  • AdminRadek Matěj (Content Management Product Owner, Kentico) commented  ·   ·  Flag as inappropriate

    Hi Jarrod, thank you for your suggestion. Master page tab in CMSDesk doesn't show final HTML output. For example some webparts can render their content into master page tags, so the HTML is there just to give you context, what you are editing. If you want full HTML control, you can use MVC or ASPX templates together with ASP.NET master pages.

    Many customers report that they want more control over the HTML. We are planning some improvements in this area.

  • Anar commented  ·   ·  Flag as inappropriate

    Currently we are doing this by adding the following code:
    protected void Page_Init(object sender, EventArgs e)
    {
    BodyClass += " " + CMS.CMSHelper.CMSContext.ViewMode.ToString();
    }

    But as you know, this file might be overwritten by a hotfix/upgrade.

Feedback and Knowledge Base