scripting / feedlandSupport

A place to share and discover feeds.
13 stars 1 forks source link

The next step in News Products #84

Open scripting opened 1 year ago

scripting commented 1 year ago

We're not done! :-)

In the next revision, you can specify the HTML that the news flows through.

This only works in outline-based templates, because who wants to edit complex HTML in a browser text box.

Here's an example.

http://sideways.this.how/

The header stuff is on the side instead of at the top.

I omitted the white-on-orange XML icon (to show that it can be done).

This is the outline behind the pretty face.

It took about an hour to do the code and build the example. Things are pretty well-constructed behind the scenes.

Knock wood.

scripting commented 1 year ago

I updated the News Product docs to include information about the new optional html section of the outline.

http://docs.feedland.org/newsProducts.opml

I also fixed some stuff that had broken with all the recent changes in news products.

scripting commented 1 year ago

A new feature/fix.

The last time the News Products sub-menu of the Tools menu was updated was before categories and outline-less news products.

Today I updated the code that builds the menu to show news products created through the new simpler Settings interface.

image

voitto commented 1 year ago

is there a way to get a URL directly to my news product opml in Drummer? Right now I am going to the File menu and choosing View OPML. can i compose a url to the opml such as drummer.scripting.com/?product= or ?screenname=. ✍🏽

scripting commented 1 year ago

@voitto -- yes.

  1. Choose Make outline public in the File menu.
akaKenSmith commented 1 year ago

Thanks to the inspiration of others who've been fancying up the display of their news products--since things might be more public soon. I added a header image today and also it's all presenting nicely on my own domain: news.tabconfab.com *

Screen Shot 2022-10-19 at 11 13 44 AM

*Works in a few browsers, but Chrome on my iPad doesn't like the shift midstream from https to http, it appears. If any members of the group know a work-around, let me know. But I'm satisfied with leaving Chrome out for now.