Announcing the Khoros Titans Program
I’m extremely excited to announce that we are launching a new user recognition program here at Khoros. The Khoros Titans! Our previous user recognition programs have been quite successful, but over the past few years have waned in audience, engagement, and execution. The Titans program aims to reinvigorate what it means to be a power user of the Khoros platform! The program introduces four levels of Titan and will run in partnership with our Khoros Core program which caters to a (mostly) different audience. Our Titans will be recognized on a regular basis as people enter the program or gain more levels. How do I become a Titan? Great question! You: Must be a current paying customer or an approved consultant* Must remain in good standing on Atlas per the Code of Conduct with no infractions May not work for a competitor Must meet certain criteria as listed on our Titans program page - these criteria take into account Atlas participation, attendance & engagement with different media such as webinars and product coaching, and in-application activities* From time to time, we may adjust criteria and invite highly engaged customers into the Titans program based on their strengths in strategy and execution, as well as their help spreading the love for Khoros and driving enterprise customer experience initiatives. What’s in it for me? What are the benefits? On top of the formal recognition provided in our regular updates of new Titans, members also gain a unique badge and label on Atlas, exclusive access to group hubs, greater networking opportunities within the Titans, and opportunities to build their own brands. There are so many ways to grow your knowledge of the Khoros platform. To see what some of these are, along with benefits at each Titan level, check out our Titans program page. Who are some current Titans? We have a set of amazing Titans, and look forward to adding you to the ranks, too. You can identify Titans on Atlas by a blue badge next to their name on posts, the Titan badge on their profiles, or by going to our Titans program page. In addition to this, you’ll see showcased blogs and highlights about our Titans around the community! We look forward to your thoughts on our program, and please let us know if you have any questions. BlakeH - Community Manager AnnaL - Director, CX and Systems PhilippeM - VP, Customer Experience * Consultants have slightly different criteria. Please contact AryannaK for the time being.14KViewsSign in to react to this post6CommentsKhoros Communities moves to The Cloud
Photo by Alex Machado on Unsplash Nearly two years ago, the Khoros Communities Engineering organization began to move from co-located data centers to AWS cloud services. It's been a long process, but we're nearly complete. Technical Manager Aditya Pandurangi AdityaP , was kind enough to discuss the project with me. Q: Can you summarize what cloud services are and how Khoros Communities uses them? A: A cloud service, at a basic level, is a collection of many data centers that are spread across multiple locations and owned by a cloud service provider such as Amazon Web Services (AWS) or Microsoft Azure. The provider offers companies like Khoros a cloud-based platform, infrastructure, and storage services. In this case, the infrastructure to host and manage Khoros Communities. The cloud service provides a user interface or a set of APIs to request and manage specific hardware with the software of our choosing. The cloud service provider handles the hardware and maintenance, and we're in control of how we allocate resources. Before cloud services, companies had to have their own hardware located in a data center (either on-premise or in a colocated data center with multiple companies). This meant that companies managed the acquisition and maintenance of their own hardware in addition to managing network traffic and other management tasks. Handling hardware failures, hardware replacements, and physically moving the hardware was all in the company's purview. Khoros Communities, for example, had our own servers and equipment running in two data centers: one in Europe (Amsterdam) and one in the West Coast US (San Jose, California). In the cloud, we no longer worry about sourcing hardware, moving it physically, dealing with failures and outages, sourcing data center facilities, or paying data center storage rates. We don’t need to have Khoros employees add, remove, troubleshoot, and replace physical machines when we need more resources or if something breaks. In The Cloud™, everything is done for you. Q: Any downsides? A: There will always be sporadic hardware failures and restarts in the cloud that might temporarily make our services unavailable. That said, Khoros has built-in redundancy to handle failures as gracefully as possible. Also, the costs of using a cloud service over the long term are probably a bit higher because we don’t own the hardware and can’t amortize the cost over the duration of ownership. Despite those points, moving to the cloud is very much a net benefit. It’s allowed us to do cool, new things that we couldn't before, as well as offer our customers a better experience. Q: What does this migration mean for Khoros Communities customers? A. This migration enables us to provide flexibility to our customers in ways we couldn't before. We can now scale our resources to the needs of any customer. For example, some customers host large events where they see a 2-3x increase in traffic on already busy communities. We're talking lots of views and demands on performance. If a game company has a huge game release taking place or if a software company is holding a major event, we can make sure we have enough hardware ready and on standby as needed. Behind the scenes, our Engineering organization has much more flexibility, which benefits the customer. Unlike in the data center, we’re able to adjust our resources on the fly. More app servers needed? Give TechOps a couple of minutes to an hour -- done! Our database is getting overloaded and needs to be doubled in size temporarily? Once again, shine the TechOps signal -- done! We’ve been able to handle outages like never before, and we’ve been able to support many more customers and resources. Q: What does our AWS infrastructure look like? A: This is a high-level diagram. Q: What were some of the challenges you faced? A: The new environment presented a few challenges. AWS uses a paradigm of separate, siloed regions for different environments (such as QA vs. Production). This was a change from our datacenter infrastructure that used region-agnostic services. In the cloud, each region requires its own service deployment. This created extra work for teams that migrated their services to the cloud, but it was worth the trouble. Our infrastructure is more resilient -- there isn’t a single shared point of failure. An issue in one region does not affect the others. The migration required several teams within the Community Engineering organization to improve services and update workflows. We broke large, multi-purpose services into smaller parts with a more narrow focus. While that led to improved security, technology updates, and better performance, we had to shake off old habits and adjust to multi-step processes. Q: How big was this project, and how long has it been in progress? A: After a couple of false starts, we created the first JIRA ticket for this project on May 15th, 2018, so I think we can consider that the beginning of the project. This migration has been a massive undertaking that’s taken the effort of many teams. A multi-year project takes endurance. For fun, we hung a child's growth chart (like something you'd use to track height over time) in the San Francisco office. Each week, we'd update the chart. This worked great, until Covid when we shut down the office to shelter in place. We got a chance to go back to the office in April to pick up personal items. The chart was still there and we updated our progress. (We got a little lazy with that chunk in the middle where we just drew a simple line.) Later on, Jake Rozin (JakeRo), an engineer in our Customer Operations group, built a UI for us to track the status of community migration. Here's a simplified, sanitized version of the page as we were just finishing moving communities out of the Amsterdam data center. Q: What kind of coordination did the migration require? How many different teams had to work together to make this happen? A: This effort has taken the coordination of many different groups. The primary teams involved have been Technical Operations (TechOps), Application Operations (ApOps), Information Security (InfoSec), and Rocket. Each of these teams has played a vital daily role in the AWS migration process. In addition, all the teams responsible for individual microservices were involved. These teams have had to convert their services to use our new service deployment pattern in AWS, including Dockerizing their service and coordinating with the groups above to migrate and set up infrastructure. Q: What's the Rocket team? A: Rocket is an Engineering team in the Community organization. Essentially the team acts as the glue between TechOps and Engineering. While TechOps deals with networking and setting up/monitoring our infrastructure, the Rocket team works one layer above. We design and implement deployment patterns and pipelines used to integrate Khoros Communities services with our AWS infrastructure. Engineering teams across the Community organization consult us about using our deployment patterns and the best ways to support different service types. Rocket also builds internal tools. For example, we built one service to determine whether we can scale a community to another node and another to find the correct service to perform cloud-based operations (such as adding/removing targets from a load balancer or creating a CDN distribution). Other projects include: improving our security practices and leveraging new cloud-based security options, such as encrypted parameter stores and policy-based access controls (in conjunction with TechOps and InfoSec) updating our current provisioning and de-provisioning processes to work with the new cloud infrastructure and paradigm (in conjunction with TechOps) Q: Did the Rocket team have to build services or tools for the migration process? A: We did! Unfortunately, we are in the process of patenting them. Once we get those filed, we'll write another post with the details 😁 Q: What have been the major milestones for the project? A: We’ve had several major milestones throughout the AWS migration. Proof of concept: Our first milestone in 2018 was building and testing the AWS environment and developing a migration plan. We started with a basic cutover process. This initial proof of concept proved that Khoros could effectively host communities in AWS. The plan slowly evolved to more detailed cutover steps and enabled us to plan for the complete migration. Atlas (Khoros's community) was among the first communities hosted in the cloud. Iteration and automation: Process iteration led to more detailed cutover steps as well as automation services. That brought us to our next major milestone, where we could pass customer migration tasks to our AppOps team and free up Rocket team resources. EMEA community migration and first data center shutdown: End of October/mid-November of 2019, we moved every EMEA customer out of the Amsterdam colocation and into AWS. From there, TechOps completely shut down the Amsterdam data center. AMER community migration: As of Apr 14th, we reached our next milestone. All our AMER communities are in AWS. All that remains are the final milestones -- completing service migration and shutting down the US datacenter in San Jose. Once this happens at the end of June, our AWS project will finally be complete! Q: Can you share and charts or metrics showing improved performance for customers due to the migration? A: Sure. The following charts show the drop in beacon times pre and post-AWS migration. Beacon time is our way of measuring the time it takes a human (we filter out bots) to load a page on a community. Lower beacon times signal that the page being viewed loaded faster. (The numbers on the Y-axis are time in milliseconds.) Two of the customers featured in these charts have heavily trafficked communities. I picked the third at random. You can see that they all showed nice improvements post-migration. Customer 1 Customer 2 Customer 3 Q: Nice! What is it about AWS that lowers beacon times? A: There are a few factors. Our servers in the datacenter were starting to age and the AWS servers are newer, have better CPUs, and thus perform better. In addition, we started routing all traffic through Cloudfront as a CDN, which serves as a caching layer. I imagine that AWS also optimizes the route by which Cloudfront reaches the load balancers for speed. Thanks so much, Aditya! We appreciate your insight and all the details. We'll end here, but before we do, let's give a shout out to all the folks who made the AWS migration possible: Rocket: JonL,eddielo), AdityaP , LauraPe , KaranS , hernan_vinuesa TechOps: BillKr, CanC, ChrisSa, DanielA, DavidSu, EricV, GeorgeB, GokulN, KunjalS, MarcS, MarkJ, MattW, MichaelCa, TauqeerA, WillY Information Security: BryanM, JuanCo, ManjunathM, MinhN, MohanaC, PeterN, SoumyaR, SuyashM Application Operations: kh-mso, ArunkumarG, DimitarI, Georgi Todorov, MichaelM, NicholasD, RonT, (WeiS)ViewsSign in to react to this postCommentsAtlas Redesign Update
The Atlas team is proud to present the next stage of the Atlas Redesign Project! Since the previous redesign, we’ve continued to listen to our members’ comments and suggestions about Atlas and believe we are moving in the right direction. Take some time to review the updates and learn about the strides we have made to enhance your experience with Khoros and our community. Let us know what you think about the changes here in the comments or in Suggestions for Atlas! Your feedback will continue to drive the changes that you want to see. Navigation Bar As the most common starting point for users, the Navigation Bar has been a focal point for the team. This update comes with a now beautifully interactive menu where color-coded category tabs light up. We also fixed a few issues from previous iterations by placing a permanent search bar and solving the disappearing category icons. Category Page Every category in Atlas is unique, filled with a wealth of information for you to discover. We wanted our category top pages to reflect that. Each category now has product colors for visual signposting, keeping in line with the navigation bar theme. We reduced the number of category cards and shifted the group hub component higher, making it easier to distinguish discussion types and find content. *Release notes are now located in the blogs area. Search The process of searching the community has been streamlined with a few simple changes. Filters are now located on the left sidebar, and more visibility is given to the basic search options. We are currently continuing work on improving search performance. Three Dot Menus We have replaced the three vertical dots menu (kabob menu) on Search, Group Hubs, Blog/TKB Dashboard, and Private Messages with more descriptive options. This gives users better visibility into the purpose of different menus.ViewsSign in to react to this postComments2022 Kicks Off With Big Updates to Dev Docs
2021 was an incredible year for the Khoros developer community. We incorporated new products and companies into our developer experience, refined navigation throughout our Developer Docs Portal (DDP). We introduced new features to help visualize use cases and demonstrate best practices. 2022 is set to be even better, with a ton of new features and improvements set to roll out early in the year. A refresh of our documentation's visual design, API reference tools, and an abundance of new content are just some of the ways 2022 is set to be the best year yet for our developer community. Our Growing Team Our Developer Documentation team grew in 2021 with the addition of JavidH. Javid's years of experience and fresh insight have proven invaluable to our Khoros family. He's been working primarily with the Khoros Community and Khoros Flow Developer Docs Portals. Recipes One of the newest features of our DDP platform, powered by Readme.io, is Recipes. With Recipes, we can explore and break down complex API requests and code examples to give context to each individual object, field, variable, etc. Our team has plans to roll out recipes throughout 2022, covering a wide range of use cases, including individualized API request examples that demonstrate the power of our Khoros APIs. You can find some examples of our existing Recipes below: Create a Monitoring Bot (Care) Pass Conversation Control to Agent from Bot (Care) Create a Group Hub with an Avatar (Community) Navigation and UX improvements We took significant steps in 2021 to improve the navigation of our DDP. These include updating our home and category pages to simplify and shorten the navigation flow between the home page and your target content. In 2022, we are taking what we've learned from the initial rollout and applying it to a design overhaul, modernizing the look and feel of our documentation. The UX changes were based on customer feedback with internal and external developer documentation users. Thank you to the customers and internal Khoros teams that we interviewed during our research phase. And a huge thank you to our designer JhilikR and front-end developers ShikherM and AbhishekGu ! Streamlined landing page Up-leveled page feedback tools Persistent header and improved signposting Streamlined landing page Use one less click to get to the product documentation you're looking for. The streamlined hover menu removes the need for a stop at landing pages for each documentation set. Up-leveled Page Feedback Tools Many of you have used the Suggest Edit feature in the DDP Guide pages, but less have used our page feedback component – Did this page help you? widget where you can give a thumbs up or thumbs down vote and add comments so that we understand your rating. We've moved the page feedback widget to the top of the page so that it is move visible. Please give us your ratings and comments to help us improve. We value your opinions and your input improves the experience for the entire Developer community. Keep those Suggested Edits flowing too! We love 'em! Persistent Header and Improved Signposting Internal and external customers expressed frustration with losing their place while working in our Guides and Reference pages. We made the header persistent so that you can easily switch between guides, references, recipes, and changelog. We also added product signposting so that it is clear where you are within our documentation. Improved Tablet Experience to Come Nearly 99% of views on the DDP are from a desktop. That said, we see that there are occasionally folks who need to use the docs from a tablet or mobile device. The new landing page design has been designed for a table viewport. The next steps are to work at navigation and layout improvements on guides, recipes, and reference pages. Developer flows in Maia Maia, the Atlas chatbot now graces the pages of the DDP. Existing customers can do things like file a support ticket, learn about our Titans program, and get to Khoros knowledge bases, ideas boards, and product coaching resources directly from the developer.khoros.com. Existing and prospective customers can schedule a demo, connect with a sales agent, and learn about Khoros solutions. Learn more about the integration in the Developer Blog. SEO Improvements One new project for 2022 that we're working on right now is a site-wide audit on our content's SEO. We want to make our content easier to find through the built-in search. This means renaming some existing content to better match the search queries developers are entering in. We expect these improvements to be continually made across the DDP in January and February. Additional Diagrams, Images, and More We realize not everyone learns best by reading text. So, we are set to add a ton of new diagrams and images to help visualize the data, content, and user experience flow. It's our goal to not only help tell the story of what our APIs can do but to inspire the developer community to map out new ways to get the most out of the APIs.ViewsSign in to react to this postCommentsAutumn Innovation Launch: New integrations & AI across our entire platform
In 2020, brands have adapted to shifts in everything from business practices to employee structure to customer expectations. But there’s one thing that never changes, and we’ve seen it reinforced time and time again over the course of this year: the fundamental need for human connection. We’re announcing our 2020 Autumn Launch to help our customers develop this important form of connection with their own customers. Our newest innovations will help brands improve their community management, team collaboration, and customer engagement processes. Here’s what’s new in the platform: The best way to manage all of your communities With new gesture-based scrolling (patent pending) and machine learning in Manage View to reject hate speech, Khoros is innovating on behalf of the people nurturing both owned communities and social media communities. Whether moderating for spam and accuracy or managing for participation and delight, community managers will have the best Engagement Manager on the market today. Learn more here. Shared visibility and coordination between Marketing and Service teams We’re bringing customer-facing teams together with shared visibility and coordination. With Khoros, service teams can take the right action on conversations based on the marketing content that inspired it. Marketing context — like campaign initiatives, plans, and tags — will now inform workflows and automatically route, prioritize, and filter conversations so customers have a cohesive experience with the brand. Plus, all customer-facing teams will see who owns the conversation so they can break down silos and speak with one brand voice. ____________________________________________________________________ What’s new in Khoros Communities Events experiences Our new Event capability with social media video live streaming makes it more rewarding to host events in your branded community. Brands can now also simplify digital events, from the initial creation and promotion to the actual management of the event. When in-person gatherings are limited or restricted, hosting events in online communities can help brands maintain crucial customer relationships. Improved knowledge sourcing and streamlined communication with Slack Our new Slack integration allows brands to connect their community on Khoros Communities in exciting ways. Now, Khoros offers the only solution in the industry for brands to seamlessly communicate and search their owned community within Slack. Learn more here. ____________________________________________________________________ What’s new in Khoros Care Email integration and channel consolidation We’re excited to add email to our repertoire of supported channels in Khoros Care. Brands will now have the ability to respond to inbound emails, and much more, directly in the platform, alongside other supported digital service channels: chat, messaging, social media, owned communities, reviews, and more. AI updates to ease agent strain and improve accuracy Our two newest AI capabilities, intent detection and suggested responses, will help agents increase conversation volume without sacrificing quality. With intent detection, agents will no longer need to manually input every keyword. Instead, intent detection uses natural language processing (NLP) to identify consumer intents and automatically tag conversations. The suggested responses feature analyzes historic brand conversations and surfaces the top responses, improving accuracy and saving agents time and effort, while still conveying a human touch to customers. ____________________________________________________________________ What’s new in Khoros Marketing Greater flexibility for social media marketers With new LinkedIn ads visibility — in addition to existing Facebook and Instagram ads visibility — social media marketers will now be able to see paid and organic data alongside one another. This will help them develop a holistic approach across social media channels. Learn more here. Custom defined metrics will give social media managers and analysts control over how they define success with the world’s most unified social media analytics platform. Learn more here. Announcing early access for paid execution for Facebook & Instagram, which enables marketers to seamlessly switch from publishing organic content to creating bespoke ads, with calendar visibility and analytics insight across social channels. Reach out to your Customer Success Manager if you are interested in joining the early access program.ViewsSign in to react to this postCommentsAtlas Proudly Adds Pronouns Option to Profile
Khoros is committed to creating an inclusive workplace for all, and that means recognizing the pronouns each of us use. Pronouns are used to refer to a person’s gender, and aren’t always what you might expect just by looking at someone. While not required, using your pronouns on Atlas can be a good way to remind people of your pronouns and continue normalizing discussions around them. Click here for more information on what pronouns are and how you can get used to using pronouns like they/them. Here’s how to include pronouns on your profile today! Update your profile Your profile management tools can be accessed by clicking on ‘my settings’ under your avatar icon on the top right of Atlas. Once on the ‘My settings: Personal’ page, click on the dropdown bar and select ‘Personal information.’ From here, you can add your preferred pronouns. Here are a few that are more commonly used: He/Him/His She/Her/Hers They/Them/Theirs After saving your preferred pronouns, click the ‘Make pronouns public’ link to be taken to your privacy settings. Making pronouns public On your ‘Privacy Settings’ page, you can change who can see what on your profile. To have pronouns displayed on your profile, set ‘Show private information in profile’ to ‘All.’ This option only displays some basic information on your profile including: name, pronoun, bio, friends list, and social fields if filled in. Your email address is not displayed. Now you can proudly display your pronouns on your Atlas profile.ViewsSign in to react to this postCommentsUpdates to Atlas Aug-Sep 2020
NEW Events Beta We have added Events Beta to the Khoros Event’s Group Hub. Head over to the Events area for a list of the Khoros Engage breakout sessions and keynote speakers. Make sure to RSVP and engage with your peers in any comments section! Please note that Events are still beta, more information to come. Community Strategy Discussion Forum The new Community Strategy Discussion forum is now open. Subscribe to the forum to stay up to date on the latest community strategy discussions! Increased Signposting We are adding new signposting components, which are located on the bottom left corner. This is intended to better inform customers of which areas are public vs. customer only. This is not visible on all pages, including category pages with mixed content and some hidden group hubs. Keep an eye out for upcoming posts on the Communities Blog to learn how this custom code was implemented. Blog Label Cloud As part of the team’s efforts to better represent each category’s content, we have introduced a label cloud to the top of the blog areas. The drop-down on the top left allows users to choose between 'Top Labels' or alphabetical. As we continue to work on categorizing content, the label cloud will improve and better represent the available content. UPDATED/FIXED Fixed overlapping rank names on component Worked on by AndyK and AbhishekGu Renamed Tags to Keywords Worked on by AndyK and NoraG Corrected brand colors throughout Atlas Worked on by AndyK, NoraG, and AbhishekGu Updated Atlas Hub Structure Worked on by JamilaR and AndrisG Update contact support page Worked on by AndyK ARCHIVED/REMOVED Retired Facebook login to Atlas Worked on by AndyK Archived Khoros Data API user Group Worked on by AndrisG and JamilaRViewsSign in to react to this postCommentsCommunity Experience Surveys Are Now Available in Aurora
Overview Community Experience Surveys enable you to gather responses directly from members through short in-product prompts. You control who sees the survey, when it appears, how often it's shown, and which standardized questions are asked. Once responses start coming in, you can export the results for review or analysis. These surveys allow you to easily quantify the impact and performance of your community, arming you with the data needed to make decisions and take action. This feature is particularly useful for checking in with members after key interactions or tracking trends in satisfaction over time. Key Features When setting up a survey, there are a few main areas to consider: Branding: Set the name, upload a logo, and choose colors to keep the survey consistent with your community’s design. Behavior: Decide which members will see the survey, under what conditions, and how frequently it should appear. Questions: Choose from a list of standardized questions to shape the kind of feedback you want to collect. Activation: Once everything is configured, you can turn the survey on (or off) with a single toggle. These options give you flexibility without requiring a complicated setup. How to Use It To configure a survey: Go to Settings > Content Features > Community Experience Surveys Follow the steps in the Create community experience surveys documentation To export results: Go to Content Features > Community Experience Surveys > Questions and Answers Click Export To help you get started, we've put together a few best practices and common FAQs for reference here. We are looking forward to seeing your usage of this survey, and would love to hear your feedback on new Community Experience Survey-related enhancements that you'd like to see in the future.ViewsSign in to react to this postComments[Podcast] Being Present on Social Media: It’s Harder than You Think
It’s finally here, and we couldn’t be more excited. The Customer Engagement team is proud to present the first episode of Titans of Customer Engagement: A Customer Experience Podcast, Being Present on Social Media: It's Harder than You Think featuring Kerrie Robert ExperianKerr, Social Media Manager of Customer Service at Experian. The Titans podcast features Khoros customers sharing best practices, insight on the evolution of customer and business demands, and what is or is not working when it comes to successful digital customer engagement strategies. Please share with your peers, leave us a rating or review, and continue the conversation in the comments section! Listen to strategic conversations with your peers and leaders about creating the world’s greatest customer experiences. Now available where you listen to your favorite podcasts Apple Podcasts Spotify Amazon Google Podcasts Stitcher TuneIn Also, don't miss out on CX Confessions: The Customer Experience Show, a thought leadership podcast on CX featuring C-suite executives Interested in becoming a Titan of Customer Engagement? Learn about what it takes to ascend to Titan statusViewsSign in to react to this postCommentThanks for Helping Us Reach 100k Members!
If you’ve kept an eye on the front page of Atlas recently, you’ll notice that we passed the 100k all-time member mark this month. To our passionate community members: thanks for joining us on this journey! Your contributions got us to this point - from your thoughtful posts and helpful comments, to your kind kudos and brilliant Accepted Solutions, to your willingness to help us build one of the best communities for you and your fellow pros. When you see a colleague struggling with the same challenges you’ve been through, you offer help, advice, and insights. That simple, consistent willingness to help is what makes this community special among others, and it’s what (I believe) will help us get to the 200k member mark. In reflecting on what you’ve achieved together, we also want to ask for your favorite moments from your experience with Atlas and Khoros over the years. Just to spark some ideas: What’s your favorite thing about the Atlas community? Or your favorite memory? What value have Khoros and the Atlas community brought to your day-to-day work? What are the most valuable lessons you’ve learned from fellow CX pros here on Atlas? When did you join, and what has the community helped you achieve since then? What makes the Atlas community unique for you among other CX communities? With the recent UX revamp and Titans program activities, plus roadmap updates, the future feels bright for Atlas. Here’s to the road ahead, and thanks again for being part of our community!ViewsSign in to react to this postComment
14KViews
6Comments
