Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
My justifications mostly centered on my fabulousness—modest, I know. But the more I got to know the system, the more I realized that, alas, they gave me the keys because they were supremely confident in their safeguards. The work I’d be doing mostly revolved around using templates, editing existing content, and making new content using lots of widgets. Little did I know that each of these contained intentional safeguards to prevent the “non-techie class” from wrecking the website.
For instance, the Drag & Drop page building means that I’m basically playing electronic Legos to create my page structure. I don’t make the blocks, but I do construct my unique page--even make my own templates--using the established widget selection. That’s totally fine with me. When editing content on the live site, I know how to undo any mess I create by reverting. Other pages, I can’t touch at all, forcing me to seek the appropriate guidance as to why, etc. There’s usually a good reason, so I don’t quibble (well maybe a little in my head, but not out loud).
Basically, the underlying protections mean that I can be Picasso and make whatever I want, noodle around the back end like a pro without the worry of the big boss wondering why the site crashed or the homepage is suddenly blank. That’s a big relief all around.
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.