Like the google one, it didn't involve writing any JavaScript. I just had to specify the name of the css file in the metadata.
Google tries to get developers to put their extensions, no matter how trivial, in the Chrome Web Store. Apple, on the other hand, requires developers to sign up for the Safari Developer Program, get a digital certificate, and sign their extensions. Apple does have a Safari Extension Gallery, but their approach is different:
> Safari Developer Program members can submit their Safari extensions to be considered for the Safari Extensions Gallery.
https://github.com/benatkin/quietgsearch
Like the google one, it didn't involve writing any JavaScript. I just had to specify the name of the css file in the metadata.
Google tries to get developers to put their extensions, no matter how trivial, in the Chrome Web Store. Apple, on the other hand, requires developers to sign up for the Safari Developer Program, get a digital certificate, and sign their extensions. Apple does have a Safari Extension Gallery, but their approach is different:
> Safari Developer Program members can submit their Safari extensions to be considered for the Safari Extensions Gallery.