Совместное место для поставки изображений и файлов CSS

sharepoint.stackexchange https://sharepoint.stackexchange.com//questions/39707

  •  09-12-2019
  •  | 
  •  

Вопрос

Я смотрел на сеть для некоторых советов и объяснения, где размещать свои пользовательские CSS и изображения для главной страницы в SharePoint 2010. Я сейчас занят брендией портала, и я немного запутался, где файлы CSS и изображения должны идти.

У меня есть несколько вариантов, либо я помещаю файлы в сам портал в библиотеке стилей (библиотека документов) или же Я положил их в улье (конечно, с решением) И если в улите в каком каталоге именно? 1033 / Стили?(Если в этом я бы очень хотел знать, почему?, почему 1033?) /Изображений? Другое место?

Конечно, я могу поставить мои файлы, когда я хочу, но я предпочел бы услышать лучшую практику (лучшее место, обычный способ сделать это).

Это было полезно?

Решение

If you want a super user to be able to change logos etc, or if the logo is specific to a site collection, place them in a subfolder in /Style Library/Images/.

However often you dont want the layout files of your page, or your CSS for that matter, to be changed by end users. This is a good reason to place them somewhere in the v\TEMPLATE\LAYOUTSfolder. These files are also available across all site collections in the farm as/_LAYOUTS`.

Exactly where under LAYOUTS really depends... If they should be able to change depending on language, you should place them under each language in LAYOUTS\<LCID>\IMAGES\yourSubDir or LAYOUTS\<LCID>\STYLES\yourSubDir (you will have one folder for each language pack you have installed).

When inserting CSS use the <Sharepoint:CSSRegistration ../> web control in the master page, SharePoint will pick the relevant localized CSS file depending on the language selected by site owner or user (see my blog post for more info) and possible caveats. This will also make sure that your CSS file is not cached when it is changed.

SharePoint libraries in general have "issues" with max-age header, which would cause excessive requests to the server even though page is cached

As you state, you can put them anywhere you want, and as you can see the answer (as usual with SharePoint is "it depends"). It is not the first time we discuss this either. Check similar question here.

On a final note, they way the files end up where they do is important too! You should always use Solutions and if needed Features to provision the files no matter where you decide to stick them!

EDIT: Files that should be published in a SharePoint library must be published using a Module element in a feature. Here you want to set it to be GhostableInLibrary. Example:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <Module Name="MyWelcomePageTemplate" Url="$Resources:osrvcore,List_Pages_UrlName;" Path="MyWelcomePageTemplate">
    <File Url="default.aspx" Type="GhostableInLibrary">
      <Property Name="Title" Value="My page" />
      <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/MyPageLayout.aspx, $Resources:cmscore,PageLayout_WelcomeLinks_Title;" />
      <Property Name="ContentType" Value="MyContentType" />
    </File>
  </Module>
</Elements>

On the other hand you include LAYOUT files using Mapped Folders (directly to SharePointRoot or LAYOUT depends on your preference) that automatically is added as <RootFile ..> elements in your package/solution

Другие советы

I believe you should put all the branding design stuff in the Style Library. The 1033/Styles folder is for custom development css file.

Find out more here

Why 1033? It is Decimal Language Code for English - United States. So if you have style/images/resources that target a different language you should use the appropriate language code.

Personally I would not use the ..Styles/ ..Images/etc folders directly but I would use a subfolder in them (i.e. 1033/Styles/MyProject or 1033/Images/MyCompany). This way you can easily find your custom files in the 12 hive.

Лицензировано под: CC-BY-SA с атрибуция
Не связан с sharepoint.stackexchange
scroll top