New: Sharing articles from the article title line

[math-GH]

It adds a column for sharing articles directly in the normal view article row

config via display config (default: not selected)

Pull request checklist:

• clear commit messages
• code manually tested

[math-GH]

The reading view is untouched yet. It will prevent conflicts with #6297. Sharing will be added later.

[Alkarex]

I like the idea, but I would like to suggest a more powerful solution: make a menu from the title line as you have, but allowing multiple functions, the sharing one being a sub-menu.
Examples of functions (which can be added in other PRs) include: mark previous articles as read, reload full content, search similar articles, etc.

[Alkarex]

Implementation consideration: this adds a lot of data in the output (consume resources server side, at network level, and client side) for a non-essential shortcut feature. To save resources and improve performances, I think this should be left to a dynamically-generated menu like we have for the configuration drop-down menu of the feeds in the aside bar.

Example:

FreshRSS/app/layout/aside_feed.phtml

Lines 153 to 189 in 329fd4b

	<script id="tag_config_template" type="text/html">
	<ul class="dropdown-menu">
	<li class="item">
	<a class="configure open-slider" href="<?= _url('tag', 'update', 'id', '------') ?>"><?= _t('gen.action.manage') ?></a>
	</li>
	</ul>
	<a class="dropdown-close" href="#close">❌</a>
	</script>
	<script id="feed_config_template" type="text/html">
	<ul class="dropdown-menu">
	<li class="item"><a href="<?= _url('index', $actual_view, 'get', 'f_------') ?>"><?= _t('gen.action.filter') ?></a></li>
	<?php if (FreshRSS_Auth::hasAccess()) { ?>
	<li class="item"><a href="<?= _url('stats', 'repartition', 'id', '------') ?>"><?= _t('index.menu.stats') ?></a></li>
	<?php } ?>
	<li class="item link website"><a target="_blank" rel="noreferrer" href="http://example.net/"><?= _t('gen.action.see_website') ?></a></li>
	<?php if (FreshRSS_Auth::hasAccess()) {
	$get = Minz_Request::paramString('get');
	if ($get === '') {
	$url = _url('subscription', 'feed', 'id', '------', 'from', $actual_view);
	} else {
	$url = _url('subscription', 'feed', 'id', '------', 'get', $get, 'from', $actual_view);
	}
	?>
	<li class="item"><a class="configure open-slider" href="<?= $url ?>"><?= _t('gen.action.manage') ?></a></li>
	<li class="item"><a href="<?= _url('feed', 'actualize', 'id', '------') ?>"><?= _t('gen.action.actualize') ?></a></li>
	<li class="item">
	<?php $confirm = FreshRSS_Context::userConf()->reading_confirm ? 'confirm" disabled="disabled' : ''; ?>
	<button class="read_all as-link <?= $confirm ?>"
	form="mark-read-aside"
	formaction="<?= _url('entry', 'read', 'get', 'f_------') ?>"
	type="submit"><?= _t('index.menu.mark_feed_read') ?></button>
	</li>
	<?php } ?>
	</ul>
	<a class="dropdown-close" href="#close">❌</a>
	</script>

Or (probably even better) use an HTML template element https://developer.mozilla.org/docs/Web/HTML/Element/template like:

FreshRSS/app/views/configure/integration.phtml

Lines 15 to 31 in 329fd4b

	<template id="simple-share">
	<fieldset class="group-share dragbox">
	<legend draggable="true">##label##</legend>
	<input type="hidden" id="share_##key##_type" name="share[##key##][type]" value="##type##" data-leave-validation="" />
	<div class="form-group" id="group-share-##key##">
	<label class="group-name" for="share_##key##_name"><?= _t('conf.sharing.share_name') ?></label>
	<div class="group-controls">
	<input type="text" id="share_##key##_name" name="share[##key##][name]" value="##label##" />
	</div>
	</div>
	<div class="form-group">
	<div class="group-controls">
	<button type="button" class="remove btn btn-attention" title="<?= _t('conf.sharing.remove') ?>"><?= _t('gen.action.remove') ?></button>
	</div>
	</div>
	</fieldset>
	</template>

[math-GH]

@Alkarex Thanks for your feedback.

Let me explain my roadmap that I have in mind:
General idea is to have the features "sharing" and "my labels" in the header too. It is not a good UX to have both just in the footer. The options are already there in the table "article actions" (as disabled checkboxes). Let the users decide if they need it or not. If the user does not need it it will not have an HTML overhead. If the user decides to have this option in the header and not in the footer anymore: plus minus zero overhead ;)
If the user decides to have the sharing menu in the header and disable other buttons (f.e. the reading icon and the "open on website" icon), then there is enough space.

TODO: I was thinking to use the templates too, because this menu is created in each article (also before this PR). I wanted to do this refactoring after this PR to keep focus on this feature and do not mix it with the refactoring of the existing sharing menu.

The submenu thing: yes, I am thinking about it too, but there is some more brain power needed ;) Right now the code does not have any sub menu features. A sub menu needs one more click/interaction than just a button (I can remember some discussion about having 1 more click to more-or-less important features). I think it will be important to have this sub menu feature and more features as you described. We could play here with CSS container queries too, so that it is usable on small and big screens.

My roadmap in bullet points to summarize it:

1. waiting for merging this PR (need to wait a bit for release of 1.24.0 and maybe a bit more for bugfixes of 1.24.0 -> 1.24.1) and keep this code free of merging conflicts
2. refactor the menu to use a template instead of duplicated HTML code
3. add "my labels" feature in similar way
4. (maybe) thinking about having the article tags in the header too (I can remember there are some feature requests)
5. optimize the UI and "compress" actions into a sub menu

While doing it we should not forget to have a good integration into the reading view too.

I am bit excited to implement it :)