Closed livike closed 9 years ago
@livike: I do not see the the 4 column layout when I checkout your branch locally. Is it because I do not have your project table locally?
@anuschka your Pull request hasn't been merged yet, so @livike can't have that. Also, the footer is not really the important part here ;)
@anuschka if you mean a 4 column layout of projects, yes, because you don't have anything in your projects table... use the admin interface and add something... or use code from the console (the tutorial covers this as well)... if there is no data in the table, nothing will (or should) be shown
@anuschka: as @goranche said, put some data in your tables and the page will show them
I have a question: I'm upgrading my work by adding a project details page. The click on the project title will link to the new page. What is better practice: to continue to work in the current feature branch and push the new commits, though the PR description don't covers the new changes or it's better to make a new branch based on the actual feature branch "projectpage"?
you can add the description, after you push... :wink:
but to actually answer: the "right" way would probably be a new branch and new PR, but that will complicate things as well, as it will introduce PR dependencies, which are not a good thing... in this case I'd say "do it here"
Thanks, will do this way
Awesome work @livike. It works like you described :+1: :clap:
you can add the description, after you push
I meant "you can edit the description"... :blush:
Added a second commit containing the project detail page
Created dynamic view and added dynamic data into project.html template No particular design implemented, only a dynamic 4 column layout, some conditional data display. Update: The link behind the name of the project on the project list will open the new project detail page for this project. Related to issue #116