I am a Site Collection Administrator currently managing a SharePoint 2016 environment. Over the years, I’ve honed my skills in using the Content Editor and Script Editor web parts to add custom HTML, CSS, and JavaScript to .aspx pages across our site collection and its subsites. These techniques have allowed me to develop tailored solutions for our business unit without needing to engage SharePoint farm admins or server-level developers.

However, with our impending migration to SharePoint Online, I am concerned about how these skills and methods will translate. From what I understand, the ability to use these web parts is either non-existent or extremely limited in the SharePoint Online environment. Additionally, I will not have access to PowerShell or higher-level roles such as Global Administrator or SharePoint Administrator.

Given these constraints, I am seeking advice on the following:

How can I continue to provide development services in SharePoint Online without the use of Content Editor and Script Editor web parts?What tools and techniques should I start learning now to prepare for this transition?Are there modern alternatives or best practices in SharePoint Online that I can leverage to achieve similar outcomes?How can I effectively develop and deploy solutions within the boundaries of the permissions I will have in SharePoint Online?

I want to ensure that I can still deliver value to my business unit by creating custom solutions and maintaining a high level of service. Any insights, resources, or experiences you can share would be greatly appreciated as we navigate this significant change.

Thank you for your support and guidance!

​I am a Site Collection Administrator currently managing a SharePoint 2016 environment. Over the years, I’ve honed my skills in using the Content Editor and Script Editor web parts to add custom HTML, CSS, and JavaScript to .aspx pages across our site collection and its subsites. These techniques have allowed me to develop tailored solutions for our business unit without needing to engage SharePoint farm admins or server-level developers. However, with our impending migration to SharePoint Online, I am concerned about how these skills and methods will translate. From what I understand, the ability to use these web parts is either non-existent or extremely limited in the SharePoint Online environment. Additionally, I will not have access to PowerShell or higher-level roles such as Global Administrator or SharePoint Administrator. Given these constraints, I am seeking advice on the following:How can I continue to provide development services in SharePoint Online without the use of Content Editor and Script Editor web parts?What tools and techniques should I start learning now to prepare for this transition?Are there modern alternatives or best practices in SharePoint Online that I can leverage to achieve similar outcomes?How can I effectively develop and deploy solutions within the boundaries of the permissions I will have in SharePoint Online?I want to ensure that I can still deliver value to my business unit by creating custom solutions and maintaining a high level of service. Any insights, resources, or experiences you can share would be greatly appreciated as we navigate this significant change. Thank you for your support and guidance!  Read More

​