@marko-srb I've changed the posts to drafts, but for future reference you should have access to do that yourself. I also changed the first item to its own issue, in general that's easier to handle for dev work (1 issue per task).

@ryelle Is it ok to have the 'meta issue' and then separate issues from there? Or its better to have only separate issues themselves?

It seems to me that unless we categorize, we won't be able to keep track of anything really. And its been the case on the last 3 sites I worked on, hence the question. Thank youuu!

It seems to me that unless we categorize, we won't be able to keep track of anything really.

We have the labels (ex, Needs design/design feedback), assignments/review-requests, & project board for help with keeping track of things.

I dislike "meta issues" personally, because in my experience, they don't have scope to them, and they're very hard to close. I've mostly been breaking your big issues into separate ones for my own work, then circling back and closing the meta issue once I've created the task-issues.

Other Neso devs might have different preferences, but usually 1 issue per task is good because then we can close the issue with a single commit/PR.

One issue per task it is. Can you help me to learn how to find an existing issue (this one we are chatting about for example) in that project board list? Thanks!

I haven't added this issue to the project board because it's not a single-task issue. Your first request, to update the featured grid on the homepage, is a new issue and it's 3rd in the "To do" column. I add issues to the board manually, if they're part of the work required for launch. I've been less strict about this with the issues that are just content/design, though.

You can check the status of an issue in the "Projects" area on the issue itself: