ui & design

We definitely should add Community SDK support for Hermes, yes.  In the meantime, I'm happy to share the Hermes v1 and v1.1 skins with any customers looking to use the Community SDK.  Let me discuss how to distribute with SuzieH .

Confirmed w/ support that there's no way to view the text keys for things that are only visible to logged-out users.

Support did go the extra mile to find the text key for us (by painstakingly searching the available keys & testing, just like I would have had to). This specific text key is: blog.articleactions.comment-on-this-button.title. HOWEVER - note that the same text key is used for "Comment" buttons/links for both anonymous and logged-in users.

tavasjn24 Below solution should have worked for you:

.lia-quilt-community-page .lia-quilt-column.lia-quilt-column-24.lia-quilt-column-single.lia-quilt-column-main-top-content {

    width: 100% !important;
    padding: 0px !important;
}

Let me know if you have any other query, happy to help!!

Hi bishalgoswami,

The quilt for the My Settings page (as mentioned by CarolineS) is called MyProfilePage.  However, the primary functionality of the settings page is handled in an out-of-the-box component called "tabs" which is not editable in Studio.

In my environment where I wanted to make changes to the settings page, I created my own component (which I called "custom.user.settings.tabs") where I first rendered the out-of-the-box component while wrapping it in my own custom div so I could make CSS-based changes, as shown below.

<#-- Render the out-of-the-box component -->
<div class="rsa-c-user-settings-tabs">
  <@component id="tabs"/>
</div>

I then used the <@liaAddScript> functionality to add jQuery to make other changes I needed, such as hiding the ability to change their email address or first/last name.  See the screenshots below.

Hope this helps!

MyProfilePage_quilt.pngMyProfilePage_component.png

SheenaK Forums v5 primarily enables threading, correct. But as a part of that, I think it allows the root message to appear on every page. 

Atlas uses Forums v5, which is how they are able to do that. 

This is the Quilt XML for the Atlas community ForumTopicPage.

<?xml version="1.0" encoding="UTF-8"?>
<quilt layout="two-column.main-side" nestable="false" disableTopCssClass="false">
  <add to="common-footer">
    <component id="quilt:Footer"/>
  </add>
  <add to="side-content">
    <component id="forums.widget.recent-threads" mode="slim"/>
    <component id="recommendations.widget.recommended-content-taplet" mode="slim"/>
    <component id="theme-lib.related-topics"/>
    <component id="forums.widget.related-messages-taplet" mode="slim"/>
    <component id="custom_content_15"/>
  </add>
  <add to="main-content">
    <component id="Lingotek_CP_Dashboard"/>
    <component id="forums.widget.related-messages-taplet" mode="slim"/>
    <component id="topic-message"/>
    <component id="thread-pager"/>
    <component id="solution-count-conditional"/>
    <component id="solution-list"/>
    <component id="reply-count-conditional"/>
    <component id="message-pager"/>
    <component id="message-list-detail-with-inline-editors"/>
    <component id="comment-editor-submit-button-alert-forum"/>
  </add>
  <add to="common-header">
    <component id="quilt:Header"/>
    <component id="custom_content_19"/>
  </add>
  <remove from="sub-header-main" for="Header">
    <component id="common.widget.page-title"/>
  </remove>
</quilt>