I realized a simple interface for my sub SharePoint site. but I have no idea how I download my files Interface (Javasript, css, html) that index.html becomes my homepage on my website .
best regards
Upload all files to a document library, then use SharePoint Designer to set index.html as the home page.
http://www.learningsharepoint.com/2013/09/05/how-to-set-a-page-as-home-page-in-sharepoint-2013-site/
Edit: If you want SharePoint functionality, then you need to do what we all do: Use a SharePoint page and customize it to show/hide what you want to see. In many cases, custom CSS can be used to hide unwanted SharePoint elements. Custom HTML can be applied by editing an individual page.
Second edit: It seems that you have very sparse understanding of SharePoint and what it can do. You need to learn how SharePoint works. It's way more than just html and it's WAAAAY more than can be posted in an answer here. No way around that. Get clued up about what SharePoint does before you do things with it that it does not do naturally.
Related
by Default there are Themes, I don't Like those. How can I modify It completely and make a professional website. I have found same Questions on this blog but all for MOSS2007. I am working on Sharepoint 2010
The way I modify sharepoint, is as I do with almost every other CMS out there combined with the power of asp .Net (Remember that as CMS' go sharepoint is a poor solution if the only thing you want is a portal. Sharepoint is first and foremost a BI Solution).
When you edit your site in sharepoint designer (Site Action -> Edit in sharepoint designer) you can see a whole lot of options.
Here you can change the default masterpage to accomodate the look and feel of your site. You will do most of the hiding stuff here (those you don't want to be seen giving them the visibility=false attribute). Here you can also include a new CSS (place it in site assets) where you can override already existing css files.
From this point on, you will be able to add web pages to the site, that will conform to the masterpage, and thus you can use all the sharepoint power (web parts and even embedded html code) keeping the look and feel you have implemented on your master page.
So what you need to do is:
Modify master page in sharepoint designer
Add css files in site assets and include them in your masterpage
Add any other aspx pages or custom web parts that you will refer to in the sharepoint site
Create web pages with sharepoint assets, web parts or custom code
Enable anonymous access for the people you want to view your portal without authenticating (Bear in mind that there are some sharepoint controls that can only be viewed by logged in users)
There are multiple ways of customizing it.
My perfered way is CSS.
Add reference to a custom css in master page using feature
Modify the look and feel by modifying sharepoint out-of-box CSS
Following resources gives all the details of SharePoint 2010 css classes.
http://sp2010notes.wordpress.com/sharepoint-2010-css-chart/
http://sharepointexperience.com/csschart/csschart.html
I hope it helps.
Cheers.
Rajendra Shekhawat
I have developed a publishing portal in sharepoint.I have a requirement wherein I need to create sitemap for the entire web application.
This should be dynamic, in the sense, whenever we update the contents of any given page in our web application, it should be reflected immediately in the sitemap page. What are the possible ways to achieve this and which is the best possible solution considering the scalability and easy configuration?
Thank you.
If you don't want to use a custom webpart, you could use normal navigation list to create your sitemap and it is automatically updated. You only need to style it in a way to resemble some kind of sitemap.
Here are some links to get you started with customizing your navigation:
Custom Navigation in SharePoint - The Full Monty
How to: Customize Navigation
Also there is the portal site map which provides the data source for your custom menu. Just read up on custom navigation and stuff like PublishingNavigation:PortalSiteMapDataSource and SharePoint:AspMenu.
There is a nice PowerShell script to create a sitemap for SHarepoint 2010, if you want to submit your sitemap to Google: Generate A Sitemap For SharePoint 2010 Using PowerShell'.
You can also install and customize the SharePoint Web part ("Table of Contents") to your liking. Read up on it here...
Take a look at our ECS product, it is close to what you need
http://www.infowisesolutions.com/product.aspx?id=ECS
It was built as a system of cross site collection navigation, with security trimming and permissions inheritance between site collection.
I'm trying to replace the navigation on our sharepoint site with a treeview. It's a large site with up to 4 subsite leves in places. All I need it to do is
show a consistent structure from page to page
show only sites and pages
The default sharepoint treeview seems to do neither of these things (doesn't display items from the parent site, includes document libraries but not pages).
Does anyone have any idea how to achieve this? We're using the publishing site template throughout if that makes a difference.
I've tried binding the tree to the datasource the quick launch uses but I guess from the error message they expect differently named properties.
You cannot do it using the default property of sharepoint.
But I had also almost the same requirement. I did this task by the following way
Store all the links in an XML file.
Create a webpart for reading XML file and create menu
Open the masterpage using sharepoint designer and comment the lines which render the top navigation and place the new webpart there
Inherit this masterpage in its subsite.
For multi level quick launch the below link will help you
http://blogs.msdn.com/sharepoint/archive/2007/04/26/customizing-the-quick-launch-menu-adding-fly-out-menus-to-sharepoint-navigation.aspx
If you want more help, pls ask me, I can help you
I've started using MOSS 2007's wiki feature for storing the ongoing technical documentation related to a project I'm working on, and it occurred to me after I started writing a few pages that there's no easy way to export out all of the pages into one document.
For those of you familiar with MOSS 2007, any ideas how this might be accomplished?
In the past I've created a site feature that exports SharePoint content to PDF and HTML but that was for publishing sites. I assume it needs some rewriting to make it working with the Wiki.
It basically iterates through the navigation of a site and all it's sub sites and reads all the pages stored in the "pages" document library. For each page it then extracts the content using XSLT.
Let me know whether I shall make the source somewhere available.
Cheers,
Michael
You should be able to create a view that shows the content for all of the wiki articles. It's not pretty; you'll get one really long web page. I don't have sharepoint up and running right now to tell you the exact steps, but I have done it before.
BlueRidge has an extension that allows you to export to PDF, but at 640+ euro it's a tad pricey.
You could copy/paste your content into your desired document. It's not convenient but it is a potential work around.
I am also after a solution for this. We have a multilevel Wiki content that follows a levelling structures. Can we automatically export the MOSS Wiki content to a more structured database such as Excel, Access, or XML?
I'm reasonably new to SharePoint 2007 and trying to move from an ASP.NET to SharePoint way of thinking has been an interesting experience!
I would like to create a page at the same level as the default.aspx page in a subsite. The "SharePoint way" of doing things involves putting the page into a document library. I am reluctant to do this as the breadcrumb navigation of the page then includes the name of the libarary but I would like the library to be transparent to the user.
I can create a page in the right place in SharePoint designer but I can't find a way to use a SharePoint template. I have tried copying the default.aspx page, but the navigation linkes are not updated.
Am I missing something or can someone suggest a solution?
I see what you are saying. I would like to share my thoughts on how I will do it.
If the Breadcrumb is your only reason why you want to move to a different than lib, the I recommend you to override the ContentPlaceholder that has the BreadCrumb in your Page, so that BreadCrumb wont be there. But URL will be there for the User to Guess ./DocLib/default.aspx.
And if the reason to hide the document library is to make sure that you don't want to allow the user to get into the Lib and change something. I recommend you strip out the permission from the Document Lib and give all the user ReadOnly and add the user with more right who you thing will need to edit the pages.
And finally you wanted to it in a Place, you can try deploying them as a Feature that will provision the pages as Ghostable rather then GhostableInLibray.
While 1,3 cab be packaged in a WSP. 2 one needs bit of a Manual / custom Code if you are trying to automate the process.
Steps to create Ghostable pages you can refer to this
It doesn't seem to be possible. Subsites can be used to be categorise content by topic, but they can't be used very much.