Internal article for feature requests and issues

content/article/int-features.md

@@ -0,0 +1,74 @@
+---
+title: "Features Requests / Issues (INTERNAL)"
+date: "2023-07-11T17:48:22+03:00"
+author: "anybody"
+contributors: ["constantinos-miltiadis.md"] 
+draft: true 
+keywords:
+  - internal 
+  - journal management 
+  - feature requests
+abstract: |
+  (Internal) List of feature requests. 
+---
+
+# Introduction 
+
+Here we can list feature requests and issues for *Sandpoints*, or for this project in general. 
+After being discussed, issues and requests should be communicated to and discussed with the *Sandpoints* developers, ideally by filing an issue on the [Sandpoints repository](https://git.sandpoints.org/). 
+
+To contribute an issue or request make a new 
+
+# Feature requests
+
+## Expose item publication date (urgent)
+
+Expose publication date of published material so that citation/reference scrapers can see when was something published. 
+My experimental [Dotawo Zotero Translator](https://github.com/cmiltiadis/Dotawo-Journal-Zotero-Translator) cannot find any mention of a date. 
+
+- Issue posted on *Sandpoints* repository -- CM 06.2023. 
+
+## Fix Zotero collection (export) > Calibre (import) 
+
+Accorder (see ![Library management](article:int-library)), has a feature that allows reference collections exported via Zotero, to be imported into the (Calibre) library. This doesn't seem to work properly.
+
+- Marcell is currently developing this feature on the new version of accorder in Go lang -- CM 07.2023.  
+
+## Add option to sort orphan entries in Sitemap by type
+Currently, entries without parent (Print, Authors, Editors, etc.) appear in the [sitemap](/) sorted by creation date. It would be useful to have an option for sorting such orphan entries by type. For example, to have all Authors together, as well as Print entries and Editors appearing as grouped together.
+
+- Issue posted on *Sandpoints* repository -- CM 06.2023. 
+## Associate print with target item 
+
+Currently, to print something, one has to go to the [sitemap](/) and look if there is a `print` entity for the item they are interested in. 
+It would be useful, as in backlinks, to be able to have a button such as 'print this item'. 
+
+- Issue posted on *Sandpoints* repository -- CM 06.2023. 
+
+## Remove date from keywords perspective 
+
+If you click on any keyword, the new page shows all entries with that keyword. It ALSO shows the date these were created (in my case file creation date is part of the MD header). It would be great if these dates could be omitted.
+
+- Issue posted on *Sandpoints* repository -- CM 10.2022. 
+# Resolved 
+
+## Add background to code blocks 
+
+Code blocks are useful not only for code but also for Markdown formatting instructions, or terminal commands having to do with site maintenance. I would be useful to be able to more easily distinguish code blocks like blockquotes. At the moment, it's not easy to tell code blocks apart, or to distinguish them from text.  
+
+---
+
+Edited CSS file (`site.min.css`) to: 
+- introduce a background color for `code` (inline code blocks), and `pre` (multiline code blocks), which is only slightly darker than the blockquote background, 
+	- > this is a blockquote 
+	- `this is a codeblock (<code> css style)`
+- reduce the font size and add a border for multiline code blocks. The border color is the same(red) as the blockquote left-side border. The font size is scaled to 75%
+   ```
+   this is a multiline blockquote (<pre> css style)
+   ```
+
+Nevertheless: 
+- The actual background color, and padding should probably be reworked to fit better with the rest of the typesetting. 
+- Perhaps a 75% (or other) font size should be shared between `code` and `pre`
+
+Current changes are in commit `f405856fbd`  -- CM 11.07.2023.