Ruggan posted:

I pushed some minor changes to one of our customer-facing websites yesterday. This website is essentially a project management & task tracker for our clients - it isn't a core part of our business but supports groups who buy and need to implement our software. One of those changes involved adding a column to a CSV extract you can pull from the app's UI. We don't expose any sort of API endpoint, you need to get it from within the tool. I got a complaint this morning from one of our employees who is staffed to some organization that was "surprised" by the change. Apparently this organization is doing some scripting automation to pull down their data via the extract and post-process it. Adding this column broke their script.

I'm not sure I'm comfortable committing to support code-writing end-users, but it brought up a few questions that I'm interested in hearing from other folks on:

• Is versioning a web-app valuable, beyond marketing purposes? If yes, what versioning method do you use?
  
• Is the code-writing end-user someone that is worth providing explicit support for even when we do not provide a public API?
  
• What would you consider the public API of a website? (relevant article here)
  
• What constitutes a major change, minor change, and patch to a website (applying the SemVer mental model)?
  
• What sort of proactive communication do you feel is necessary for varying degrees of change?
  

Ruggan posted:

Is versioning a web-app valuable, beyond marketing purposes? If yes, what versioning method do you use?

Ruggan posted:

Is the code-writing end-user someone that is worth providing explicit support for even when we do not provide a public API?

Ruggan posted:

What would you consider the public API of a website? (relevant article here)

Ruggan posted:

What constitutes a major change, minor change, and patch to a website (applying the SemVer mental model)?

Ruggan posted:

What sort of proactive communication do you feel is necessary for varying degrees of change?

Lumpy posted:

If you were actually updating an API, I'd answer your questions, but since it's a website, there's no need. Them scraping your site is their problem, not yours.

sunaurus posted:

Providing a public API and providing explicit support for an internal API are pretty much the same thing. It's worth creating public APIs for end-users who will pay for them.

If no other agreements are in place, then I would never consider anything but the UI to be the public API.

sunaurus posted:

Keep track of all systems that depend on your APIs (give them unique API keys and make sure to have a mapping of API keys to some sort of contact information). If you want to deprecate an older version your API, it's also useful to know if it's ever actually used at all, so keeping track of historical request statistics is also be a good idea, and you can find out exactly who is using which API endpoint by forcing everybody to use API keys. When you release a new version, keep the older versions around if at all possible, and communicate to all known users that the old version is deprecated and will be turned off at X date.

Lumpy posted:

If you were actually updating an API, I'd answer your questions, but since it's a website, there's no need. Them scraping your site is their problem, not yours.

Thermopyle posted:

Also, once you start feeling pretty good about your abilities go to a site like the following and realize you know nothing.

https://tympanus.net/codrops/category/tutorials/

Null of Undefined posted:

Please note: Never ever show this site to a product owner or designer.

uncle blog posted:

In React, what's a good way to implement a button that needs to be pushed for a couple of seconds to have an effect? And also set a css class on initial push to animate that it is reacting/waiting.

oliveoil posted:

I have a really hard time taking a set of wireframes or mocks and turning it into matching html + css.

Is there any good resource for web development for a backed software engineer who wants to be able to handle frontend?

I can do backend stuff no problem but I will spend two hours of trial and error trying to do basic tasks like figure out why an anchor tag won't center in the middle of its container even though I thought I understood the flexbox cheatsheet I re-read right before starting, then spend another three hours trying random poo poo to figure out how to remove the text decoration from it and make it inherit the color of the container since the container may be in multiple states with different colors for its contents and I had no idea I needed to use the text-decoration or inherit keywords and I didn't see anything on stack overflow for that till I happened to rephrase my Google search in just the right way.

I had a big UI project late last year that resulted in me getting complaints about my slow performance from a teammate and my manager asking if I wanted to stay here and what my future plans were.

I was pretty much at the end of that UI project at the point when those complaints started coming in so I was soon able to get backend stuff and start making fast progress again, but this seems like a major weak point of mine that I don't know how to address.

I always thought I could do literally anything given time, but it seems that there's a big difference between getting something done very fast and getting something done very slow. Backend stuff, code flies from my fingertips faster than my teammates review it and I develop a backlog of stuff they have to churn through. But frontend stuff, I get similar sized changes out every 2-3 days instead of 3-5 times per day.

What do I read to get me ready to become a web dev expert? I want to get just as fast if not faster at web stuff than I am at backend stuff.

oh no computer posted:

I'm trying to learn web development in Javascript and to this effect I'm building a simple webapp in Node/Express using mongoose to interact with a MongoDB database. I'm trying to delete everything in a specific collection where some condition is met, so I'm using the deleteMany() function. The mongoose docs seem to indicate that providing a callback function isn't required (that's what the square brackets mean right?), but if I don't provide a callback it's not working properly:

code:

// doesn't work (no error just doesn't perform the deletes)
Comment.deleteMany({
    _id: {
        $in: someArrayOfIDs
    }
});

// works as expected
Comment.deleteMany({
    _id: {
        $in: someArrayOfIDs
    }
}, (err) => {
    if (err)
        console.log("Placeholder message to be replaced by proper error handling at a later date");
});

Obviously I can get it working by just providing a callback, but I'm trying to learn this poo poo and I'm confused as hell as to why one works and not the other.

Edit: just noticed there's a separate JS thread further down, apologies if this should have been posted there.

Lumpy posted:

Go to Dribble or other site where people post UIs. Pick one. ...

prom candy posted:

A lot of people act like implementing layouts with HTML and CSS is easy but it can be really tricky! See if you can find some screencasts ...

uncle blog posted:

Is there a good place to ask UI/UX questions related to web apps?

The Fool posted:

I mean, there's technically this thread, but seriously

uncle blog posted:

kedo posted:

I have a big batch of exported content from an old site that needs to be imported into a new site (WordPress). The content is in a CSV, in its raw HTML format. I need to perform some mutations on the content to support the new markup/styles on the site, so for example I need to be able to take a piece of code like this:

code:

<div class="Media--center">
  <div data-picture data-alt="alt text" data-class="Media-image">
      <img alt="image alt text" class="Media-image" src="https://example.com/image.jpg" />
  </div>
  <div class="Media-caption">
    Caption text goes here.
  </div>
</div>

and change it into this:

code:

<div class="ImageContainer">
  <img alt="image alt text" class="ImageContainer-image" src="https://example.com/image.jpg" />
  <p>Caption text goes here</p>
</div>

So nothing earth-shatteringly complex, but enough of a difference that doing it by hand for several thousand pages of content would be a massive pain in the rear end. Any recommendations for how to approach this/tools that might be helpful? Best case scenario I'd like to do the work outside of WordPress, probably locally, so that I can import content and have it Just Work™ if at all possible.

I'm comfortable in JS and PHP and would rather not learn a whole new language just for this one project. I'm imagining some sort of JS that might use something like jQuery for DOM modifications, but I'm not sure what's the best/smartest way to parse, update and save a CSV.

Null of Undefined posted:

Depending on how complex these mutations have to be you should be able to do a lot with regex and find+replace in your editor of choice.

NotWearingPants posted:

I'm sure NodeJS has something similar.

NotWearingPants posted:

The person who first came up with CRUD could have easily gone with CURD instead. I think I would have chosen the later. I wonder if they regret it.

NotWearingPants posted:

The person who first came up with CRUD could have easily gone with CURD instead. I think I would have chosen the later. I wonder if they regret it.

NotWearingPants posted:

It might have been interesting to try a window.print() from the console to see if the problem might have been with the buttons and not the print function.