How to add wiki pages to web-part page?

How to add wiki pages to web-part page?

Salve!  
EasyTabs works on a web-part page.
I want users to be able to create wizzywig pages with, say, the "create page" which creates a blank wiki page.
Then I want to use the web-part page that has EasyTabs on it to show those wiki pages in the web-parts there.  
Problem is, that the only way to get the wiki pages into the web-parts is through a web-part viewer, and when you do that, it displays all the site's title, ribbon and navigation inside the web-part.  
I tried a content-editor and linked to the page, but it displays the source instead of the page!
What can I do?  

Solutions/Answers:

Answer 1:

You can use a “Wiki Library” that houses wiki pages – in this library’s settings, there is a field called “wiki content” by which you can display the content without all the surrounding navigation.

Try the following:
Add the Wiki Web Part associated with your Wiki library, then Configure it to only display “Wiki content” and filtered for the name of the page you wanted to display. If you don’t filter by the page name, every wiki page in that library will be displayed. And if you don’t check the box for “wiki content” in the list settings, then you will get columns for “created by”, “title”, etc. like you would with a regular list.

This link is helpful.

Answer 2:

As far as easytabs goes, if you don’t want to use a wiki library, you can, instead, do a couple other things:

  • write out some simple html in a text editor, save the file as an html file, and upload it to your document library. Now you can reference the file with file-link via a content editor webpart. This will avoid any scrollbars which you would get with a web-page-viewer. You can keep and edit the original copies of these html files (complete with javascript and css in-page) on your local disk, and upload them programmatically using davcopy. The value to this method is that you can easily deal with your own css styles. If you are using a custom css file in your master page, then you can reuse the same styles throughout all of your site, and even in these html inserts. It isn’t so easy to use css styles (although you definitely can do it) in the wizzywig wiki pages because Sharepoint wants to style things it’s own way. But this method allows you to reuse your html inserts in other places.
  • Or, you can write your html directly into the content-editor webpart. Again, you can use styles and script there. This is fine as long as you don’t need to re-use the html.
  • Or, you can skip the html code and work wizzywig, just like in a wiki page – right in the content-editor webpart. This way there are no external pages, and no code nor links to mess with. And if you want script or css in the wizzywig code, you can always edit what you have written in the html markup of the content-editor webpart. If you want quick-and-easy text in easytabs, this is the way to go. It is really the equivalent of linking to wiki pages, except that you can’t really use them in more than one place (unless you don’t mind linking to your web-part-page that houses the content-editor webpart).

I already accepted saumilm’s answer because my original question was how to add wiki pages to easytabs, and he answered that question. But this here answer is what really solved my issue.

References

How to automatically convert the word document into PDF?

How to automatically convert the word document into PDF?

Is there any workflow that I can create to convert a word document into PDF after the approval workflow is finished. 

Solutions/Answers:

Answer 1:

I have not seen anyone create a workflow capable of converting word files to PDF out of the box, but i have seen third party solutions that enable workflow features like this in SharePoint.

read this link, http://blog.muhimbi.com/2012/02/convert-document-types-using-pdf.html

Answer 2:

There is a custom action for workflows capable of that using Word Automation Service.

http://sp2010wordautomation.codeplex.com/

Answer 3:

You could try Kaboodle Renditions at http://www.kaboodlekonnect.com/renditions. The Converter module can be configured to create a PDF (or other format such as XPS, TIFF, ePub etc.) automatically when a major version of a Word document is published.

So if the final step in your approval workflow publishes a major version then the conversion just happens. The beauty is that the PDF can be saved anywhere i.e. it can be in the same web or site collection but it could equally be a in a library in a remote SharePoint farm or even SharePoint online. And you can send metadata as well.

I should add that I work for Kaboodle Software, but don’t let that put you off.

References