Changeset - 45904d4a25a2
[Not reviewed]
0 4 0
Bradley Kuhn (bkuhn) - 8 years ago 2013-11-14 17:50:48
bkuhn@ebb.org
Don't put any text in the <a> with only id so that the class isn't need in CSS.

<joar> you should change it to <a id="foo"></a>Generating reports
<joar> so, just create an empty <a> tag before the anchor target
<bkuhn> is that really the "right way" to do it?
<joar> it's the generally accepted way
<bkuhn> oh, ok.
<joar> it's the way sphinx does it, for example
<joar> I think wikipedia does the same
4 files changed with 8 insertions and 11 deletions:
0 comments (0 inline, 0 general)
UseCases/Collaborating.mdwn
Show inline comments
 
As an accountant that collaborates with other accountants I need:
 

	
 

	
 
- <a class="idOnly" id="simultaneous-ledger-edits">Simultaneous editing of the same ledger</a>
 
- <a id="simultaneous-ledger-edits"></a>Simultaneous editing of the same ledger
 
- FIXME: this should probably be stated differently: In the case of decentralized ledgers, such as ledger-cli files shared via DVCS
 
  - Easy synchronization of entries from separate ledgers
 

	
 
in order to efficiently and collaboratively perform accounting tasks.
UseCases/GeneratingReports.mdwn
Show inline comments
...
 
@@ -2,16 +2,16 @@ As an US-based NPO I need a way to *generate reports* in order to:
 

	
 
- Send the reports to an auditor
 
- Forward them to organization members.
 

	
 
The usual reports an NPO is expected to generate, and all of these should be generatable for any given date period:
 

	
 
- <a class="idOnly" id="trial-balance"></a>[Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
 
- <a class="idOnly" id="bank-reconciliation"></a> [Bank Reconciliation Report](http://en.wikipedia.org/wiki/Bank_reconciliation)
 
- <a id="trial-balance"></a>[Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
 
- <a id="bank-reconciliation"></a> [Bank Reconciliation Report](http://en.wikipedia.org/wiki/Bank_reconciliation)
 
    + This report often needs to be generated with input from the user, since [the subset sum problem](http://en.wikipedia.org/wiki/Subset_sum_problem) is [NP-complete](http://en.wikipedia.org/wiki/NP-complete), human intervention is often needed to identify the specific transactions to show on this report.
 
-  <a class="idOnly" id="chart-of-accounts"></a> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
 
-  <a class="idOnly" id="cash-disbursements">Cash Disbursements Journal</a>
 
- <a class="idOnly" id="income-report">Income Report</a> (just a list/sum of all Income accounts for a period)
 
- <a class="idOnly" id="expenses-report">Expenses Report</a>  (just a list/sum of all Expenses accounts for a period)
 
-  <a id="chart-of-accounts"></a> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
 
-  <a id="cash-disbursements"></a>Cash Disbursements Journal
 
- <a id="income-report"></a>Income Report (just a list/sum of all Income accounts for a period)
 
- <a id="expenses-report"></a>Expenses Report  (just a list/sum of all Expenses accounts for a period)
 
- [[Fund Report|UseCases/FundAccounting#FundReport]]
 

	
 
Also, To handle [[UseCases/FundAccounting]] all of these reports should be generatable narrowed to specific funds.
UseCases/WorkFlow.mdwn
Show inline comments
...
 
@@ -2,13 +2,13 @@
 

	
 
Many accounting systems seem to assume that the workflow fits a certain type
 
of uses.  While the ability to impose a specific workflow (e.g., for a
 
bookkeeper who might make an error easily if the system doesn't require a
 
workflow), the  workflow should not be dictated.
 

	
 
## <a class="idOnly" id="unaccrued-invoice">The "Unaccrued Invoice" Example</a>
 
## <a id="unaccrued-invoice"></a>The "Unaccrued Invoice" Example
 

	
 

	
 
The easiest example I have of this relates to accruing income upon invoice
 
generation.  Non-profits very typically generate invoices as part of a
 
fundraising discussion *even though* the non-profit doesn't have a good faith
 
belief that the invoice will be paid.  Using an invoice to convince a donor
local.css
Show inline comments
...
 
@@ -24,9 +24,6 @@ footer {
 
.npoacct-navbar .createlink a:focus,
 
.npoacct-navbar .createlink a:active,
 
.npoacct-navbar .createlink a:hover,
 
.npoacct-navbar .createlink a {
 
  color: #ce1f1f;
 
}
 
a.idOnly {
 
text-decoration: none !important;
 
}
...
 
\ No newline at end of file
0 comments (0 inline, 0 general)