Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users

Dashboard
Notifications
Mark all as read
Meta

Are we there yet?

+4
−0

Are we ready to let the world know about this site yet? What, if anything, do we still need to do or set up first?

I have created a bunch of help pages that are intended to give newcomers a good idea how to use the site, and what is expected of them. There is an infinite amount of information that could be provided. Do we have enough to go live?

Of course this site isn't a secret, and anyone can come here as it is, and we can't control who tells whom about it. I'm going to hold off my own efforts to make the site known out there until there is a consensus here that we're ready.

2020/6/12

It's now over 24 hours since this was asked, and there have been no answers. There has been one comment from a bystander suggesting that there should be something here when people first visit. That makes sense. I've already written one canonical question and answer, with more planned. Hopefully others will add some of their own.

At this point I'm going to start letting people know about this site. It will take a while for people to poke their heads in, and more canonical questions will be added in the mean time. I'll also make it clear that this site is new, and therefore doesn't have an existing volume of questions. That's a feature! Your question won't get drowned under a flood of others.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

3 comments

I think it would help if the people you reach out to saw at least a couple questions in Q&A. A blank page can be a little off-putting. You know your target audience better than I do, but consider a little content to start? I don't think you need a lot, just something (of decent quality) to give people an idea what they'd find if they come back. Monica Cellio‭ 11 months ago

@Monica: Yes, I plan on adding a few canonical questions. I've been busy with the help pages, and the day job gets in the way too. Do you think this is something we need to do before getting the word out about the site? Olin Lathrop‭ 11 months ago

I'm hoping your other initial users can help with that; one person needn't (and shouldn't) bear the entire load for a community. I do think it'd be better to have something there before you start reaching out to people; the difference between "there's going to be a good thing here, trust me" and "here, you can look at samples of what we mean" is significant. Of course the site is public and anybody can come at any time; this is more of a marketing concern. Everyone wants this site to succeed! Monica Cellio‭ 11 months ago

2 answers

+3
−0

Hi there!

The on-topic page https://electrical.codidact.com/help/topics might need a bit of tweaking and discussion.

I think it is important that such a page attempts to be as specific as possible early on, so I quite like it and agree with most stuff there. But a few other things might need to be addressed:

  • "The physics behind how circuits and circuit components work" should probably be expanded to all physics involving electronic design - including things like magnetism, radio, optics etc etc.

  • Soldering, electronics assembly and ESD should explicitly be on-topic.

  • Electronic component identification. Potential hot potato. A lot of people find this interesting - do we want this & to what extent?

  • Repair questions. Definitely a hot potato that probably calls for a discussion thread of it's own. This needs to be made either explicitly on-topic or off-topic. Should we allow them or not? If allowing them, we need rules. What's required from the OP other than the question being researched & answerable? Basic electronics knowledge? Basic tools like solder iron and multimeter? A scope?

  • Similar to repair questions: DIY questions where someone is trouble-shooting/fiddling with the household mains voltage or the electronics in their car etc. On-topic or off-topic?

  • Electronics approval/certification/legislation (FCC/CE/UL etc approval) questions should probably be on-topic. Possibly also including electric environment questions such as climate testing, IP class, EX etc.

  • General programming questions that are not unique to embedded systems should be off-topic.

Why does this post require moderator attention?
You might want to add some details to your flag.

5 comments

I'm not qualified to comment on the content of this, but a note on mechanics in case it affects the discussion: if you have types of questions that have fundamentally different requirements, you could consider creating a category for them. Photo created Gear Recommendations for this (yes you can ask these but you have to specify...), and Scientific Speculation has a category for more-rigorous questions with higher requirements on answers. Just FYI in case the approach helps on this site. Monica Cellio‭ 11 months ago

@Monica: Thanks, but I think we'll wait a bit on that. Creating lots of categories early makes the site look even more empty than with the single category we have now. We may eventually get there. Time will also help us see where splits make the most sense. Frankly, I think it was a mistake of Photography to create all those categories, at least for now. The place looks like a ghost town. Olin Lathrop‭ 11 months ago

@Lundin: Some of what you ask for already existed. I also just added a few items. Repair questions are tricky to make on-topic. There should probably be a help page devoted to them, like there is for component ID questions. I'll work on that as I have time. Olin Lathrop‭ 11 months ago

I don't think sites want lots of categories either. Categories aren't tags. In designing them we were envisioning a site having maybe as many as 4 or 5 (Q&A, meta, blog, contests, maybe something else -- not necessarily all of those on any particular site). Monica Cellio‭ 11 months ago

Things like component identification or repair questions are probably not suitable categories, we should rather just make rules for how they should be asked, as I've now noticed was already done here: https://electrical.codidact.com/help/compid. Lundin‭ 11 months ago

+1
−1

$\color{purple}{\text{Are we there yet?}}$

No, it's not ready: -

  • The embed image doesn't seem to work anymore on the EE part of the site and neither does it work here. It did yesterday because I added an image to an answer I posted; but not today - I just get a message saying: -

javascript:void()

I have javascript enabled for this site and I have no sites listed as blocks for javascript in Google Chrome

  • I get no preview pane while editing or writing an answer or question on the EE site - it works here on meta because I can see it below. Here's what I see on the EE site: -

Image alt text

  • I get two underscores but that doesn't italicize the text. Deleted due to user incompetence.

  • Regards posting images (when it works for me), "the other place" allows you to use CTRL-V to place an image you have previously copied. Going through the rigmarole of saving to local drive as an image and then trying to find that image via the current embed_image button is tiresome and not as sleek and quick as "the other place".

$\color{red}{\text{hello everyone}}$

  • I'm glad to see that mathjax or latex (or whatever it's called) works but it's a bit flaky in that as I add to this sentence it temporarily results in it going back to: -

\$\color{red}{\text{hello everyone}}\$

  • Also, when I use blockquote on the above latex phrase I get this: -

$\color{red}{\text{hello everyone}}$

  • And not this: -

\$\color{red}{\text{hello everyone}}\$

I guess it might be monospace font: -

\$\color{red}{\text{hello everyone}}\$

  • Yes it is! Hurrah. Previously I used the "`" character to make it work. OK, so blockquote and monospace quotes work - I just got them the wrong way round because they are in different places on "the other site". $\color{magenta}{\text{Another case of user (me) incompetence.}}$

  • I started editing something and I ended up making a mistake that I wanted to rectify with an undo button - I can't find it. So, I tried cancelling the edit but couldn't find that either so it ended up a bit of a head-scratch and I bodged my way through laboriously and with pain.

  • Another annoyance (and it is an annoyance) is that when you drag your mouse (left key pressed) over text already written so that you can block-quote it, after pressing the block-quote button, the edit pane drops right to the bottom and you easily forget where you are and have to search for the bit you were trying to modify. Yes, that is very annoying.

$\color{blue}{\text{Recent "observations": -}}$

  • when getting a notification of a comment added, it takes you to the page where the comment is added but doesn't help you find that new comment - in other words you have to wade through all the other comments on the original posting and answers to see if that might "be the one". Not a show-stopper but a right royal pain.

  • The "EE" top banner should remain fixed in place as you scroll down unless there's an overriding reason (based on user experience) that takes precedence over my desires.

$\color{red}{\text{Newer "observations": -}}$

I really, really don't like the ability to change comments beyond the 5 minute limit. I don't like it at all, not one bit, ever. It leads to confusion and time wasting trying to figure out what someone originally said when you are trying to explain to them where their original comment was incorrect and, suddenly (and out of the blue) you "see" that what you thought they originally said has possibly changed and then, you doubt that what you thought you originally read was a mistake on your own part. Not a good idea.


Of course I'm used to how "the other place" does things but the fewer the differences the better for me. Did I mention I was selfish and want everything done my way no later than this Thursday?


For my sins I have previously taken part in beta testing of new websites.


Anything I list as user incompetence means yes, I was incompetent but, if enough folk also demonstrate the same incompetence then it potentially becomes something that is worth fixing.

Why does this post require moderator attention?
You might want to add some details to your flag.

18 comments

Most of these are system-wide issues, not specific to this EE site. There is a system-wide meta for that, but the people that would see that might also notice it here. The software is very much still in development, but far enough along to have at least basically working Q&A sites. I was really asking what we can do here on the EE site before letting the masses know about it. So far we created a bunch of help pages and some canonical questions to get things started. Olin Lathrop‭ 11 months ago

Most of what you've mentioned here is either not a bug, a misunderstanding, or the same as how it works on SE. If you want to post this as a question on Meta, I'll explain each point individually - hard to do that in comments! ArtOfCode‭ 11 months ago

@ArtOfCode No, I don't want to post it as a question on meta. Olin says these are system-wide issues and YOU say it is not a bug, a misunderstanding or same as SE. There is a huge difference between what you say and what Olin says so you guys need to get your cylindrical brown lumps together because you are cancelling out each other and confusing me...... Andy aka‭ 11 months ago

.... Olin asked me along here to throw in my little bit and that's what I'm doing. Of course I may be wrong about this or that and need a slight poke in the eye as a reminder to work at things a bit more but, there are things I say that still look like bugs. Andy aka‭ 11 months ago

@Andyaka With all due respect to Olin, he's not the developer. I am, which means I'm in a better place to recognise what's a bug, not, or otherwise - and causes, and workarounds, etc etc. I'm also in a position to help you get things that don't work for you fixed, but it can't be one-sided - we need to be able to figure out an agreeable solution, rather than either of us insisting that "it's a bug" or "it's not a bug". ArtOfCode‭ 11 months ago

Show 13 more comments

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!