CyJervis
Boss
Joined 11 years ago
Manager, Knowledge Programs for Support at Cloudera
User Profile
User Widgets
Contributions
Re: Driving Growth in Community with Banners & Content Gates
Interesting for sure, you would think the feed would be based on new content based on the newest first publish date/time not based on last modified. This does remind me that I need to eventually post my own findings from when we A/B tested gating all community solutions.Re: Is a Studio cheat sheet available?
If the image provided is the specific look you desire, that would require a custom component. That being said, I would look at the Atlas articles around Group hub pages and quilts as well as Group hub components. I am not aware of a cheat sheet for group hub components but in studio you can hover over a component and the pop up description will tell you which pages it can be used on.Re: "1" was searched 1,755 + 501 times one day in August?
If you click into the day you can see what the most commonly used search terms were. it may give some insight. We had a couple of days like this and it seemed to be terms involving "nessus_was_" which according to google is likely related to a security scanning tool.Re: Dev server best practices?
I'll echo the sentiments of StanGromer and Claudius . We however took it to an even larger level in our previous contract. We currently have 4 classic environments: Dev, Test, Stage and Production. We did this as we were doing a merger of two communities and wanted minimal disruption of stage and prod during the 6 month migration and redesign project. Here is how we worked through them. Development: only developers on this instance. They would do all their main work here including their Q&A and then copy/paste the changes into the test environment Test: The community team and others we assigned would test all the changes here and document any issues. The developers would then update and test the dev environment and pass fixes to the test environment for us to check again. Stage: once we gave final sign off on the test environment, all changes were copied and pasted into staging. We would then do shorted testing round to make sure everything appeared fine before pushing to production that same day if possible. Production: One more spot check after the push to ensure nothing went wrong For the project it was ok but I'd say the Test environment was overkill. Keeping them all in sync has been a major issue as we and the devs often explore setting changes and issues on an environment and forget to revert. When we updated the community to Hermes this year we used only three of the environments and honestly, we are dropping back to stage/prod upon our renewal later this month. As we are planning the Aurora move next year it didn't make sense to pay for the extra environments.
