Automate

Guillaume,

I have linked by subject what you are looking for.   I wish I had this advice when I started my first Foundation site in 2010.

Remember that Foundation is on Sharepoint with web parts proprietor to Winshuttle.   So this means that some MS functions will not work in Foundation.   Verify with Winshuttle technical team what would be the best Sharepoint version to have with Foundation.   Usually, many companies will have Central on a separate server from the existing Sharepoint server.


SharePoint Document Library – one or many?

 https://sharepointmaven.com/sharepoint-document-library-one-many/

 How many document libraries shall I have in a SharePoint Site?

 https://sharepointmaven.com/how-many-document-libraries-shall-i-have-in-a-sharepoint-site/

 Hub Sites vs. Subsites

 https://sharepointmaven.com/hub-sites-vs-subsites/

 SharePoint is not about templates!

 https://sharepointmaven.com/sharepoint-is-not-about-templates/

Naming convention scripts / forms / documents / templates / sites

Adopt a naming convention at the early stage of your project.   Name your scripts, forms, and sites in a way that it is easy to link them together.  Example:  Plant Maintenance site call it PM.  A recording for Maintenance Processing Notification Create, name it PM_IW21_V1.  For the Web form, name it the same PM_IW21_V1.

• The SAP server list users need access to for forms and workflows (since 12.1 Studio allows you to use your local list).
• Winshuttle roles (Bill will be a Central Application Administrator for one site and just a runner on another)
• Usage reporting is per site.
• Sharing simplification.
  • While libraries and to a lesser extent folders are valid options, they also introduce complications and limitations. I'm not sure about 12.1, but in 12.0, custom libraries do not show up in the menu and it greatly complicates the process of end users opening scripts and data templates. We've found that separating Foundation sites in such a way that users have a home and can default application settings and libraries is the best user experience.

• The SAP server list users need access to for forms and workflows (since 12.1 Studio allows you to use your local list).
• Winshuttle roles (Bill will be a Central Application Administrator for one site and just a runner on another)
• Usage reporting is per site.
• Sharing simplification.
  • While libraries and to a lesser extent folders are valid options, they also introduce complications and limitations. I'm not sure about 12.1, but in 12.0, custom libraries do not show up in the menu and it greatly complicates the process of end users opening scripts and data templates. We've found that separating Foundation sites in such a way that users have a home and can default application settings and libraries is the best user experience.