Using Atlassian cloud you are limited.. You would need to disable addons via the Dashboard Macro list which only Atlassian can do. Though this reflect across Confluence for everyone so probably not ideal.
You maybe better of creating a page and configuring that and make that the default landing page, after enabling Anonymous access via global permissions and then allowing public access to that space via the space permissions. It will not matter if you have several public facing spaces as you will have enabled a space via Confluence Administration > Further Administration and edit via a select list. Though it will display the landing/home page of that space. If you don't want anyone to access anything underneath, page restrictions should be added = painful.
You could possibly put a script in the look and feel section within space admin to hide macros etc but I've only managed in the past through a need of a client to hide and put macros into side bar, but not sure if it can be made to be clever so that it will check for user access so that users can see and anonymous users cannot to keep the stuff you want above in for internal users..
Hello Community, Jessica here from the Confluence product marketing team! Today I wanted to get your takes on project planning –– what works, what doesn’t, how do you know if you’re doing it r...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs