j12tGWG: I'm unclear just what the "optimal" configuration is ... the perfect help would be if somebody knowledgeable logged into my example instance, and configured it, documenting it step by step as I did
j12tBest if any screen shots look as close to what the reader will see ... if I have them set up an account called "admin" that's what we should use ...
[chrisaldrich]mrkrndvs I suspect that to add more extensive h-card detail into the theme itself, you'd want to create a child theme and replace some of the template files for your posts. Doing this would involve some code however.
j12tI basically installed "everything" relevant that I'm aware of, and so chances are that not all of the plugins/themes that are available make sense at the same time
[chrisaldrich]j12t, the tough part about setting things up "to your liking" is that there are a multitude of different plugins as well as means of doing various parts of an indieweb configuration.
LoqiUBOS (pronounced You-Boss) is a new Linux distro that makes it much simpler to install and maintain indie web and IoT applications on physical servers, cloud servers and devices such as as the Raspberry Pi https://indieweb.org/UBOS
[chrisaldrich]While there isn't a one-size-fits all solution, one could certainly recommend a minimum threshold, but then folks are likely to want to move beyond that at some point too.
j12tchrisaldrich: totally agree. The point of these tutorials is to get the user from zero to "it works". So pick whatever is easiest and most compelling. After it works, we can discuss and recommend what else could be done / instead.
[miklb]Not sure I could encourage a WordPress scenario where you had to add/update plugins & themes from the command line. I mean, I use wp-cli for a lot of stuff but a user could still do it from the admin.
[chrisaldrich]miklb I'd generally agree, especially since command line work can be pretty opaque for most generation 2+ users who are the most likely to benefit from a recipe like this...
[chrisaldrich]I was looking at setting up a wp-cli recipe for setting up and installing an indie-capable site, but have set it aside for some of the issues I think that Gen2+ would have in utilizing it.
j12tThis is for somebody who is willing to setup their own server, and take responsibility for it. They will have to run apt-get or pacman or whatever to keep their OS updated otherwise
[chrisaldrich]I agree and thought that the original purpose of this was to bring the walls down. Kudos on putting together a reasonably followable tutorial though!!
[miklb]j12t point taken, but I still wouldn’t want to tie my WordPress plugin and theme updates to the OS and disable the admin option. Nor could I recommend it. But then again, I don’t know UBOS.
[chrisaldrich]GWG, I was following along in Github, but don't remember any specific reservations he had... I thought it was more about time than anything...
[chrisaldrich]j12t I would tend to agree with miklb as disabling the traditional interface would require people to really know wp-cli even better and limit the amount of searchable support was immediately available for a large swath of potential users.
GWG[chrisaldrich]: No. It doesn't. I do it that way because otherwise, the display issues are problematic. But as raamdev points out, a plugin calling the_content would therefore get the markup.
[chrisaldrich]Has anyone set up an indieweb suite of plugins on a multi-site configuration? Does everything work? I'm tempted to do one as a means of pulling in 2nd/3rd gen users or friends who are interested in kicking the tires so-to-speak.
[chrisaldrich]I've been thinking about the business model for edublogs and considering creating a multi-site instance somewhat like they've got (though naturally focused on indieweb technologies instead of education).
[mrkrndvs]chrisaldrich I wonder what it would take for someone like Edublogs to incorporate some of the elements of the #indieweb. Like your idea of a multisite though.
j12tI guess what I'm trying to say is that there is a big scary looking text field in the middle of my New Post page, about 50% as big as the field for the content of my post, looking like it's demanding input, but there are no contextual clues about what should or should not be entered.
j12this essential point is that for a great software demo, you need to get from start to "wow, I want this" within like 3 minutes. All details come later
[miklb]I understand that. I just feel like sometimes feedback on the IW WordPress experience doesn’t take into account the constraints of the WordPress admin and what plugin developers are limited in doing from a UI standpoint and that tradeoffs sometimes are made.
[miklb]Personally, I have been shoe-horning WordPress for 10 years, so I’m comfortable with all of the extra fields. But I get the point that from someone not as familiar with extending with a lot custom meta boxes could be taken aback by the UI.
j12tAnd I also want to do the whole thing, end to end, on video / screen cast. I think it can be done in less than 10min if typing fast, and it would be a great proof point
[chrisaldrich]GWG, I'd be careful hiding syndication links by default. Most users who install the plugin are going to be immediately wondering where the field is after they activate it.
[chrisaldrich]I always have the feeling that too many people don't know that screen options even exists to bring things back, much less that they can drag and drop those meta boxes to places they want in the admin ui.
j12tIt's just following the tutorial. I learned how to do 3D CAD by following some video tutorials going through completely non-obvious GUIs. It can be done :-)
[chrisaldrich]GWG, I would suggest that someone like j12t who wants to hide it in a simple install like he's talking about, should do it via wp-cli or in specific code.
[chrisaldrich]I suspect most who download and install it do so as an a-la carte thing or as part of the indieweb installation workflow and know what it is and what it does.
[chrisaldrich]I keep hearing that Gutenberg is a better/easier client for publishing to WordPress. Why not do that workflow with micropub so that clients doing custom publishing would work not only with WordPress, but could be leveraged to publish almost anywhere on the web?
[chrisaldrich]As an example, I'm always seeing dev shops building for gen4 users and spending a lot of time hiding UI so they can't "screw up" their posts. Why not just create a clean micropub client that only allows the 2-3 fields they want to give the user, and rely on the plumbing to do it's job?
[miklb]Well, they have the Rest API for that…I get your point, but I don’t think we’re at a point where the millions of people using WordPress in the browser are going to switch just yet.
[chrisaldrich]I just remember the days in which there were thousands of Twitter clients, it'd be cool to see that kind of proliferation happening not only for WordPress, but for any other CMS that supported micropub.
[miklb]I’ve been one of those devs who hid as much as possible from content creators. Not so they wouldn’t screw anything up, they just didn’t need the distraction. They had one focus and there was no need to confuse them with a huge menu of stuff they didn’t need to bother with.
[chrisaldrich]As an example, micro.blog has a pretty clean interface for posting status updates to WordPress, or MarsEdit for generic posts. It would be cool if these were more broadly supported for all platforms instead of just some.
[chrisaldrich]Quill is certainly a great example. Wish it worked natively with Post Kinds though. I see a lot of wonky posts by folks using it or other micropub tools in combination with Post Kinds....
[chrisaldrich]This looks about like the type of post I've seen on a few sites using Post Kinds and seems to have come from somewhere else like Quill, though perhaps I'm wrong): https://stephenpieper.net/general/3179/
[chrisaldrich]It may have been made by the press-this bookmarklet too... Better would be for the link to be in the URL field with the fetch/parser data filled in.
@FJdeKermadec@miklb The microservice is indeed not the issue… The issue, as I see it, at least, is that third-party URLs are inherently more brittle (less future-proof) and that a URL using the word “demo” is even less likely to belong to a production or stable server. ? (twitter.com/_/status/934327345934200833)
[miklb]if the content of the tweet is supposed to be marked up like a title, I just want to understand the mf2. Or iw the post-kinds template is handling how it is displayed?
[miklb]But if it’s not, then I would recommend not filling in the field because a new user wouldn’t know they are supposed to clear the title field before publishing.
[miklb]and some tweets don’t add anything to the title. I can’t find anything different in the tweets to differentiate one to get a title and one not to. I’ll investigate further.