You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
1I may not have time for an answer. But, maybe start with considering why you want "separate, self contained, importable components" to begin with. How does component-izing some stuff on a page make your team's job easier?svidgen– svidgen2020-03-09 18:23:27 +00:00Commented Mar 9, 2020 at 18:23
-
Thanks, @svidgen. I am building a Content Development Environment so, in a wider context, a component here represents a user-generated "plug-in" which may (or may not) be reused on different pages by the same site, or by other sites. The most immediately apparent benefits of such component-ization are plug-and-play reuse across different documents, sites & web-apps and component-level scoping, such that an individual developer might work on a given component without needing to know anything else about the overarching site(s) the component will be "plugging into".Rounin– Rounin2020-03-09 18:38:13 +00:00Commented Mar 9, 2020 at 18:38
-
1A good place to start your guidelines, IMO, is just be to restate that as guidelines. Maybe, "If what you're developing may be re-used or benefit from it's own scoping, component-ize it." ... Bear in mind, it still requires experience to recognize when things are likely reusable, benefit from internal scoping, or whatever other guiding quality you come up with. Maybe also consider what the with problems with "over-componentization" are and state as counterbalancing guidance.svidgen– svidgen2020-03-10 16:30:20 +00:00Commented Mar 10, 2020 at 16:30
-
Yes, you are absolutely correct, I am seeking to avoid over-componentizing my setup. This is the main thrust of my question above: while I know I can turn every last nut and bolt into a component, I feel this is going overboard and I want to establish if there are any rules of thumb I can refer to, to help me decide when to turn something into a component and when not to.Rounin– Rounin2020-03-10 17:28:16 +00:00Commented Mar 10, 2020 at 17:28
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you