• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Developing a Documentation Portal on Heroku
 

Developing a Documentation Portal on Heroku

on

  • 242 views

 

Statistics

Views

Total Views
242
Views on SlideShare
242
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Developing a Documentation Portal on Heroku Developing a Documentation Portal on Heroku Presentation Transcript

    • Developing a Documentation Portalon HerokuSteve Anderson, salesforce.com, Information Architect@sanderson_sfdc
    • Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward- looking statements.
    • Even the Simplest UINeeds Documentation
    • Creating a Help SystemTakes Time Away FromYour Project
    • Let Us Do It For You!
    • Heroku Doc Portal
    • Hosted on Heroku
    • Written in Ruby
    • Contents stored inCouchDb
    • Search powered by Solr
    • Format controlled byoocss
    • Project available ongithub
    • Upload Your HTML, Add aTable of Contents Writtenin JSON, and You’reReady to Go
    • Demo
    • Let’s dig in
    • Keeping it simple Everything is done using RESTful HTTP actions
    • Sinatra• Domain Specific Language (DSL) for defining RESTful HTTP actions• Every time a user visits a URL, a Sinatra route is triggered• Each route returns something to the browser• The content returned can be • a HTML file from CouchDB, • a simple page defined using HAML, • a search results page that displays the SOLR data, or • a static page
    • A Simple Sinatra Route
    • A More Interesting Sinatra Route
    • Sinatra Supports Complex Routes
    • Views HAML (HTML Abstraction Markup Language ) is used to define the views
    • CouchDB for Content Storage• CouchDB is a document database• The data is saved in a semi-structured key/value store• Advantages of a document database for this project • The data isn’t restricted by a schema • Queries aren’t limited by the keys • Use views for powerful data access• Provided by Cloudant, CouchDB in the cloud• Integrated with the application using couchrest_model
    • Define the Model
    • Document in CouchDB
    • Views in CouchDB
    • Retrieve Using a View
    • Let’s Put It All Together
    • Solr for Search• Open source enterprise search platform from the Apache Lucene project. • full-text search • hit highlighting • faceted search• Powered by WebSolr, Solr in the Cloud• Integrated with the application using Sunspot
    • Solr Schema
    • Search with Solr
    • Search Flow
    • Look and feel - oocss• Oocss (Object-Oriented CSS) is a BSD licensed CSS framework• It’s very easy to swap in your own favorite CSS framework• https://github.com/stubbornella/oocss
    • Static Files• PDFs, images for your CSS, JavaScript, etc.• All are stored in the file system
    • What About the Table of Contents and SearchFacets?• Each topic has an associated JSON (JavaScript Object Notation) file stored in CouchDB.• The facets are in a static JSON file• They are displayed using Dynatree, a JQuery plugin
    • Steve AndersonInformation Architect, @sanderson_sfdc