-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMS v3 #1027
Comments
Hi, @owen2345! I'm in, as long as I will have spare time to dedicate.
|
@owen2345 Great to hear from you!
Overall, I'm in favor of any change that reduces dependencies, or at least uses dependencies that are Rails defaults. I would like to be a part of this, but I'm not sure how much I'll actually be able to get done based on my current work. Once the work is more defined and broken up into parts I'll have more of an idea. |
Also, we should use ES6 modules for the assets as discussed in #1025. It seems like this approach would have the best support for use with both import maps and bundlers. |
@brian-kephart I thought nobody was using multi-site feature hehe.
@texpert @brian-kephart What other goals would you like to add or exclude? As it could be a step by step refactoring, it does not require a fulltime dedication. |
I agree. Since IMO, the es6 will be the standard in the near future. |
@owen2345 I think your list is pretty good. Most of what I can think of is for making onboarding easier. We have So instead of this... rails new my_cool_app
cd my_cool_app
bundle add camaleon_cms
rails generate camaleon_cms:install
rails db:migrate ... you could just do this ... camaleon_cms new my_even_cooler_app ... and it would create a whole new Rails/Camaleon app, ready to run. Additionally, I think it would be nice if the sample site generated included basic getting-started documentation, or a tutorial. So, when you start the app, it gives you some tips instead of listing features. Basically, helping people learn the basics by clicking around the sample pages instead of switching back and forth to separate documentation. We should also decide how to publish the new docs. Right now @texpert and I don't have access, so it's hard to help. We could do a GitHub wiki, but it seems wrong not to make a docs site with Camaleon :) |
I like your idea @brian-kephart
About the access, I thought I provided you the credentials, so sorry my bad. |
Hi, @owen2345! I have just sent you a message by email, so you'll have my email address. |
Hey guys @texpert @brian-kephart
I was thinking to work on the version 3 of the CMS with the following things:
As always, open to hear other features to be added or removed
Would you like to be part of it?
The text was updated successfully, but these errors were encountered: