Remove complete implementation

2023-09-17T09:07:08Z

Restarting from scratch seems to be the fastest approach to switch to sqlite and get rid of some other structural mistakes from the past.

index.html: Remove autofocus to search field

2023-05-07T08:36:27Z

This is useful for desktops but is annoying on mobile devices since a touchscreen keyboard is overlayed automatically and hides half of the index page.

Implement ingredient summary

2023-05-01T17:20:43Z

Show link just if not empty

2023-05-01T16:15:21Z

Otherwise this is confusing.

Switch to tripel to describe ingredients

2023-05-01T16:07:55Z

It is always the same: - amount float32 - unit string - type string This is good as a starting point. Later the types of ingredients might have to be tracked. In this a string as key is maybe not the best.

Focus search input on index page load

2023-04-28T15:22:59Z

This allows the user to start typing without clicking into the input field.

Implement search bar on index page

2023-04-28T14:53:10Z

This is way it is way easier to filter recipes by name.

Replace JavaScript on edit page by form

2023-04-23T20:01:50Z

This is actually possible when using

instead of <pre>. With
this change the recipe server has full support for browsers without
JavaScript.
</article>
<article>
<h1>Move delete button from edit page to recipe page</h1>
<p>2023-04-22T18:30:46Z</p>
This reduces the number of clicks to delete a recipe.
</article>
<article>
<h1>Update edit page</h1>
<p>2023-04-22T18:28:54Z</p>

</article>
<article>
<h1>Use <section> elements for recipe steps</h1>
<p>2023-04-22T18:09:48Z</p>

</article>
<article>
<h1>Improve representation of step ingredients</h1>
<p>2023-04-22T17:57:44Z</p>

</article>
<article>
<h1>Implement basic recipe target with JSON</h1>
<p>2023-04-22T15:54:57Z</p>

</article>
<article>
<h1>Fix layout on delete confirmation page</h1>
<p>2023-04-08T20:15:06Z</p>

</article>
<article>
<h1>Fix links</h1>
<p>2023-04-08T20:13:03Z</p>

</article>
<article>
<h1>Switch from MariaDB to files</h1>
<p>2023-04-02T19:52:10Z</p>
Using a database is way more complex (see the commit statistics of this
commit) than using files to store recipe data. Also administration and
usage is simpler.
</article>
<article>
<h1>Improve user interface</h1>
<p>2023-04-01T16:37:47Z</p>

</article>
<article>
<h1>Implement recipe deletion</h1>
<p>2023-04-01T16:21:27Z</p>

</article>
<article>
<h1>Make Markdown editable</h1>
<p>2023-04-01T13:20:46Z</p>

</article>
<article>
<h1>Reduce to ID and Markdown</h1>
<p>2023-03-31T19:46:53Z</p>
The upstream URL can be encoded easily by the user in the Markdown-based
description. The title can be parsed by the first found top-level
heading in the Markdown text.

Thus these two columns are no longer used. To avoid an additional
migration they will be kept in the database.
</article>
<article>
<h1>Remove image functionality</h1>
<p>2023-03-31T17:47:55Z</p>
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
</article>
<article>
<h1>Rework edit page dummy</h1>
<p>2023-03-07T17:08:00Z</p>
Since there are no good solutions to upload the file and markdown
description text via HTML forms the edit page will upload the changes
using embedded javascript.

The page is now complete apart from the necessary javascript code and
the backend handlers.
</article>
<article>
<h1>Update navigation links</h1>
<p>2023-03-07T16:27:14Z</p>

</article>
<article>
<h1>Make add.html a template</h1>
<p>2023-02-12T18:46:48Z</p>
This allows to use partial HTML files via Go's templating features.
</article>
<article>
<h1>Move footer to own template file</h1>
<p>2023-02-12T18:40:49Z</p>

</article>
<article>
<h1>Move <head/> section to own template file</h1>
<p>2023-02-12T18:33:49Z</p>
This reduces copies of the same HTML code.
</article>
<article>
<h1>Add new recipe edit page</h1>
<p>2023-02-08T19:44:02Z</p>
Recipes should be completely editable and removable. Thus this edit page
was added.
</article>
<article>
<h1>Switch to simple.css</h1>
<p>2023-01-11T19:51:13Z</p>
This makes it easier to maintain and it looks better.
</article>
<article>
<h1>Add existing work</h1>
<p>2022-11-07T20:17:44Z</p>

</article>
</main></body></html>

ceres/data/templates, branch v0.5.0