Cudos and feature requests

Yes, great! Everything works as expected, now!

Already thinking about new ideas like…

• Your jQuery injecting the page slug as an id for the content-panel div, to have named anchors like /#contact in the custom links
• Added functionality to use category archive pages as front page sections, too

…just dreaming…

Ah, and how can I feed your PayPal again for all your efforts?

That’s good news.

Page slugs as anchor link ids should be possible. I’ll add it to the list.

How would you see the category archive content on front page working? I notice on your site you have “Upcoming Academies” … is that what you mean? What do you use there?

You can always use the “Feed Now” button on our website ??

https://webd.uk/options-for-twenty-seventeen/

Thanks!

Oliver

The academies are a good example. Under the hood, I have the academies basically organized in chronological categories like academies-2018, academies-2019 and so on. And I have one category apart from that which is upcoming-academies and which I attribute temporarily always to the next two or three upcoming academies as a second category to have a quick selector.

This way, I automatically have an archive page for that temporary category which is automatically always up to date (reachable from the main menu). But in order to have that on the front page, too, I actually add manually single post blocks (another Gutenberg plugin) to the static front page. That works, too, but I feel that this manual add is redundant work, and the style is horribly different from the upcoming-academies category page. That’s why I’d like to integrate this one directly as a front page section. And with named anchors, I would not longer have to rework the custom links when I add front page sections or when I change the order…

Will try to play with PayPal, now.

OK, so, for example, you would like one of the sections on the static front page to be able to be the category “Upcoming Academies” and to show the following …

1) Category Title with link to Category
2) Category Description
3) All (?) the posts from that category in descending date order (newest first)
4) Post Title with link to Post
5) Post Featured Image
6) Post excerpt
7) Continue Reading link to Post

This is quite complicated and I’ll need to work out exactly what you mean in order to think about how it might be done.

Thanks for the payment! ??

As I said, that would be a “nice to have”, no hurry!

I imagine adding the upcoming-categories (or any other) archive page as if it were as static page into a front page section. I imagine it being rendered like the original archive page, again like a static page which is also be rendered identically, independent of the page being displayed as stand-alone or as a front page section.

Just for info: I just got feedback from the WP-Multilang plugin developer. In fact, the translated URL rewriting works, when the full URL is given in the custom link, i.e. https://mydomain.com/#myanchor. I tried this and can confirm. Thus, if a new update with named anchors and putting the full url by default will come from you, we could definitively close this part of the construction site.

The other thing, the category page(s) as front page sections, might be more complex or need more thinking, thus I’m ready to put it on low priority for the moment.

Hi Oliver,

me again… I decided to abandon the idea of category pages as front page sections for the moment. Static pages with nice posts sliders which allow to filter by category do the job for now. Found a nice plugin for that.

Thus, I wanted again to point out the importance of named anchors in the #page-slug style. Having these would allow to easily re-arrange front page sections (adding, moving, etc.) without having to rewrite the menus all the time.

Kindest regards from France

Thierry

Hi Thierry,

OK, lets stick archive pages on static home page sections on the back burner for now. I’d been thinking about it and to be honest thought that the only real way would be to have a short code “solution” where by posts are returned to a page using a shortcode. This page could then be selected in the customiser for a home page section. But … because this is a solution that doesn’t require the Twenty Seventeen theme, it’s probably outside of the scope of this plugin and I believe there are already plugins that do this job.

Soooo … I can confirm that “named anchor links” and full length anchor link URLS are top of the list for the next update.

Kind regards,

Oliver

Great!

Let’s add a little usability detail: What about a configurable (enable/disable) option which would add a “Back to top” link at the end of each front page section, with a simple #main href?

Nice one. I like that. Should it appear on all pages as well at the bottom or just the static front page sections do you think?

Depends on people’s use case, I think.

Thus, in the customizer, I’d allow distinct options with a select element:

Add “Back to top” link at the bottom of

• all front page sections
• all pages

… where the “all pages” option would have to include archive pages, too.
But the one option would have to exclude the other to avoid doubling the link.

I just made a quick hack to demonstrate how I imagine it could look like, by adding the following code snippet in the template part files content-front-page.php and content-front-page-panels.php, just before the closing entry-content /div:

				//start insert
				<div style="text-align: right">
					<a href="#main">Back to top</a>
				</div>
				//end insert
			</div><!-- .entry-content -->

That’s a quick and dirty hack, I admit. I’m sure that you can do this in a smarter way with jQuery, so that the string “Back to top” would be translated and not be hard coded English.

You might see the result on https://theremin.academy/ ??

• This reply was modified 6 years, 4 months ago by Thierry.

Yes, a drop down is what we were thinking too, maybe tick boxes. We’ll see what works best.

And yes, that code is similar to what we’ll need to do although it would have to be injected at the top of a section via the get_template_part_template-parts/page/content hook and pushed down via CSS … no jQuery required ??

Oliver

By the way, #page might be a better anchor link?

Oliver