-
Notifications
You must be signed in to change notification settings - Fork 11
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
Several static-content pages #11
Comments
In GitLab by @thomwiggers on Jul 6, 2016, 20:50 Het is niet een goed idee om flatpages te gebruiken: die dingen vertalen namelijk voor geen meter. Het is veel makkelijker (in termen van vertalen) om gewoon een statische pagina te committen met de relevante |
In GitLab by @joostrijneveld on Jul 6, 2016, 22:24 Right, daar neigde ik ook naar. Helder. |
In GitLab by @joostrijneveld on Jul 26, 2016, 22:24 Marked the task Contact as completed |
In GitLab by @joostrijneveld on Jul 26, 2016, 22:24 Marked the task Sister associations as completed |
In GitLab by @joostrijneveld on Jul 26, 2016, 22:24 Marked the task 'Become an active member' (although potentially part of the active members app) as completed |
In GitLab by @joostrijneveld on Jul 26, 2016, 22:28 'Become a member' lijkt handig om even apart aan te pakken (nadat !8 gemerged is, ook), want die is net een beetje complexer. Daar heb ik #19 voor gemaakt. |
In GitLab by @thomwiggers on Jul 27, 2016, 20:24 Status changed to closed by commit add67b2 |
In GitLab by @thomwiggers on Jul 27, 2016, 21:55 mentioned in commit add67b2 |
In GitLab by @joostrijneveld on Jul 6, 2016, 20:30
Some of our pages are trivially filled with static text. These can be combined in a single package, or go into the
thaliawebsite
package.Consider if flatpages is a good idea, whether we want to roll our own, orsimply hardcode the relevant content in template files.Relevant pages;
'Become a member' (although potentially part of the members app)The text was updated successfully, but these errors were encountered: