@extends('layouts.app')

@php
$target = config('app.funding.target_eur');
$collected = config('app.funding.collected_eur');
$period = config('app.funding.period');

$percent = ($collected / $target) * 100;
if ($percent == 0) $percent = 1; // make a bit of the green show up
@endphp

@section('content')
  <div class="container">
    <div class="row justify-content-center">
      <div class="col-md-8">
        <h1>Frequently Asked Questions</h1>

        <dl>
          <dt>How to report bugs?</dt>
          <dd>
            You can <a href="{{ config('app.href.feedback') }}">send us an e-mail</a>, or submit your issues to
            our <a href="{{ config('app.href.bugtracker') }}">bugtracker</a>.
          </dd>

          <dt>Can I donate?</dt>
          <dd>
            Donations are most welcome, please see our <a href="{{route('donate')}}">donations page</a>.
          </dd>

          <dt>Will there be...?</dt>
          <dd>
            The answer is likely yes, but keep in mind that this is a hobby project without any budget,
            so things tend to go slowly. You can check the <a href="{{ config('app.href.bugtracker') }}">bugtracker</a>
            for issues marked "TODO", those are planned features. You can also try to add a feature yourself, see below...
          </dd>

          <dt>Is datatable.directory open source?</dt>
          <dd>
            Yes. The upstream code is hosted at <a href="{{ config('app.href.git') }}">git.ondrovo.com/MightyPork/datatable.directory</a>,
            where you can register and submit issues, comments, and pull requests.
          </dd>

          <dt>How can I contribute?</dt>
          <dd>
            If you'd like to help with development, please head over to
            <a href="{{ config('app.href.git') }}">our git repository</a>.
            We welcome any improvements, ideas, or bug reports.
          </dd>

          <dt>I deleted my table, can I restore it?</dt>
          <dd>
            Tables can't be restored, but there is a chance that your table data could be, if you reach the admin
            quickly. If anyone made a fork of your table, you can also simply fork it back.
          </dd>

          <dt>I want to report something illegal / bad</dt>
          <dd>
            For now, please send us a <a href="{{ config('app.href.feedback') }}">feedback e-mail</a>.
            A built-in reports system will be added later.
          </dd>

          <dt>What technologies are used?</dt>
          <dd>
            <p>
              The server is written in <a href="http://php.net/">PHP</a> using the <a href="https://laravel.com/">Laravel</a> framework.
              The data is stored in a <a href="https://www.postgresql.org/">PostgreSQL</a> database.

              The front-end is based on <a href="https://getbootstrap.com/">Bootstrap 4</a>,
              including <a href="https://jquery.com/">jQuery Slim</a>, <a href="https://lodash.com/">lodash</a>,
              the <a href="https://github.com/axios/axios">axios</a> HTTP library,
              and the reactive JavaScript framework <a href="https://vuejs.org/">Vue</a>.
              We use <a href="https://webpack.js.org/">Webpack</a> to compile and minify JavaScript and <a href="https://sass-lang.com/">SCSS</a>.

              Most icons come from <a href="https://forkawesome.github.io/Fork-Awesome/">Fork Awesome</a>, using our
              <a href="https://git.ondrovo.com/MightyPork/fork-awesome-customizer">Fork Awesome customizer</a> to
              exclude unused icons.
            </p>
          </dd>

          <dt>How does it work?</dt>
          <dd>
            <p>
              It's complicated, and a great deal of thought went into the database design.
            </p>

            <p>
              A key thing to know is that table rows and revisions are immutable, and work in a way
              a bit similar to Git, except we don't actually use Git, it's all in the database.
              Rows and columns have unique IDs that ensure a change proposal (merge request) can be applied to any
              fork of a table, and in any revision.  A row change results in a new copy of the row being created,
              but maintaining the original row ID. Columns are, likewise, identified by their IDs; names are defined
              only in the revision object (a "header" of a table version), so changing a column name or order does not
              alter the row data in any way.
            </p>
          </dd>
        </dl>
    </div>
  </div>
@endsection