#@cswordpress↩️ Do you know specifically which #indieweb functionality isn't working? That would be a useful place to start so that others can help figure out what's not working and how to fix. (twitter.com/_/status/1074319891132485632)
#[jgmac1106]except I am not doing what I sat down to do...layout an h-resume in css grid for my students to remix next semester...just wanted to do a like post......shutting everything down until the h-resume is done...just as I layout what I am calling my "few" static pages I want moar...need to learn to be happy with I have enough
#[tantek]Jgmac1106 how did you put it? Just want a box to type in some HTML?
#[tantek]Do you have a post / summary of just that feature / user request?
#[jgmac1106]yes I want a blank box for HTML, Known as a rich text edior, I publish stuff as post that shouldn't be articles simply as that is only route to HTML
#[tantek](Incidentally “just type / copy paste some HTML” is a lot like how I blog in /Falcon so I’m hoping to understand broader needs better through your example)
#[jgmac1106]if I syndicate a note from a micropub client it publishes in plain text
#[jgmac1106]yeah its neat, but I also worry nobody elese really wants to publish that way..but what i want...its the plumbing I can't do
#[tantek]Ooh like a micropub client that lets you enter HTML!
#[tantek]It may be a small use case but it’s definitely not “nobody else”
#[jgmac1106]all I want box->html->post the title no title field be something to figure out..but if h1 reserved for title maybe doable
#[jgmac1106]I would just keep every post type as a template in sublime, image uploads of course get tricky...requires a bit of UI
#ZegnatSo would you want an HTML editor for entire pages/URLs, or does it still apply some sort of templating around what you put in the box?
#[jgmac1106]then I saw...I add h-feed...my site is in my social reader with me doing nothing...I could design a page for my photos, likes, all the post types...CSS Grid brings design to everyone
#[tantek]Like do you explicitly put in the h-entry or does the CMS add that wrapper for you?
#[jgmac1106]for my long form writing I will just start with a blank HTML field...but I am spending too much time trying tofiugre out simple problems...
#[jgmac1106]I do that now because I have no CMS, but it takes 17 files in the Known plugin to inject an h-cite and a u-like-of....that seems wrong
#[jgmac1106]I huess the CMS should handle the top h...but the more CMS handles..the more that breaks and the more I can't do...
#[tantek]Yeah “17 files” is the kind of thing that can happen when a developer “refactored” code and/or uses a bunch of OOP
#[jgmac1106]microformats is easy enough for anyone who knows HTML that just doing plain HTML easiest approach...it's a community plugin as well....so noboidy to blame people helping each other, just feels like too much overhead
#[tantek]Even simple things (user features) end up requiring touching lots of files :(
#[tantek]Yes the # of files problem is what turns me off from most OSS
#ZegnatMy blog is built around an HTML field. But I definitely had problems there with figuring out how much wrapping the CMS should do. I started with h-entry+e-content wrapping. Then dropped the e-content when I noticed I wanted to be able to add metadata that shouldn’t be in there. Then dropped the h-entry when I also wanted to start posting events.
#[tantek]as in actually trying to contribute to and or use OSS libraries or frameworks
#[tantek]Actually even directories in a Github repo are a turnoff.
#sknebelyeah, I post a bunch of not-ideal markup because my site works similarly
#sknebelkeep meaning to have it look in the content in more detail, but haven't gotten around to it yet, always other things more interesting :D
#[jgmac1106]which is where I think I would end up back at empty HTML box....but also thinking about students...they would need a UI....but micrpub clients can be the UI
#[tantek]Not sure why there’s such a pattern / habit of complexity (hierarchy of folders, lots of files, lots of micromanaged mini OOP classes) among what seem to be majority of OSS devs & projects
#[jgmac1106]a note is easy: https://indiewebcoursetemplate.glitch.me/updates.html I can layout every page the way I want..what i don;'t know is post type discovery..if HTML contains X dispaly on page Y...and have no idea how to get webmentions to display...need all the plumbing
#ZegnatYou could do what tantek (and I think kevinmarks?) is doing and load the webmentions from off-site. No need to have that implemented yourself
#[jgmac1106][tantek] it is interesting...I think one distinction OSS as part of a company...you nee to justify your salary
#[jgmac1106]been thinking there are three types of OSS a company that releases OSS (Ghost) , a company that works openly and releases OSS (Mozilla...though working openly getting reduced), company who dominates an Open Source space (Automattic)
#[tantek]Few OSS projects should need to be more than just one folder of flat files, and even then only a few files
#[jgmac1106]Few OSS are just community supported and the focus on show not tell has help to protect against that influence
#[tantek][jgmac1106] there are many more types of OSS projects / companies - see if you can find the Mozilla “Open Innovation” report on this - pretty sure it’s a public PDF somewhere.
#[tantek]They did a lot of formal measuring, research, and analysis on this
#ZegnatI like it when there is a separate folders for the source and tests. Beyond that I am pretty ambivilant to folders
#[tantek]Would love to chat more with you about that
#sknebelthat's how you get the JS ecosystem on NPM: tons of tiny projects instead of larger-sized groupings? :D
#[jgmac1106]watching how ClassicPress is growing, committees, steering committees, marketing channels...all the stuff around the product before the product....there is a large Moz Rep influence...the structure you folks buuild into people gets reflected
#[jgmac1106]I was involved with the research on Open Innovation tangentially familiar
#[tantek]Zegnat I hate “source” folders. No, the top level folder / Github project repo *is* the source folder. Quit hiding the important stuff in nested folders!!!
#[jgmac1106]okay back to the h-resume....could just find a CSS grid aleady done...bu t wha'ts the fun...
#ZegnatI disagree. Because when I want to just checkout the files I need, I can much easier just grab the source folder and leave the test folder behind. If tests are interwoven with actual source things get murky real quickly.
#[tantek]and if I have to click more than one folder deep I just close the project. Not interested in something that complex. Less work to write it myself than understand someone’s else’s rando overly complex folder hierarchy.
#[tantek]Excess folder hierarchy = murky. That’s the problem. Deep folder hierarchy is literally murky, you cannot easily see beyond just one layer
#[jgmac1106]that being said, I like the modular vision Known went for...a small core with all the plumbing and a ton of compatible community plugins is a good design....in theory...if it was summer and not winter break I might take the steps of trying top make a minimal CMS
#[jgmac1106]just need an engine to and the hooks, have fun all be back later
#Zegnat“you cannot easily see beyond just one layer” - that is exactly my point with the source and test folder divide though. You do not need to see the 26 txt files and the PHPUnit TestCase if you are interested in the source of my library. Just read the source folder.
#Zegnat(I am noy advocating for more subfolders beyond that. As I said, ambivalent on that point.)
#[jgmac1106]I have about 2 million dolalrs in grants pending if any of them hit I get to build whatever we want
#[tantek]Zegnat no because everyone names “source” differently and you have to hunt anyway. Or they make one source folder then they split that into more. Includes, templates, etc etc
#[tantek]Yes to subfolders for the extra min-source stuff like tests, any project dependency stuff, documentation
#[tantek]But no source subfolders. Just keep all source at the top level where it is directly visible
#[tantek]extra non-source* stuff. Darn autocorrect
#ZegnatI already have 6 configuration files that go into almost all my git repos’ root. I am happy to put the actual project sources in a source directory, haha
#[tantek]Zegnat why not stick the config files in a “config” folder instead?
#[tantek]This is UX 101 IMO. Put the commonly used things (actual source files) as top level “options” (flat in the repo folder), then put less used options (config, tests, docs) in submenus/folders
#ZegnatBecause that is not where the tools look for them. You’d then have to go into the config folder to have composer grab dependencies or for PHPUnit to know where to find the tests.
#jgmac1106ohh web, I don’t really micropu on the web, usually just in the cms
#jgmac1106…of course if I went no cms I would need to figure out a web micropub client….never thought about that…if there are third parties to handle webmentions and stuff mayve I can get a blank box by not really using a CMS at all
#[jgmac1106]yeah...I can do that...so I guess I mean a littl ebit more..we had no idea what we were doing and visions of this big remixable web
[asuh] joined the channel
#tantek.comedited /multi-photo (+408) "/* Instagram */ no longer requires square multiphotos, just all items having the same aspect ratio, and that ratio is still capped a bit" (view diff)
#jgmac1106but why isn’t the create UI native rethink the space as both a pallete and a browser
#jgmac1106yeah I like playine with Beaker….and that’s what Atul keeps telling me to try
#[tantek]!tell aaronpk I think there have only been tweets/notes requesting IndieAuth in Mastodon, still waiting for an issue to be filed (and linked from https://indieweb.org/Mastodon#IndieAuth_Provider ) <-- maybe existing links there can help?
#LoqiIt looks like we don't have a page for "2018-review" yet. Would you like to create it? (Or just say "2018-review is ____", a sentence describing the term)
#[tantek]2018-review is a list of indieweb and indiewebcamp accomplishments for all of 2018, as well as indieweb-related news in 2018. See [[2017-review]] and start copying/filling out sections from there!