Opened 14 years ago
Last modified 14 years ago
#16 closed defect (FIXED)
beardomatic chapter in docs
Reported by: | Will Kahn-Greene | Owned by: | Will Kahn-Greene |
---|---|---|---|
Priority: | minor | Milestone: | 0.0.1 |
Component: | Keywords: | ||
Cc: | Parent Tickets: |
Description
Chris is tentatively calling the stack we're using Beardomatic. This stack needs some documentation to make it a lot easier to work with for existing and new contributors. This documentation would include the following: 1. the components in the software stack 2. how to create a new view 3. how to add something to the database 4. ... Adding Chris to the watcher list so he can expound on the above list. We currently have a "softwarestack" chapter. I think we should rework that into a Beardomatic chapter and cover all the other things in there.
Change History (5)
comment:2 by , 14 years ago
I just pushed some updates. I converted the softwarestack chapter into a chapter on beardomatic complete with explanation of what the hell we're talking about when we say "beardomatic". It includes the software stack in a slightly more hierarchical list so it's "clearer" where the components are in relation to things. I added a "How to ..." section stub, but there's nothing there, yet. I think this can wait until post-0.0.1.
comment:4 by , 14 years ago
Status: | New → Closed |
---|
Switched this to be codedocs. We should add some recipes for how to do things, but I think we should make a new issue for that and close this one out.
Note:
See TracTickets
for help on using tickets.