Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Refactor/remove js layout files #161

Merged
merged 2 commits into from
Sep 3, 2023
Merged

Refactor/remove js layout files #161

merged 2 commits into from
Sep 3, 2023

Conversation

Bowens20832
Copy link
Contributor

No description provided.

@Bowens20832 Bowens20832 added type: enhancement New feature or request. type: friction Elegant user friction. To be fixed with priority. version: 3.0 Issue will be included Elegant version 3.0. Estimated Release: November 2023 status: ready to merge PR's that are ready for public review and comment. Will be merged in a matter of days once tagged. version: elegant-cms This is the development effort leading up to v1.0 of Elegant CMS. labels Sep 2, 2023
@Bowens20832 Bowens20832 added this to the Elegant version 3.0 milestone Sep 2, 2023
@Bowens20832 Bowens20832 merged commit da21634 into v3.0-alpha Sep 3, 2023
1 check passed
@Bowens20832 Bowens20832 deleted the refactor/remove-js-layout-files branch September 3, 2023 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
status: ready to merge PR's that are ready for public review and comment. Will be merged in a matter of days once tagged. type: enhancement New feature or request. type: friction Elegant user friction. To be fixed with priority. version: elegant-cms This is the development effort leading up to v1.0 of Elegant CMS. version: 3.0 Issue will be included Elegant version 3.0. Estimated Release: November 2023
Projects
Elegant Framework
Status: Elegant - version 3.0 -- Elegant CMS
Milestone
Elegant version 3.0
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@Bowens20832