4h ago

consolidated feedback from our developer when optimising or editing events

1. Limited Layout Customization ( "Templates are fairly rigid; while you can add logos, colors, and some branding, you don’t get full design freedom.") 2. Generic Look & Feel ("Out-of-the-box pages tend to look like other HeySummit events. This reduces the ability to create a truly unique branded experience, which is often critical for high-profile events.") 3. Poor Granular Styling Controls ( " You can adjust basic colors, fonts, and backgrounds, but not fine-tuned CSS-level changes unless you hack workarounds.") 4. Limited Media & Content Placement Options (" You can’t always place images, videos, or sponsor logos exactly where you want. This creates challenges for creating compelling landing/schedule pages.") 5. Lack of Custom Code Injection ("minimal ability to inject custom JavaScript, CSS, or HTML into event pages. This blocks advanced customizations or unique interactive features.") 6. Rigid Templates (" pre-built templates that auto-adjust, but they’re not fully flexible. We can’t easily tweak breakpoints or create unique responsive behaviors for different screen sizes.") 7. Limited Mobile Customization("You can’t design mobile layouts separately. The system auto-scales desktop designs, which often leads to spacing issues, oversized buttons, or squished layouts on smaller screens.") 8. No Custom CSS for Breakpoints("We can not inject custom CSS to define media queries. This blocks fine-tuning of how the design responds to tablets vs. phones vs. widescreen monitors.") 9. Image Cropping/Scaling Issues("Images can't be resized in ratio") 10. Backend Updating Issue ("While working live on the backend, the live version is not updated simultaneously, which causes confusion and overwork.") 11. Backend is really slow ("We have to encounter a lot of slow editing in the backend. ")

Reviewing

2 hours ago

Hi Claire - thanks for sharing your feedback - very much appreciated. There is a lot here that in time we hope to improve upon (such as expanding how templates work etc). However, its not going to be possible at this moment in time to pin an ETA to them. What i’d recommend though, is that new features / improvements aside, if you have hit actual bugs in the way something is supposed to work, then please do reach out to the support team so that they can be looked into and fixed.

2 hours ago

One suggestion for the slow backend experience - is to try managing your event via the standard HeySummit domain (i.e. yourevent.heysummit.com) rather than your custom domain (i.e. myevent.growcfo.com). Reason being, in a previous pre-event review, i recall highlighting that when accessing the site via your custom domain, loading pages seemed considerably slower. I dont recall hearing anything back from you regarding this, so i suspect this might still be causing the slowness you’ve described. Please do feel free to reach out to the support team though, if you continue to have speed and performance issues after trying out the recommendation above, as that will need to be looked into properly.

2 hours ago

If possible, if you can please also share a specific example of a situation where the public event page is not updating immediately when changing something in the backend. We do employ caching throughout but caches should be cleared when data is updated via the backend. If you have an example where this is not the case, please can I ask you to reach out to the support team with specific details - the support team can then look into it for you and all being well, help you resolve it.

2 hours ago

Thanks, Ben. All of our events are managed via the standard HeySummit domain. The only event where we use a custom domain is the Tech Showcase https://tech.growcfo.net/

2 hours ago

Ah thanks - thats interesting. Would it be at all possible for you to have your developer record a Loom video (or equivalent) and then share it with our support team at support@heysummit.com? It would be useful for them to see first hand the slowness you described.