Skip to content
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.

Naming : KAMI to MOTIF !!! kami.js to motifs-js #25

Closed
Skaant opened this issue Oct 31, 2020 · 1 comment
Closed

Naming : KAMI to MOTIF !!! kami.js to motifs-js #25

Skaant opened this issue Oct 31, 2020 · 1 comment
Labels
design A conceptual work is needed documentation Improvements or additions to documentation epic Made of multiple features improvement New feature or feature improvement low priority Identified issue, will be fixed with motivations question Further information is requested

Comments

@Skaant
Copy link
Owner

Skaant commented Oct 31, 2020 •
edited
Loading

Actions

1. Evaluate the cost of this refactoring.

Globally, we think about :

  • Renaming _shrine to _motifs,
  • Renaming .kami.js to .motif.js,
  • Renaming KAMI to MOTIF.

More related work may appear during process.

2. Repository should be moved to motifs-js

Consuming projects should update the remote link.

3. Other controversial names

  • WAY to [ METHOD, OPERATION, F ? ],
  • PANTHEON, but I still like some ideas behind the concept.

Why ?

Kami may be a bit too oriented name. We think that we should stick to the concept of ...concept, pattern, idea, ...motif.

While concept and idea seem too general, pattern seems a bit too "patriarchal".

Motif in itself describes repetition as well as the motivation to use it.
@Skaant Skaant added documentation Improvements or additions to documentation epic Made of multiple features question Further information is requested design A conceptual work is needed low priority Identified issue, will be fixed with motivations improvement New feature or feature improvement labels Oct 31, 2020
@Skaant
Copy link
Owner Author

Skaant commented Nov 11, 2020

kami.js has been renamed motifs.
All .kami files has been renamed and tested

SHRINE is deprecated and instances has been completely removed
WAY is deprecated, but most folders remain, waiting for a refactor
PANTHEON remained untouched, wainting for a refactor

@Skaant Skaant closed this as completed Nov 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
design A conceptual work is needed documentation Improvements or additions to documentation epic Made of multiple features improvement New feature or feature improvement low priority Identified issue, will be fixed with motivations question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Skaant