0
Apps: Start to Finish Building an App for Drupal 7 Distributions
Who’s Here  Karen Borchert    Jay Callicott Product Director    DeveloperPhase2 Technology   Mediacurrent
Today’s GoalShow how Mediacurrent built an Eventsapp for the OpenPublic distribution.
What is an app?The Apps module wraps a     layer ofusability (discoverability, installation,  configuration, demo content) ...
Are Apps &Features thesame thing?
Why Apps for Distros?➡   Keeps distributions lighter➡   Provides specific functionality for    specific use cases➡   Allows ...
Five Big Steps:    1. Plan    2. Build    3. Package    4. Submit it    5. Go Live
PLAN.
An app identifies adistinct problem fora specific audience,    and solves it    completely.
1. What ProblemAre You Solving?
Problem➡   Most public institutions have events➡   Institutions need a way to publicize    information about events in a w...
2. Who is this   app for?
AudiencePublic institutions...➡   Nonprofit organizations➡   Government agencies➡   Government departments...who regularly ...
3. How will this app     be used?
Use Case: Public Institution➡   Institution has an event to publicize.➡   Site administrator creates an event:➡    where➡ ...
4. Whichdistribution is it for?
Which Distribution?
Checklist #1✓ Does it solve a specific, discrete problem?✓ Does it solve a problem for a specific   audience?✓ Does it solve...
“with new Events App by@mediacurrent, public sector orgsnow have a way to publicize events on @OpenPublic with calendar an...
BUILD.
5. What are the components?
Modules Used    Existing:➡   Address Field➡   Views 3x    New:➡   None needed
6. Can we  contributeanything back?
Anything to Contribute?➡   This solution relies on only contributed    modules➡   The apps, features themselves are    ope...
7. Which pieces dowe need to build?
Components to Build➡   Event content type➡   Events view➡   A little css
8. Ok, Build it!
Checklist #2✓ Did you seek out existing modules?✓ Did you contribute back new modules   to Drupal.org?✓ Is it kit complian...
PACKAGE.
9. Gather the Assets
Manifest.appLogo               Screenshot
openpublic_event.info
10. Buildconfiguration page
11. Build the default      content
12. Test it!
Testing Procedure➡   Load a fresh database (Drop old one    first)➡   Remove everything from modules    directory except yo...
Checklist #3✓ Does the app install?✓ Can you configure the app?✓ Can you turn on and off default  content?✓ Can you uninsta...
SUBMIT IT.
13. Put itsomewhere
Mediacurrent Feature Server
14. Submit App
What We Sent:Zipped file with:➡   Manifest.app file➡   Images
How does a distro owner  decide which apps?      ✓ Sound Architecture      ✓ Stable Construction      ✓ Reliable Performan...
GO LIVE!
Get Started➡   Download OpenPublic Beta3➡   Check out documentation on    community.openpublicapp.com➡   Contact the OpenP...
Apps: Start to Finish
Apps: Start to Finish
Apps: Start to Finish
Apps: Start to Finish
Apps: Start to Finish
Apps: Start to Finish
Upcoming SlideShare
Loading in...5
×

Apps: Start to Finish

926

Published on

Presented by Product Director Karen Borchert from Phase2 Technology and Senior Developer Jay Callicot with Mediacurrent at DrupalCamp Atlanta. This presentation walk you through the five stages of building an app for Drupal.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
926
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript of "Apps: Start to Finish"

    1. 1. Apps: Start to Finish Building an App for Drupal 7 Distributions
    2. 2. Who’s Here Karen Borchert Jay Callicott Product Director DeveloperPhase2 Technology Mediacurrent
    3. 3. Today’s GoalShow how Mediacurrent built an Eventsapp for the OpenPublic distribution.
    4. 4. What is an app?The Apps module wraps a layer ofusability (discoverability, installation, configuration, demo content) aroundexisting Drupal functionality.
    5. 5. Are Apps &Features thesame thing?
    6. 6. Why Apps for Distros?➡ Keeps distributions lighter➡ Provides specific functionality for specific use cases➡ Allows for multiple third party solutions, rather than giving preference to one
    7. 7. Five Big Steps: 1. Plan 2. Build 3. Package 4. Submit it 5. Go Live
    8. 8. PLAN.
    9. 9. An app identifies adistinct problem fora specific audience, and solves it completely.
    10. 10. 1. What ProblemAre You Solving?
    11. 11. Problem➡ Most public institutions have events➡ Institutions need a way to publicize information about events in a way that is accessible to the public on their web site➡ OpenPublic does not accomplish this “out of the box”
    12. 12. 2. Who is this app for?
    13. 13. AudiencePublic institutions...➡ Nonprofit organizations➡ Government agencies➡ Government departments...who regularly hold events and want toinform the public about them.
    14. 14. 3. How will this app be used?
    15. 15. Use Case: Public Institution➡ Institution has an event to publicize.➡ Site administrator creates an event:➡ where➡ when➡ description➡ who➡ Event Appears on calendar.
    16. 16. 4. Whichdistribution is it for?
    17. 17. Which Distribution?
    18. 18. Checklist #1✓ Does it solve a specific, discrete problem?✓ Does it solve a problem for a specific audience?✓ Does it solve the problem completely?✓ Can you tweet it? (describe it in 140 characters or less)
    19. 19. “with new Events App by@mediacurrent, public sector orgsnow have a way to publicize events on @OpenPublic with calendar and events listings.”
    20. 20. BUILD.
    21. 21. 5. What are the components?
    22. 22. Modules Used Existing:➡ Address Field➡ Views 3x New:➡ None needed
    23. 23. 6. Can we contributeanything back?
    24. 24. Anything to Contribute?➡ This solution relies on only contributed modules➡ The apps, features themselves are open source
    25. 25. 7. Which pieces dowe need to build?
    26. 26. Components to Build➡ Event content type➡ Events view➡ A little css
    27. 27. 8. Ok, Build it!
    28. 28. Checklist #2✓ Did you seek out existing modules?✓ Did you contribute back new modules to Drupal.org?✓ Is it kit compliant?✓ Does it address the defined use cases?
    29. 29. PACKAGE.
    30. 30. 9. Gather the Assets
    31. 31. Manifest.appLogo Screenshot
    32. 32. openpublic_event.info
    33. 33. 10. Buildconfiguration page
    34. 34. 11. Build the default content
    35. 35. 12. Test it!
    36. 36. Testing Procedure➡ Load a fresh database (Drop old one first)➡ Remove everything from modules directory except your app➡ Have “Development server”enabled➡ Remove everything from temp directory / update-*
    37. 37. Checklist #3✓ Does the app install?✓ Can you configure the app?✓ Can you turn on and off default content?✓ Can you uninstall it?✓ Does it show up everywhere its supposed to on installation, and disappear as needed on uninstall?
    38. 38. SUBMIT IT.
    39. 39. 13. Put itsomewhere
    40. 40. Mediacurrent Feature Server
    41. 41. 14. Submit App
    42. 42. What We Sent:Zipped file with:➡ Manifest.app file➡ Images
    43. 43. How does a distro owner decide which apps? ✓ Sound Architecture ✓ Stable Construction ✓ Reliable Performance ✓ Compliance ✓ Open App Standard
    44. 44. GO LIVE!
    45. 45. Get Started➡ Download OpenPublic Beta3➡ Check out documentation on community.openpublicapp.com➡ Contact the OpenPublic and/or OpenPublish team at Phase2
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×