4 Commits

Author	SHA1	Message	Date
Chris Hill-Scott	e6a0382243	Make page <title> on API info match page heading ... Otherwise you might get it mixed up with the API integration page when you have a bunch of tabs open.	2016-08-01 09:22:08 +01:00
Chris Hill-Scott	27ad1532e4	Make the flow of using templates better ... For users who: - want to send messages from a template - want to edit templates For developers: - who need to get the ID of a template This commit mainly cleans up the choose template page so there are less options, and the options that are there are less wordy. This means: - moving ‘send yourself a test’ onto the send messages page, and making it button - stripping a lot of stuff out of the ‘send from API’ page, so it’s more obvious what the template ID is	2016-04-19 15:31:19 +01:00
Chris Hill-Scott	a32fd36b1b	Use real API endpoints in documentation ... There is no need to make the API endpoints environment-specific. But it is still useful to know what the endpoint is. Also fixes a broken link on the integration page.	2016-03-21 16:36:15 +00:00
Chris Hill-Scott	8e7b0edc4d	Add page explaining how to send template using API ... Would like to test something like this and see how well it works. Intention of having this page is so: - template IDs are discoverable (https://www.pivotaltracker.com/story/show/115404593) - it’s obvious there’s an ‘automated’ way to send messages, as well as the CSV way (we’ve seen people oblivious to this in research)	2016-03-15 07:11:01 +00:00